For school IT: look inside a file in ten minutes
A packet is one HTML file that holds a short practice activity or a short check. The questions, the recorded sounds and the scoring are inside the file, so it runs in a web browser with no internet connection. At the end the student can save a results file to the device, and a teacher opens that file in a spreadsheet.
Where the data goes
- A teacher makes the file on their own device: on one of the maker pages of this site, or inside the AlloFlow app. The maker page puts the file together in the browser. The words and the choices are not uploaded. What a teacher adds to a word there (its sounds, a recording, a picture) is kept in that browser's storage for this site and goes only into the files the teacher makes. The microphone is used only when the teacher presses Record.
- The file reaches the student by a channel the school already uses, such as its learning platform, email or a shared drive. These pages have no way to deliver a file.
- The student opens the file in a browser. The student's place, answers and the time on each item are kept in that browser's local storage, on that device. On a phone or tablet the student opens it on Open a practice file or check (
packets-open.html). There the file runs walled off in a sandboxed frame, on an origin of its own, so it cannot read anything else this site keeps. It passes that page only two things, bypostMessage: its own progress, which the page keeps in the browser's storage for this site, and its results file, which the page saves to the device. On phones and tablets that support the device share sheet, Open a practice file or check also offers a Share results file button that hands the saved file to the device share sheet only when the student presses it. Nothing is uploaded, except by the class mailbox kind of file, below. - At the end the student presses one button to save a results file to the device: CSV, for a spreadsheet. JSON and a copy to paste are under Other ways to save. Saving sends nothing.
- The student hands the results file to the teacher, again by the school's own channel.
- If the teacher wants, the results files are added up in a spreadsheet, or on the Add up results page, which cannot connect to anything.
Check it yourself
None of these steps asks you to trust this site. Each uses the file itself and your own browser.
- Read the report. Put the file on Look inside a file. It reads the file as text in your browser and lists the policy, the script hashes and every construct that could reach out, with line numbers. Then confirm by hand:
- Find the policy line. Open the file in a text editor. Near the top is
<meta http-equiv="Content-Security-Policy" content="...">. That is the policy the browser enforces on this file. - Read the policy.
default-src 'none'refuses everything the policy does not name.connect-src 'none'refuses every connection a script can make: fetch, XMLHttpRequest, WebSocket, EventSource and sendBeacon.img-src data:andmedia-src data: blob:allow only pictures and sounds held in the file.form-action 'none'andbase-uri 'none'block forms and a base address. Each file made now also carries two reading fonts inside it, Lexend and Atkinson Hyperlegible (SIL Open Font License 1.1), andfont-src data:allows fonts from inside the file only. - Check the script hash.
script-src 'sha256-...'lets one script run: the one whose SHA-256 is that value. The file has one script that runs, plus one data block. Change a character of it and the browser refuses to run it. A matching hash shows that the file agrees with itself, not who made it: a person who changes a file on purpose can change the hash too, and the policy still limits what that file can reach. The report also gives a hash of the code without its data block: two files made the same way, with the same activities, show the same value, so code that was read once does not have to be read again. - Search for what a policy cannot stop. A policy cannot stop a page from being sent to another address. Search the file for
location,open(,<formandhttp. In a packet with no class mailbox, the code useslocationonce, to read the student's code name after#in the file's own address, andhttpappears only inhttp-equiv. A file with a class mailbox also holds the address of its mailbox. - Run it and watch. Open the file with the browser's developer tools on the Network tab, or with the network unplugged, and complete it. No request leaves the device.
- Find the saved place. In the developer tools, open Application (Chrome, Edge) or Storage (Firefox, Safari), then Local Storage. There is one key, named
alloflow-take-home:then the packet id, a colon and the version. To clear it, press Start over in a practice file, delete the key, or clear the browser's site data. A check keeps the student's label and a count of tries after Start over, so clear a check in the browser.
The facts, for a privacy review
| What is collected | A label the student types (a code name or a first name; it can be left blank). For each item: each answer, the number of tries, the time on the item, how often each help was used (a count for each, such as hearing a word again, and the reading tools: bigger text, contrast, spacing, reading focus and the magnifier), and a note when an item was skipped, ran out of time or was open when the file was opened again. The start and finish times from the device clock, with its offset from UTC, and a random session number. A check also records the seconds the page was hidden, the try number, and whether the page was left for more than 3 seconds, reloaded, or had its clock set back. Listening choices inside a file (voice speed and spoken directions) stay on the device and are not written to the results file. Nothing else: no email address, no account, no details of the device or the browser, no location. |
|---|---|
| Where it is stored | In the browser's local storage on the student's device, and in any results file the student saves. |
| Who can read it | Anyone who uses that browser on that device, and anyone who is given the results file. Neither is encrypted. The answers of a practice file can be read in its source. The answers of a check are scrambled, which stops casual looking only. A teacher code locks the review screen of a check; it is not encryption. |
| What leaves the device, and when | Nothing, unless a person passes on a saved results file. There is one exception: the class mailbox kind of practice file, in the next row. For teachers, one page of this site, Find a picture (packets-pictures.html), can search three picture services after the teacher turns its search on: Global Symbols, Openverse and Wikimedia Commons. It sends them the word searched for and asks them for the pictures it shows. One more page, Look up a word online (packets-vocab-lookup.html), can send one word that is not in the vocabulary word list to the Free Dictionary API (api.dictionaryapi.dev), after the teacher allows it and presses Look it up. Two more pages, Make recordings with a computer voice (packets-voice.html) and Make a read-along (packets-read-along.html), are the only pages of this site that use AI: after the teacher presses Get the voice, the page downloads a voice (Kokoro, about 88 MB) from Hugging Face (huggingface.co) and runs it on the device. They send no words: Hugging Face sees only that the browser asked for the voice. A read-along file that a teacher saves holds recordings and plays them: it runs no voice and reaches no site. A check for the youngest students (Quantity Discrimination or Missing Number) holds a recording of its directions, made ahead of time with the same computer voice and stored on this site with the page; it plays only when the student presses Hear the directions, and the results say how often that was. Every other page of this site reaches only this site. A vocabulary file reads aloud only with a voice that runs on the device: it does not use a voice that sends the text to a speech service. |
| The class mailbox kind | A practice file made inside the AlloFlow app by a teacher who has set up a class mailbox has a Send button. When the student presses Send, the results go to that class mailbox, a Google Apps Script web app at script.google.com, and nowhere else. The file carries its mailbox address inside it, so anyone who has the file can post to that mailbox. How to recognize one: the report on Look inside a file starts "This file can send results to one place", the policy's connect-src names script.google.com, and About this file says so. Files made on this site's maker pages have no mailbox. Checks are made with no mailbox. Such a file can also send from Open a practice file or check (packets-open.html), the page that runs a file on a phone or tablet: that page's rule allows the class mailbox for the file it runs. The page itself sends nothing. |
| What this site's server can see | When someone uses these pages: ordinary web requests for the pages, their scripts and, on the maker pages, the sound files and the vocabulary word list, with what every web request carries, such as the IP address and the time. Most sound files are the same whatever is chosen, and so is the word list. Some words have their sounds in small files of about 40 words each, and the Word Sounds and vocabulary makers ask only for the ones they need: the server can see which of those files were asked for, not which words. Never the words or the choices, and never results. If a school puts a packet on its own web server, that server sees requests for the file and nothing the student does in it. |
| Accounts, cookies, analytics | None on these pages: no sign-in, no cookies, no analytics or tracking scripts. Each page lists every file it loads under See the details. In the browser, each maker page keeps the teacher's last choices (the Word Sounds maker also keeps the sound files, and the vocabulary maker the teacher's changes to the questions), the results page keeps results only if a switch is turned on, Open a practice file or check keeps the place of each file it runs, and this page and Look inside a file keep nothing. Present & print word cards keeps the last export setup on this device until cleared. What a teacher adds to a word on the maker page or on Find a picture (its sounds, a recording, a picture with its credit) is kept in that browser's storage for this site (IndexedDB) until the teacher removes it. It is not uploaded. Custom pictures added on the vocabulary and Symbol Runner makers are kept in that same browser storage and are not uploaded. |
| How long it is kept | As long as the school keeps the files. The saved place stays in the student's browser until it is cleared. This site holds no copy, because nothing is sent to it. Results sent to a class mailbox are held by that mailbox; ask the teacher who set it up. |
| License and code | AGPL-3.0, free to use. The code is public: AlloFlow on GitHub. A packet is built by word_sounds_packet_builder.js (Word Sounds practice), packet_math_practice_builder.js (math fact practice), packet_check_builder.js (math checks), packet_vocab_builder.js (vocabulary practice and checks), packet_symbol_runner_builder.js (Symbol Runner practice and checks) or packet_read_along_builder.js (read-alongs), with word_sounds_take_home_loader.js. Audio compression to MP3 on the maker pages (including Symbol Runner) uses packets_audio_kit.js and lame.min.js from this site. What Look inside a file looks for is in packets_verify_core.js. The two reading fonts inside each file are under the SIL Open Font License 1.1. What is inside a file, its results files and the one file that Add up results saves is written down in the file format document. Who makes Packets and how to report a problem: About. |
Whether this meets your district's obligations under FERPA or state law is your district's decision; this page gives you the facts to make it.
Known limits
- A results file can be edited. The check value inside it finds accidental changes, not deliberate ones.
- Times come from the clock of the student's device.
- A packet is for practice and for checking progress. It cannot keep its answers secret: they travel inside the file so that it can score with no internet.
- Look inside a file reads text. It cannot follow code that hides what it does, and it cannot prove that software is free of mistakes. Reading the script goes further: it is one script and it is not minified.
- The previews in Google Drive, Google Classroom and the iPad Files app do not run the file: the file shows a note that asks the student to download it and open it in a browser. Reported, not yet tested by us. A student can open the file on Open a practice file or check (
packets-open.html) instead, which works on any device, phones and tablets included. - The file has had no formal accessibility audit yet.