Data Processing Summary

What Greta stores and why.

Last updated: July 15, 2026

This is a plain-English product summary for a school or privacy administrator evaluating a teacher’s personal Greta account. It is not a contract. For the exact FERPA posture and the language Greta uses for teacher-kept observational notes, read the FERPA page.

What can be collected

Teacher account: email, name, optional school context, and password authentication data.
Teacher writing and capture:voice memos, text notes, transcripts, conversations with Greta, and teacher-approved writing samples used for that teacher’s voice.
Student context: first names and optional last initials, teacher-kept observations, academic progress notes, and optional full names when a teacher chooses that setting.
Carefully gated details: photos only when a teacher opts in per kid; IEP flags and accommodations are stored with review and draft-only safeguards.
Family and connector context: parent contact information and only the Gmail, Calendar, Drive, Outlook, or OneDrive context a teacher asks Greta to use.
Generated work: drafts, sub binders, newsletters, conference preparation, and other artifacts prepared for teacher review.

What Greta does not store as student fields

Greta’s schema rejects SSNs, birth dates, and student ID numbers as data fields. Greta also does not provide fields for official transcripts, grades of record, disciplinary files, attendance records, or free-text medical diagnoses. Keep those records in the district system intended for them.

Where the data lives

Greta stores account data, notes, records, drafts, and files with the infrastructure and service providers listed on the Trust page. The list includes the purpose, data touched, dated pass-through claim, and source link for each provider.

Anthropic: Claude drafts and other language-model features.
OpenAI: Whisper transcription and text embeddings for search.
Convex: Database, file storage, and backend functions.
Vercel: Web application hosting and delivery.
Twilio and participating mobile carriers: Optional SMS/MMS capture, verification, and compliance messages.
Composio: Optional Gmail, Calendar, Drive, Outlook, and OneDrive connector actions.
Postmark: Inbound email capture.
Sentry: Error tracking and performance monitoring.
PostHog: Privacy-conservative product analytics.

Who can touch it

Greta uses the minimum context needed for the feature a teacher asks for. Provider access is limited to the service being operated: model calls for requested drafts, transcription for requested audio, connector reads after a teacher connects them, and SMS or email transport when a teacher uses those capture channels.

Drafts stay drafts until the teacher reviews and sends them. Analytics and error events use privacy-conservative operational fields rather than names, transcripts, notes, email bodies, or classroom content.

Deletion, export, and retention

Teachers can remove individual kids, notes, and class memories from live storage.
Provider backups follow a retention window of up to 30 days.
Full account deletion or a copy of a record can be requested through privacy@teachgreta.com with a verified request. There is no in-app export screen in this alpha.
Raw voice audio is purged after 90 days; the transcript is retained according to the account’s current retention settings.
Anonymous error logs are retained for 90 days. Billing records, when applicable, are retained for the legally required period.

See the Privacy page for the public policy, the FERPA page for the exact FERPA-adjacent language, and the Trust page for controls and provider sources.