Privacy
What Wavicle collects. And what it does not.
A plain-language account of what the system stores about students and teachers, how that data is used, and what never happens to it. Written so a tech director could read it in two minutes.
What is collected
Students
A student joins a class with a join code and a first name. Nothing else is asked for. There is no student account, no student email address, and no student password anywhere in the system.
Teachers
A teacher creates an account with an email address and a password, in order to set up classes, generate join codes, and see results. That email is the only personal detail a teacher account requires.
How it is used
The first name a student enters, their answers, and their simulation results are stored so the teacher who owns that class can see them: in the live results dashboard and in auto-graded assignments tied to that class’s join code. A teacher’s email is used to sign in and to keep their classes and students separate from every other teacher’s. That data lives with Supabase, the database provider behind the site. Wavicle does not run its own separate servers for it.
What is never done
Student and teacher data is never sold and never shared with advertisers. There are no ad trackers on this site and no third-party marketing analytics. Wavicle does not claim a formal FERPA or COPPA certification; the paragraphs above describe, as plainly as possible, what the system actually collects and does, so a tech director can judge it on the facts rather than on a badge.
Wavicle is a small, independent project built by one person, not a company with a privacy department. Questions about how any of this works are genuinely welcome.