Last updated 25 September 2026
Class Dash has no accounts, no server-side database, and no analytics. Everything you enter stays in the browser you entered it in, unless you pair a hall pass kiosk, link two computers, or turn on sync with Google. We keep no copy of anything, because there is no database to keep it in.
Class Dash can now pair a door iPad as a hall pass kiosk. If you do, student names and sign-out times travel between your computer and that iPad through a small relay server we run. They are encrypted before they leave either device, with a key only those two devices hold, so the relay passes along messages it cannot read. If you never pair a kiosk, nothing changes and nothing leaves the device. The details are under The hall pass kiosk.
On 25 September we added a noise meter that listens through a microphone. Sound is measured and thrown away on the device. Nothing is recorded or saved. If you use a phone as its microphone, only a loudness number travels, encrypted, through the same relay. The details are under The noise meter.
You can also link two of your own computers, so the computer that runs your classroom Board matches the laptop you plan on. Everything that passes between them is encrypted with a key only those two computers hold, through the same relay as the kiosk. The details are under Linked computers.
Also on 25 September we added an optional sync with Google, for teachers who use more than one computer. If you turn it on, Class Dash saves a copy of your classes, rosters, schedules, plans, and hall pass log to one spreadsheet in your own Google Drive. That copy is readable, not encrypted, and it lives in your Google account, not with us. Nothing passes through a server of ours. The details are under Sync with Google.
Class Dash writes to a single key in your browser's local storage, named classdash.v1, on the device you are using. That entry holds:
Be aware that student first names are student data. If you type them in, they are stored in that browser profile on that computer. They are not sent anywhere unless you pair a kiosk, but they are readable by anyone who can unlock and use that device, and by anyone who opens a backup file you export. Treat the device and the backup file the way you would treat a paper roster.
Nothing, until you deliberately embed something or pair a hall pass kiosk. The application code contains no analytics, no tracking pixels, no content delivery networks, and no web fonts, and the only code that sends data anywhere is the optional kiosk link, the optional phone microphone link, optional linked computers, optional sync with Google, and the pass timer's one status message. The only outbound connections are ones you create:
| If you | Then |
|---|---|
| Add a video to a plan | Your browser loads it from youtube-nocookie.com, YouTube's reduced-tracking embed domain |
| Add a Google Docs, Slides, Sheets, or Forms link | Your browser loads a preview from docs.google.com |
| Add a YouTube playlist under Music | Your browser loads YouTube's player from youtube.com |
| Add any other link | Your browser loads that address directly |
| Pair a hall pass kiosk | Your browser and the iPad each connect to our relay at presenter-relay.onrender.com and exchange encrypted messages through it |
| Scan the timer code after signing out at the kiosk (only if the teacher turned the phone timer on) | The student's phone opens a page from classdash.app and connects to the relay for that one trip. The Board sends it only "still out" or "back", encrypted with a key made for that trip. No name is involved |
| Link two computers | Both connect to the same relay. The laptop sends its setup and plans to the Board, and the Board sends back hall pass sign-outs, all encrypted with a key only those two computers hold |
| Turn on sync with Google | Your browser signs in at accounts.google.com and reads and writes one spreadsheet in your Google Drive through sheets.googleapis.com and www.googleapis.com. Nothing passes through us |
| Pair a phone as the noise meter's microphone | The phone and your browser connect to the same relay. The phone sends loudness numbers, encrypted. No sound leaves the phone |
Those requests come from your browser to that company, exactly as they would if you opened the site in a tab. Their own privacy policies and your district's filtering rules apply. Class Dash sends them no information about you, your classes, or your students. If you never use those features, the application makes no outbound requests at all after the page loads.
Pairing is optional and off until you choose it. When you pair, your browser makes a random room code and a random 256-bit key and puts both in the link inside the QR code, in the part after the # sign. Browsers do not send that part of a link to any server, including ours.
What crosses the relay: the current period's class list as you typed it, the class and period names, your list of places, your pass settings, and each sign-out and sign-in with its time.
How it is protected: every message is sealed with AES-GCM using that key before it leaves your computer or the iPad. The relay forwards sealed messages to the other device in the same room and does not store them. It never has the key.
What the relay can see: the room code, how many devices are connected, when messages pass and how big they are, and the IP address each device connects from. It writes room codes and connection counts to its log. It is hosted on Render, which keeps its own request logs, including IP addresses. We use those logs only to keep the relay running. The same relay carries the remote control for Class Dash Presenter.
What stays on the iPad: the kiosk writes one entry to its own local storage, named classdash.kiosk.v1. It holds the room code and key, the current period's class list and who is out, and any sign-outs the Board has not confirmed yet. It keeps no history. The room code and key also stay in the kiosk's link, and in its Home Screen icon if you add one, because that is how the icon pairs itself.
What this does not protect against:
The noise meter is off until you open it and press Start, and the browser asks your permission before it can use a microphone. Once on, it keeps listening when you close its window or switch to another tab, and if you leave it on, it starts again by itself the next time you open Class Dash. Stop turns the microphone off. While it runs, the browser shows its own sign that the microphone is in use.
On this computer, or with a USB microphone: the browser measures how loud the room is ten times a second and throws the sound away as it goes. Nothing is recorded, saved, or sent anywhere.
With a phone: the phone does the same measuring and sends only the resulting number, a loudness level from 0 to 100, ten times a second. It is sealed with its own key, separate from any kiosk, and passes through the same relay as the hall pass kiosk. Your computer sends back which colour and words to show. No sound, no names, and no class information go to the phone. The phone keeps only its pairing, in an entry named classdash.mic.v1, and in its link and Home Screen icon if you add one.
The meter cannot tell voices apart and does not try to. It hears a room, not a person.
This is off unless a teacher turns it on in Settings, since many states and districts don't allow students to use phones during class. When it's on, after a student signs out at the door kiosk, the kiosk shows a code they can scan to carry a timer on their phone, so they know how long they have been out and when it is getting long. Nobody has to scan it, and it is not a hall pass anyone checks.
What the link carries: where they went, the time they left, the class name, your warning minutes, when the class period ends, and which Class Dash theme to show. It carries no student name and nothing else about the student. All of it sits after the # in the link, a part browsers never send to any server.
What the phone connects to: the relay, in a room made for that one trip, with a key made for that one trip. The Board sends only "still out" or "back". The phone never gets the roster, other students' trips, or the kiosk's key, and the Board never reads anything a phone sends. The relay sees the phone connect and its IP address, the same as for any device that uses it. Loading the page itself is an ordinary visit to classdash.app, which our web host sees like any other.
What it can't do: it knows the student is back only if the phone can reach the relay. If it can't, it keeps counting until the class period ends, or for an hour when there is no schedule, then says class is over. The Board forgets a trip's key ten minutes after the student is back.
Linking is off until you choose Link computers from the menu on two of your own computers. One shows a six-digit code, you type it on the other, and both screens show a four-digit check number to compare.
How the key is made: the code only lets the two computers find each other on the relay. They then agree on a 256-bit key between themselves, using the browser's built-in cryptography, so the key never crosses the relay or reaches us. The check number is made from that key: if it matches on both screens, no third computer is in the middle.
What crosses the relay: from the laptop to the Board, your classes and the student names in them, schedules and school calendar, plans, group rules, and music and alarm settings; from the Board back to the laptop, hall pass sign-outs. Every message is sealed with AES-GCM before it leaves the computer. The relay forwards it to the linked computer and does not store it.
What stays on each computer: the look and colours, window positions, running timers, the noise meter, the This computer is in setting, and any kiosk or phone pairing. The link's key stays in that computer's browser, in an entry named classdash.device.v1, never in backup files.
What the relay can see: the same as for the kiosk: a room code, how many computers are connected, when messages pass and how big they are, and each computer's IP address.
What this does not protect against:
Turning it off: choose Unlink this computer in the Link computers window. Start with a blank slate also unlinks that computer first, so the other one keeps everything. When a Board that already has its own setup is linked, it asks before the laptop's setup replaces it, with a button to save a backup first.
Sync is off until you choose Sync with Google from the menu and sign in. It exists for teachers who use a different computer in each building, or plan at home.
What it asks Google for: one permission, to see, edit, create, and delete only the Google Drive files Class Dash itself creates. It cannot open anything else in your Drive, your email, or your contacts. It also reads your Google account's email address, to show you which account is connected.
What it saves: one spreadsheet named Class Dash sync in your Drive. Its Data tab holds your classes and the student names in them, your schedules and school calendar, your plans, your group rules, your music and alarm settings, and the hall pass log. Its Hall pass tab shows the hall pass log as rows you can read, sort, and print. None of it is encrypted: anyone who can open that spreadsheet can read it, including anyone you share it with and, for a school Google account, your district's administrators.
What stays on each computer: the look and colours, window positions, running timers, the noise meter, kiosk and phone pairing, and the This computer is in setting.
How it travels: straight from your browser to Google. The sign-in pass Google gives your browser lasts about an hour and is kept only in that browser tab's session storage. Class Dash has no server that could receive it, and we never see your data, your email address, or the spreadsheet.
What this does not protect against:
Turning it off: choose Disconnect in the sync window on each computer. Delete the Class Dash sync spreadsheet in Google Drive to remove the copy. To take back the permission as well, remove Class Dash from the third-party apps and services list in your Google Account's security settings.
The site is served as static files by Netlify. Like any web host, Netlify records ordinary server request logs, which can include IP address, timestamp, and browser user agent. That is a property of loading any web page and is not specific to Class Dash. We do not read, export, or analyse those logs.
The form on the contact page is the one place where you can send us something. Whatever you type there, including an email address if you provide one, is delivered to us through Netlify Forms so we can reply. Please do not put student information in it.
We do not describe Class Dash as "FERPA compliant" or "COPPA compliant", because those laws place obligations on schools and on operators who collect data, and a self-declared label on a product page means very little to a careful reviewer. What we can state plainly:
If your district requires a signed data privacy agreement, a completed vendor questionnaire, or an entry in a state privacy consortium, please use the contact form and say which one. We would rather complete your paperwork than ask you to take a claim on a web page at face value.
Because there is no server copy of ours, deletion is immediate and complete. There is nothing for us to purge on request, and no retention period to disclose.
Class Dash is a tool for a teacher to run from the front of a room. The one screen students touch is the optional hall pass kiosk, where they tap their own name and where they are going. It asks nobody, adult or child, to create an account or supply any other information about themselves.
If this notice changes, the date at the top changes with it. If a change ever meant that data began leaving the device, that would be stated at the top of this page in plain language rather than buried in a revision.