Technical Data Sheet
For IT Admins & Data Protection Officers
This page provides the full technical picture of how magistrOS interacts with Google Classroom — scopes requested, when they are used, what data is stored, and how it is protected. Share it with your school IT team or DPO before approving the app in your Google Workspace domain.
Available on the Google Workspace Marketplace
Domain admins can install magistrOS directly from the Marketplace for all teachers in their school — no individual sign-ups needed.
Google OAuth Scopes
magistrOS uses incremental authorisation. Teachers grant only read-only scopes when they first connect. Write scopes are requested in context — only when a teacher explicitly clicks a Pro write feature for the first time.
…/classroom.courses.readonlyRead your class list
Always — needed to show your classes in the app
Read-only…/classroom.rosters.readonlyRead student names per class
Always — needed for risk detection and parent email drafts
Read-only…/classroom.student-submissions.students.readonlyRead submission status and grades
Always — used to detect at-risk students
Read-only…/classroom.coursework.studentsRead & write student coursework
Pro only — requested separately the first time a teacher clicks "Push Grades to Classroom"
Write (Pro)…/classroom.coursework.meCreate assignments on behalf of the teacher
Pro only — requested separately the first time a teacher clicks "Create Assessment in Classroom"
Write (Pro)…/classroom.announcementsPost class announcements
Pro only — requested separately the first time a teacher clicks "Share Quiz to Class"
Write (Pro)Full scope URIs are prefixed with https://www.googleapis.com/auth/
Hard Limits — What We Can Never Do
- Email students or parents directly
- Access Google Drive, Gmail, or any service outside Google Classroom
- Read or modify data from classes the teacher did not select
- Share student data with third parties, advertisers, or AI training datasets
- Perform any write action automatically in the background — every write is teacher-initiated
- Retain Classroom data after account deletion or Classroom disconnect
These limits hold regardless of which OAuth scopes are granted. Write scopes enable teacher-triggered actions only; no background automation is possible.
Data Flow
- 1
Teacher signs in
Google OAuth authentication via your school Google account. We receive an access token and, for offline use, a refresh token.
- 2
Classroom data synced
Class list, student roster, assignments, and submission status are pulled from the Google Classroom API and stored in Supabase (EU, Frankfurt region, AWS eu-central-1).
- 3
AI processing
Risk analysis runs on magistrOS servers. Raw student data is not sent to third-party AI providers. AI-generated text (parent email drafts, assessment content) is generated from anonymised signals and your own prompts.
- 4
Teacher reviews and acts
All AI-generated content is reviewed by the teacher before any action. Write-back to Classroom happens only on explicit teacher click.
Data Retention
Classroom data
Kept only while the teacher's account is active and Google Classroom remains connected. Deleted immediately on Classroom disconnect or account deletion.
OAuth tokens
Stored encrypted (AES-256-GCM) in Supabase EU. Deleted immediately when the teacher disconnects Classroom or deletes their account.
AI-generated content
Parent email drafts and assessment content belong to the teacher. Deleted with the account on request.
Analytics
Privacy-friendly, cookieless analytics via PostHog EU. No student data is ever included in analytics. No persistent identifiers.
Security Controls
- HTTPS-only — all traffic TLS 1.2+
- httpOnly CSRF-validated cookies
- AES-256-GCM encrypted OAuth token storage
- EU-hosted infrastructure (Supabase Frankfurt, Vercel EU)
- Google OAuth 2.0 — we never see your Google password
- Row-level security on all database tables
- No student data sent to external AI APIs
- Principle of least privilege — minimal scopes on initial connect
GDPR & UK GDPR Compliance
Data Controller
PRAGMA AI LTD — Company No. 16377226, registered in England & Wales
DPO / Privacy Contact
Legal Framework
UK GDPR + EU GDPR dual compliance. Data processing lawful basis: legitimate interest (risk detection service) and contractual necessity.
Data Subject Rights
Right to access, erasure, portability, and restriction. Exercisable via in-app Settings → Delete Account, or by emailing privacy@magistros.app.
Still have questions?
If you need a Data Processing Agreement (DPA), a custom security questionnaire, or have any compliance questions, email us at privacy@magistros.app. We respond within 2 business days.
Teachers can also try the live demo with synthetic data — no login or Classroom connection required.