Student Data Privacy Policy
1. Who this covers
Teachers create accounts and run classes. Students join a class session by typing a code the teacher shows on the board — they have no accounts and are never asked to agree to anything.
2. What we collect
| From | Data | Why |
|---|---|---|
| Teachers | Name, email, school, login records | Account, license, security |
| Students | A display label (teacher-controlled) and lesson results (score, accuracy, grade, stars) | So the teacher can record a music grade |
We do not collect from students: email, last name (not required), passwords, address, phone, photos, biometrics, location, contacts, or advertising identifiers. Teacher card payments are handled entirely by Stripe — we never see card numbers.
3. What we never do
- No advertising, ad networks, or ad trackers.
- No sale, rent, or trade of any data.
- No marketing or behavioral profiles of students — results are grades, nothing more.
4. Who can see the data
A teacher sees only their own students' results, enforced by database-level row security — not just the user interface. Vendor staff access production data only for support or security, under logging.
5. Infrastructure providers (subprocessors)
| Provider | Role | Student data? |
|---|---|---|
| Supabase (US region) | Database, authentication, server functions | Labels + results |
| Stripe | Teacher billing only | No |
| Vercel | Serving the app over HTTPS | Request logs only |
6. Retention & deletion
- Student results are automatically deleted 365 days after the class session closes (configurable per district).
- Audit logs are kept 18 months for security review, then deleted.
- Teachers can delete any session and all its results from the dashboard, instantly.
- A school or teacher may request full deletion; we complete it within 30 days.
7. Security
HTTPS everywhere; encryption in transit and at rest; teacher-only accounts; server-side license checks; row-level security; and audit logging of logins, session creation, and exports. There is no offline mode and no downloadable copy of the application.
8. Parents
Schools typically cover classroom tools under their existing technology notices. Where direct parent consent is required, we provide sample notice language, and any student can complete the same learning objective in a no-record guest mode where nothing is stored.
9. Compliance posture
Piano Professor is built to align with FERPA and COPPA (operated through schools) and Maryland student-data-privacy expectations. We will sign a district Data Privacy Agreement where required.