Privacy Policy

Google/Microsoft OAuth

• Email address and name during sign-in flow

Payment Information (Individual Subscribers)

• For individual paid subscribers, Stripe provides transaction and subscription status
• Not used for school pilot users
• We never directly handle credit card details

To Provide the Service

• Generate personalised questions
• AI-powered grading for typed and handwritten work
• Track progress and performance
• Provide hints and solutions
• Deliver class assignments and teacher reporting

To Improve the Platform

• Analyse anonymised aggregate usage patterns
• Calibrate question difficulty
• Develop new content
• Improve adaptive learning algorithms

For Security

• Prevent abuse
• Enforce usage limits
• Detect fraudulent activity
• Maintain service stability

For Communication

• Transactional emails (password resets, account notifications) via Mailgun through Supabase Auth

Retention Period

Data is retained for the duration of your use of the service to support ongoing learning and teacher reporting.

Deletion on Request

Full deletion is available on request. Deletion is comprehensive, with cascading removal across 30+ database tables including:

• User account and profile
• Role and access records
• Class enrolments
• All question attempts, submissions, and grades
• Uploaded handwritten work (images and PDFs in storage)
• Learning model data and AI-generated summaries
• Provisioning records

Deletion Timeline

• Production deletion is immediate upon request
• Encrypted database backups are retained for 7 days, then auto-expire
• Server request logs are retained for 30 days (metadata only, not answers or grades)

Self-Service Deletion

Students and teachers can delete their own accounts via the Settings page, which triggers the same comprehensive cascading deletion.

Anonymised Data

Irreversibly anonymised aggregate statistics (where no individual is identifiable) may be retained.

Data Required by Law

Notwithstanding the above, data that is required to be retained by applicable law or regulation will be kept for the minimum period required and then deleted.

Encryption

• In transit: TLS 1.2+ on all connections (browser-to-server and server-to-database)
• At rest: AES-256 encryption on all stored data

Server-Side Only Architecture

The browser never directly accesses the database. All data access flows through authenticated, permission-checked server-side API routes. Database credentials are server-side secrets and never reach the client.

Database Security

• Row-Level Security (RLS) enabled at the database layer as defence-in-depth
• Pseudonymised UUIDs used in all analytical and learning data (not names or emails)
• All database queries parameterised to prevent SQL injection

Vendor Access Controls

• Production access restricted to 2 personnel (CEO and CTO)
• Multi-factor authentication enforced on all infrastructure accounts
• Database credentials and API keys rotated on a quarterly schedule
• Audit logging via platform trails (Supabase database logs and Vercel access logs)

Incident Response

In the event of a confirmed data breach, affected schools will be notified within 24 hours in accordance with the Notifiable Data Breaches scheme under the Privacy Act 1988. Incident response includes immediate containment, root cause analysis, patching, and verification before restoring service.

Access (APP 12)

You can view your own data at any time through the platform. Students can see their own submissions, grades, and progress. Teachers can see performance data for students in their own classes.

Correction (APP 13)

You can update your profile information at any time. If you believe any data we hold about you is inaccurate, please contact us and we will correct it.

Deletion

You can request deletion of your data at any time via the Settings page or by contacting us. Deletion is comprehensive and removes all associated records across 30+ tables.

School Deletion

For school pilots, the school may request deletion of all school data at any time. Individual student or teacher records can also be deleted independently without affecting the rest of the school's data.

What We Use

• Secure HTTP-only session cookies for authentication
• Essential cookies only — not used for advertising or cross-site tracking
• Session tokens validated server-side on every request

What We Do Not Use

• No third-party advertising cookies
• No social media tracking pixels
• No behavioural tracking
• No browsing history or location data collected

Data Stored in Australia

All persistent data is stored exclusively in Sydney, Australia. No student data is replicated to overseas data centres.

Limited Cross-Border Processing

• AI grading requests may be processed outside Australia (OpenRouter) — designed to exclude identifiers, stateless, zero retention by the provider
• Transactional email via Mailgun (US) — only the recipient email address is sent
• Google/Microsoft OAuth — global during sign-in flow only
• Stripe payment processing (individual subscribers only) — global, per Stripe's data policy

14.1 AI Grading

When you submit an answer (typed or handwritten), the question, its solution, and your response are sent to an AI provider via a server-side API call for grading. For handwritten submissions, the image or PDF of your work is sent for vision-based grading and OCR extraction.

• Processing is stateless with no data retention by the AI provider
• Identifiers are not intentionally sent (would only appear if you write your name in your submission). For AI-generated teacher summaries, the student's first name may be included for contextual reporting. No other identifiers (email, school, etc.) are sent.
• Each request is completely independent — no conversation history or session memory
• AI providers are contractually prohibited from using data for training

14.2 Adaptive Learning

Leibniz uses a statistical model to personalise question difficulty. This model operates on pseudonymised data (UUIDs, not names or emails) and stores only mathematical parameters representing estimated mastery per concept.

• Any model tuning uses anonymised, aggregated data only
• Schools may opt out of having their data included in aggregate analyses

14.3 Progress and Teacher Reporting

For class-assigned work, your progress is visible to your assigned teacher and school administrator (see Section 4). Anonymised aggregate statistics may be used to improve the platform (school opt-out available).

14.4 Device Fingerprinting

Device fingerprinting is used for free and guest users only to enforce daily question limits.

• Not collected for school-provisioned Pro users
• Data used for rate limiting only

14.5 School Pilot Provisioning

For school pilots, the onboarding process works as follows:

• The school provides an email whitelist for students and teachers
• On first login, the system matches the user's email, assigns the appropriate role, and activates Pro access
• Teacher access is granted only to approved, school-provided addresses
• Students can only join classes belonging to their own school — cross-school access is blocked