FLXCode

FLXCode apps

Appearance

Check it yourself

You don't have to trust the privacy page. Here is how to see what your browser sends.

1. Watch the Network panel

  1. Open a tool, for example the QR code generator.
  2. Chrome or Edge: press F12 (Mac: Cmd + Option + I) and open the Network tab. Firefox: F12, Network tab. Safari: turn on the Develop menu in Settings, Advanced, then Develop, Show Web Inspector, Network tab.
  3. Reload the page so the list starts clean. Then type something, play a tone or start the microphone.
  4. Look at the list. Once the page and its files have loaded, the only request that carries anything about you is a POST to /api/e. Other rows are the page's own files from flxcode.com, such as a decoder or a data file. Click it and open Payload (Request in Safari).

If you type in a tool and nothing new appears in the list, nothing was sent. A share link or a map link that you choose to click opens a new page, and you see that as a navigation.

2. What the one request holds

The page batches its counts into one small request. Usually that is one request after your first click or key press and one more when you leave the page. It looks like this:

{"app":"tone-generator","v":"","d":"desktop","h":"prod",
 "events":[{"event":"app_view","b":"search"},
           {"event":"play","b":"mid"}]}

That is the app name, a version, the device class, the environment and a list of event names with at most one short value each, such as a frequency band. No text you typed, no audio, no file, no cookie. Your IP address and browser details are not in the request body. Our server turns them into a daily code on arrival, and the key to that code expires at the end of the day. The full list of events is under each app on the privacy page.

3. Airplane-mode test

  1. Open a tool and wait until it has loaded.
  2. Turn on airplane mode, or switch off Wi-Fi and mobile data.
  3. Use the tool: type a coordinate, make a QR code, play a tone.

It keeps working, because the tools run in your browser. Only the counts above can't be sent. Reloading the page needs a connection, since the site doesn't work offline yet.

4. The security policy header

Every page on this site is served with a Content-Security-Policy header. Older pages in legacy app folders have their own, looser policies (the old /tonelab_web/ build also allows one font host, fonts.gstatic.com). The policy tells your browser to refuse connections to other hosts, so a page could not send your input elsewhere, even by mistake. See it in the Network panel (click the page request, then Headers), or in a terminal:

curl -sI https://flxcode.com/ | grep -i content-security-policy

This is the policy of this build:

connect-src 'self' means pages may only talk to flxcode.com. form-action 'none' means no form can post anywhere. style-src allows inline styles because the pages set sizes and colours that way. Scripts get no such allowance.

5. Which build you are looking at

This page was built from commit 1b16327. The same short hash is in the footer of every page, linking here. If it says dev, the page was built without version information.