What we do with your students' data.
Gregarious was built by a classroom teacher and doctoral researcher. This page answers every hard question we could think of, honestly, including the ones we don't yet have full answers to.
Last updated: October 2026
AI Use Details
What AI does, and what written rules decide
Safety Protocols
Concerning content and crisis response
Full Privacy Policy
Complete legal privacy document
1. What Gregarious does with student data
Student data in Gregarious is used for exactly one purpose: improving the educational experience of the student who generated it and supporting the educators and parents who serve them.
We collect:
- •Account information: display name, email address, role, and grade level.
- •Mastery activity: which standards were practiced, how many questions answered, scores earned, and session timing. This powers the adaptive engine.
- •Studio work: saved on the student's own device until the student chooses to share a piece with their class. A shared piece is visible to classmates in that class, their teacher (who can hide it), and a linked parent. Nothing in Studio is graded.
- •Pulse check-ins: a daily mood indicator (emoji selection) and optional short text. Shown in aggregate to the student's teacher. Never shared outside the classroom.
- •Usage patterns: pages visited, features used, session length. Used to improve the product and for anonymized dissertation research. Never tied to a student's name in any published report.
We do not collect biometric data, device identifiers, location data, or any information unrelated to the student's learning activity.
2. Is student data sold?
No. Student data is never sold.
Gregarious does not sell student data to anyone, for any reason, ever. We do not share it with advertisers, data brokers, or any commercial third parties. The business model is school subscriptions, not data monetization.
We also do not use student data to show advertising, build commercial profiles, or train AI models without explicit opt-in consent from a parent or eligible student.
3. How is AI used?
In the core product, AI does one thing: the Socratic tutor. Everything else a school would worry about is decided by written rules a teacher can read.
- •Socratic tutor: when a student is stuck on a sprint question, the AI asks a guiding question rather than giving the answer. It never writes essays, answers questions for students, or completes assignments on their behalf.
- •No AI grading: sprint scores are the share of questions a student got right, and Studio work is never graded.
- •Written rules, not AI, find learning gaps, show what the class misread, and screen for safety concerns. A teacher can see the rule and make the call.
Tutor requests carry no student name, and every message a student types passes a safety screen first. The code also holds AI drafting tools for teachers outside the core product; none of them is offered to schools today.
For full documentation of every AI touchpoint, see /trust/ai.
4. Who can see my child's data?
Access is strictly role-scoped. A student cannot see another student's data. The following people can see a student's record:
Their own mastery scores, EP and Studio projects, and what classmates choose to share with the class. Never another student's scores.
Mastery data and pulse trends for their enrolled students only. They cannot see data from other teachers' classes.
Their linked child's mastery percentage, EP, streak, and Studio projects. Read-only. No other students' data.
Anonymized, aggregate data only for dissertation research. Individual student records are not accessed for research purposes. IRB protocol requires anonymization before any analysis.
Individual records only to investigate a bug or support request, and only with the school's knowledge. Never for marketing or product analytics at the individual level.
5. How does deletion work?
Schools, parents, and eligible students have the right to request deletion of a student account and all associated data.
- •Email cgb003@gmail.com from the school's official address (or a parent's email on file).
- •Include the student's display name and the school name.
- •We will confirm receipt within 2 business days.
- •Deletion is completed within 30 days of the confirmed request.
- •You will receive a confirmation email when deletion is complete.
Anonymized, aggregate research data that cannot be linked back to any individual may be retained under IRB protocol #2025-0847 for dissertation purposes. This data has no name, email, or school identifier attached.
You may also request a full export of your child's data before requesting deletion. We will provide a CSV within 5 business days.
6. What happens if there's a breach?
In the event of a confirmed data breach affecting student records:
- •We will notify affected schools and parents within 72 hours of discovery.
- •Notification will include: what data was affected, when the breach occurred, what we have done to contain it, and what you should do.
- •Supabase handles encryption at rest (AES-256) and in transit (TLS 1.2+). Breach response is covered under Supabase's SOC 2 Type II certification.
- •We will file all required notifications under applicable state and federal law.
If you discover a security vulnerability, please report it to cgb003@gmail.com before public disclosure. We take responsible disclosure seriously and will respond within 48 hours.
7. Subprocessors
Gregarious uses the following third-party services. Each is subject to a data processing agreement, and each was selected in part for its privacy posture.
Supabase
Database and authentication
Stores all user accounts, student records, and activity data. Enforces row-level security at the database layer. US-based infrastructure. SOC 2 Type II certified.
Vercel
Application hosting
Hosts the Next.js application and serves it globally via edge network. No student data is stored at the CDN layer. SOC 2 Type II certified.
Anthropic
AI features
Powers three features in the core product: the Socratic tutor, a first-draft score on a short write that the teacher confirms or changes, and translating one family message when a teacher or parent taps Translate. Tutor and scoring requests carry no student name. A message to translate has the student's, teacher's and parent's names swapped for placeholders before it is sent, and the translation is not saved. AI tools outside the core product remove names from chat and progress-report requests, and teachers are asked not to paste names into them. Under Anthropic's commercial terms, API requests are not used to train its models.
Resend
Transactional email
Sends account confirmations, the weekly emails parents and teachers turn on, and breach notifications. Receives the recipient email address and the message for that send; a parent's weekly email describes their own child's week (sprints, EP, standards reached 70%, shout-outs).
We do not use advertising networks, behavioral tracking pixels, or social media SDKs anywhere in the student-facing platform.
8. For district IT teams
Starting a district procurement review?
We want to make this as easy as possible. The documents below should cover most of what your review team needs. A Data Privacy Agreement (DPA) is available on request.
Gregarious is designed for FERPA compliance. Student education records are accessible only to the student, their teacher, and their linked parent. We act as a school official under the school's direction and do not own student data.
Search engines are asked to stay out. The student, teacher, parent and admin portals and every API route answer with a noindex, nofollow header and are disallowed in robots.txt; the sitemap lists only the public pages. A page that carries student data is never meant to be found by a search, only reached by signing in.
If your district has a student data privacy addendum template, send it to cgb003@gmail.com and we will review and sign it. If your district uses the Student Data Privacy Consortium's National Data Privacy Agreement, we will sign that.
9. What has been checked, and by whom
Honest transparency
Gregarious is an early-stage platform built by one teacher with AI assistance. Nobody outside the project has reviewed the code yet. Here is what we check ourselves, what is planned, and the timelines.
What do you check yourselves?
On every push: an automated workflow runs more than 300 tests, including checks that data routes refuse signed-out and wrong-role requests and a check that no public page claims more than is true; a lint pass; a dependency audit; and a scan of the repository for leaked secrets. Before every release: a production build and an accessibility check (WCAG 2.1 AA) that passes on the 101 pages reachable from the home page and the four portals. Row-level security is on every database table, AI routes are rate-limited, every student AI request goes through a safety filter, and every response carries the standard security headers (the app cannot be shown inside another site, and the browser is told which device features it may use). These are our checks, not an independent review.
Has Gregarious had a penetration test?
Not yet. The product for a first pilot is being cut down to the pages and routes it needs (107 portal pages and 149 API routes today, listed in docs/CORE-PRODUCT.md) so that an independent firm can test all of it. That test is planned before the Spring 2027 district wave. Until then, no outside party has tested the application.
Is Gregarious SOC 2 certified?
Not yet. Our infrastructure (Supabase and Vercel) is SOC 2 Type II certified, which covers the storage and delivery layers. Gregarious itself as an application has not undergone a SOC 2 audit. We are working toward this. Timeline: 2027.
Is there a bug bounty program?
Not yet formally. If you find a security issue, please report it to cgb003@gmail.com. We take responsible disclosure seriously and will work with you. The same address is published at /.well-known/security.txt for scanners that look for it. A formal program is on the roadmap. Timeline: 2027.
What about COPPA?
Gregarious is designed for grades 5-12 and does not knowingly collect data from children under 13 without verifiable parental consent. Deployments involving students under 13 require a signed parental consent form administered by the school. We are evaluating formal COPPA compliance documentation. Timeline: 2027.
We would rather be honest about our current state than obscure it. If one of these gaps is a blocker for your district, reach out and we will talk through it.
Questions? Talk to a real person.
We are a small team. You will get a real answer from Brian, not a ticket number.
cgb003@gmail.com