1. Who this covers
This policy covers InterClass accounts for students, parents/guardians, and staff of one pilot school, [School Name]. It is not a general public product. If a student is under 13, see "Children under 13" below.
2. What we collect
| Data | Who | Why |
|---|---|---|
| Email address | Everyone, at signup | Login (parents/staff), password reset, and (for students) verifying school affiliation via Google account domain |
| First name, last initial | Everyone, at signup | Showing who a message is from/to, without storing a full last name unnecessarily |
| Grade level | Students | Shown to staff in the account list |
| Role | Everyone | Controls what the account can see and do |
| Password | Parents, staff | Stored as a salted hash by our authentication provider (Supabase Auth); we never see or store the plaintext. Students have no InterClass password; they sign in with their school Google account instead. |
| Messages you send | Students, parents | Delivering the message, and the safety/monitoring purposes described below |
| Blocked message attempts + why | Students, parents | Safety review by staff |
| Reports you file | Students | Routing your report to staff |
| Pings | Students | Feature delivery |
| Parent-student link requests + code | Students, parents, staff | Making sure only an approved parent/guardian can message a given student |
| Terms/consent acceptance, with timestamp | Everyone, parents specifically for parental consent | Recording that you agreed, and when |
| Staff dashboard views and moderation actions | Staff | Accountability: an audit trail of staff activity itself |
We deliberately do not collect: physical addresses, phone numbers, government ID numbers, payment information, or any content beyond plain text (InterClass does not support links, images, or file attachments).
3. How messages are monitored, and by whom
InterClass is built to be watched, not private. Specifically:
- Everyone in a conversation can see the full content of their own messages.
- An automated content filter scans every message before it's sent, and blocks ones matching hateful/derogatory language, bullying or self-harm language, sexual content, or certain profanity. Blocked attempts are stored in full for staff review, on every channel.
- Staff can see an aggregated pattern flag for peer messaging or pinging with nothing coming back over the last two weeks (e.g. a student who's been reaching out and getting no replies): names and counts only, not a message-by-message log of every ordinary message sent.
- Staff can see the full text of a message only if it was blocked by the filter, or a student reported it. This is enforced at the database access-control level, not only by what the dashboard UI chooses to display. A staff account cannot query the full text of an ordinary, unflagged, unreported message, even directly.
- A parent/guardian can see their own messages with their linked child, the same way any participant in a conversation can. They do not see their child's messages with other students.
- Staff dashboard access is itself logged: which staff member viewed the dashboard or took a moderation action, and when.
4. Who we share data with
- Supabase, our database, authentication, and hosting provider, processes all InterClass data on our behalf as a service provider.
- An email-sending provider (e.g. Resend), once configured, delivers password-reset emails and, if enabled, parent email-confirmation links.
- School staff, as described in Section 3.
We do not sell personal information and do not use it for advertising.
5. How long we keep data
Messages are deleted automatically on a schedule: ordinary messages(peer and parent channels) after 30 days; blocked/flagged message content kept up to 365 days, since this is the content staff may need for a disciplinary process that unfolds over months. These numbers are configurable by [School Name]'s admin to match the district's own records-retention schedule.
6. Children under 13
[School Name] is a [grade range, e.g. "grades 9-12"] school, so InterClass is generally not directed at children under 13. If that ever changes, verifiable parental consent meeting COPPA's requirements would need to be obtained before that student's account is activated, using a stronger method than the consent flow described below. If you believe a child under 13 has an InterClass account without that additional consent, contact [Your Email] immediately.
7. How consent works
Every account holder checks a box agreeing to this Privacy Policy and our Terms of Use at signup, recorded with a timestamp. For students specifically, a parent/guardian must separately confirm consent to that student's use of InterClass, either digitally, by checking a consent box when submitting a parent-student link request in the app, or through a staff-confirmed process outside the app. A student's peer messaging is not enabled until this consent is on file. See our parental consent process document for the full mechanics.
8. Your rights and choices
A parent/guardian, or a student themselves, can request a copy of the data InterClass holds, request early deletion of specific messages or the full account, revoke a parent-student link, or deactivate the account entirely, by contacting the admin, [Admin Name / Title], or [Your Email].
9. Security
Passwords are hashed by Supabase Auth; we never see them in plaintext. Data is encrypted in transit (HTTPS). Access to student data is restricted by role-based database rules (row-level security). InterClass has not undergone an independent third-party security audit as of the effective date above.
10. Changes to this policy
We'll update this policy as InterClass changes, and notify [School Name]'s admin of material changes so families can be informed.
11. Contact
Questions about this policy, or a data request under Section 8: [Your Name / Email], or [School Name]'s InterClass admin, [Admin Name / Title].