GCSE App

Privacy Policy

A short, plain-English explanation of what GCSE App does and doesn't do with your information.

Effective 31 August 2026 uk.co.londonjobs.gcseapp

The short version

01 What we collect

GCSE App is built to work almost entirely on your device. When you first open the app, you're asked for a display name so your progress screen can greet you — that's stored only in the app's local storage on your phone.

We do not collect your name, email address, location, contacts, or photos on any server, and the app requires no account or sign-in. The one exception is described in full below: if you choose to use AI examiner feedback, the specific answer you're checking is sent for processing, as explained in section 3.

02 What's stored, and where

DataWhere it livesEver leaves your device?
Display name, study streak, XP, levelLocal device storageNo
Flashcard review history & scoresLocal device storageNo
Premium unlock statusLocal device storage + Google PlayOnly to Google, to verify your purchase
Payment card detailsGoogle PlayNever seen by us at all
An answer you submit for AI examiner feedbackNot stored anywhereYes — only that answer, only when you tap the feedback button, see section 3

All app content and progress use a local storage library (MMKV) that keeps data on your device only. Uninstalling the app permanently deletes it — there is nothing left on any server for us to retain or delete on your behalf, because we never had it.

03 AI examiner feedback (only when you use it)

Blurting Arena and Exam Practice let you write free-text answers to exam-style questions. Instant scoring against the mark scheme happens automatically, entirely on your device, using no AI and sending nothing anywhere.

Separately, on the results screen, there's an optional button: "Get AI examiner feedback." Nothing is sent unless you tap it. If you do, the following is sent over an encrypted connection to our own backend relay and on to Google's Gemini API for processing:

This is not linked to your name, an account, or any device identifier when it reaches Gemini — it's sent only to generate a mark and one line of feedback, and is not stored on our own servers beyond the moment needed to relay that response back to the app. All AI requests use stricter-than-default child-safety content filters. See Google's Gemini API terms: ai.google.dev/gemini-api/terms.

If the feature is unavailable (no connection, or the service is down), the app tells you and lets you retry — your instant, offline mark-scheme score is unaffected either way.

04 In-app purchases

Unlocking premium topics is handled entirely through Google Play Billing. When you make a purchase, Google processes your payment and tells the app whether you're entitled to premium access — we never see or store your card details, billing address, or any other payment information.

05 Advertising & tracking

GCSE App contains No ads No analytics No third-party trackers

We don't use advertising SDKs, analytics platforms, or crash-reporting tools that collect usage data. The app doesn't know — and we don't know — how you use it beyond what's stored locally on your own device and the specific answer text described in section 3.

06 Children's privacy

GCSE App is designed for GCSE-age students (roughly ages 13–16) revising for exams. The app requires no account and collects no personal information on any server. The only data that ever leaves the device is the specific answer text a student actively chooses to submit for AI examiner feedback (section 3) — never a name, contact detail, or any other identifying information, and never automatically.

If you believe a child has submitted personal information within an AI-marked answer, contact us and we'll help — though because that data isn't stored on our servers at all, there's nothing on our end to delete; the request would need to go to Google, whose terms are linked in section 3.

07 Changes to this policy

If GCSE App ever adds a feature that changes what data it collects (for example, an optional cloud sync), this page will be updated first, with the effective date above revised accordingly.