FLXCode

FLXCode apps

Appearance

For schools and libraries

What runs where, what we count, what is tested, how you may reuse things, and how to link to us.

This page is about the web tools on flxcode.com. The Android apps have their own privacy policies, linked from privacy.

What runs where

The tools run in the browser. Text you type, files you open and sound from the microphone are handled on the device and are not uploaded. This is enforced by the page policy, not only promised: the Content-Security-Policy header on every tool page allows connections to flxcode.com and nowhere else, and forms cannot be submitted. A tool page cannot send data to another site.

The exceptions, all of them:

What we count

Pages send small usage events to /api/e, our own endpoint, which accepts only events from a fixed list. An event holds the tool name, an event name such as "played a tone", a device class (phone, tablet or desktop), country and region, a coarse system and browser family, a two-letter browser language and where the visit came from (a category or a known site name). Some events add one value from a short fixed list, like a mode name. What you type, the files you open and recorded sound are never in them. Every event of every tool is listed, and you can check it yourself.

There is no cookie and no ID stored in the browser. The server makes a daily code from a secret salt, the IP address and browser details, then throws the inputs away. The salt is deleted at the end of each UTC day, so a browser gets a new code the next day. The privacy notice says records are kept for 3 months. A school that does not want to be counted can use the "Don't count my visits" switch there, per browser.

No cookies, no accounts and no ads on the tool pages. Our code never sets a cookie, no tool turns ads on, and the page policy only allows scripts from flxcode.com, so ad and tracking scripts from other companies cannot run. Tool settings are kept in the browser's local storage on that device and are not sent to us. Anyone can delete them from the privacy page.

Accessibility

We aim for WCAG 2.2 level AA. We do not claim full conformance and we do not publish a formal conformance report. What is tested:

Automated checks find only part of the problems. If something does not work for a student, tell us the page and the device.

Licenses

The reference data (tables, CSV and JSON files and posters on the reference data pages) is CC BY 4.0. You may copy, change, print and hand it out, in class or in a publication, with credit and a link to the page. The reference page has a sentence you can copy.

The rest is not under that license. The terms say the code, text and design of the site belong to FLXCode and the tools are free to use for personal or work purposes. Files and sounds you make with a tool are yours. Open-source parts keep their own licenses, listed in the legal notice. If you want to copy a page or reuse text that the terms do not cover, ask first.

Linking from a library guide or course page

Questions

A data-protection question we have not answered, a tool a class needs, a mistake in a table: write to flxcodelab@gmail.com.