Privacy policy

Last updated: 8 November 2026 (children under 13; feedback you send; counting each device once, the device email and the new-device limit); 20 October 2026 (tap counts and answer timing, and how to turn them off; counting the devices a paid account is used on); 4 October 2026 (our own anonymous page counts)

In short: we store only what we need to run your account (email and access), your progress (so you can pick up where you left off) and anonymous aggregate stats. We don't sell your data and we don't run third-party ads. You can have everything deleted by emailing us.

1. Who runs this site?

igcsemathrevision.com is one of the Math Revision sites run by Pete Bromfield in the UK (listed in the footer); they share one sign-in system and database. Questions about your data: pbromfield@ibmathrevision.com.

2. What we store, and why

What	Why	Where
Your email address	To sign you in, save progress and send emails you asked for (receipts, updates, digests).	Firebase Authentication (Google Cloud)
Name and avatar (Google or Microsoft sign-in)	To personalise the site.	Firebase Authentication
Your class, confidence ratings, practice attempts, homework uploads and scores	To show you (and your teacher, if you're in a class) your progress.	Firestore and Cloud Storage (Google Cloud)
Updates email (if you signed up)	To send the revision tips and news you asked for.	Firestore
Your plan and payment records	To unlock your plan, and because tax law requires us to keep receipts.	Stripe (card details never reach our servers) and Firestore (plan status only)
School invoices (when a teacher asks us to invoice their school): the school’s legal name and billing address, the finance contact’s name and email, an optional copy-to email, the PO number and the school’s VAT number or GSTIN, if given	To send the invoice and payment reminders, show it to the school’s Heads of Department, and keep the accounting and tax records the law requires.	Firestore, and Stripe, which issues and emails the invoice.
Your devices: a random device ID your browser makes, a label such as “Chrome on Windows” (worked out from the browser’s user-agent, which we don’t keep), when each device was first and last used, and which of our four sites it was used on, and a scrambled code for the network it was used on	Accounts are personal and can be used on up to 5 devices; this is how we count them. To protect paid accounts, we also note how many different devices an account is used on, so we can spot a shared login. So that one phone or laptop counts once, we keep a scrambled code for the network each device was used on (made from the first part of its IP address, and different for every account); we never keep the IP address itself or your location. We keep an eye on account use: if we suspect an account is being shared, we may email you about it, and the account may be paused while we review it. Teacher, school and class accounts are not limited. You can see and remove your devices on your account page. No other fingerprinting.	Firestore; the device ID also sits in your browser’s local storage. A device unused for 60 days is deleted automatically.
Feedback you send: the “Report a problem” form, “Was this useful?” thumbs and comments, and the “Feedback” link. We keep your message or rating, the page you were on, and your email address if you are signed in or give one	To fix problems, improve the site and reply to you. “Report a problem” messages are also emailed to us.	Firestore; “Report a problem” messages also reach our inbox through Resend.

3. Who else sees your data

Google Firebase: sign-in, database, file storage and cloud functions.
Stripe: card payments for plans, and the invoices schools ask for (it emails them to the school’s finance contact).
Resend: transactional email.
AI marking (Google Gemini): when you ask for feedback on your working, the question and your answer (or a photo of your working) are sent to Google's Gemini service to generate that feedback. We don't use them to identify you.
Emergent (emergentagent.com): stores some uploaded files, such as photos of written work and class handouts.
Crisp (crisp.chat): the live chat. Nothing from Crisp loads until you press “Chat with us”. Then Crisp's chat window loads from Crisp's servers, keeps a chat session ID in your browser and, if you send a message, stores it and any email address you give.
ipapi.co: only if you click “Accept all” in the cookie banner: at most about once an hour per visit, our site asks this geolocation service for the approximate location of your internet connection and records the country and city with the page you visited, so we can see where visitors come from. We don't store coordinates or link it to your account.
Your teacher: if you join a class, your teacher sees your progress for that class.

No advertising networks, no tracking pixels, no profiling.

4. Cookies and local storage

Firebase sign-in storage keeps you signed in.
Google Analytics runs only if you accept analytics cookies in the banner.
Our own page counts — to see which parts of the site help and what is broken, each page sends us a small anonymous note when you leave it: the page address, where the visit came from (for example Google or another page of ours), which kind of link or button was clicked, menu links used, how far down a long page you scrolled, how fast the page loaded, and any error or “page not found”. It has no cookie, no ID and no IP address, is never linked to you or your account, and is only added into daily totals. Only if you click “Accept all”, it also counts what you type into the site search box (never anything with an email address or long number) and which features you used each week (remembered in your browser). Nothing you type into answers or forms is ever sent. Page-level details are deleted after 90 days. Turning on “Do Not Track” or Global Privacy Control in your browser stops it.
Only after you press “Chat with us”, Crisp keeps a chat session ID in your browser (see section 3).
Local storage remembers small preferences (e.g. banner dismissals). It never leaves your device.
Device ID — a random ID in local storage that identifies this browser as one of your (up to 5) devices. It is sent to us only while you’re signed in, with each request, and is deleted from our records when you remove the device or don’t use it for 60 days.
Where you came from — if you arrived from another site or a tagged link (e.g. a newsletter), the site name and campaign tags are kept in your browser for this visit (30 days if you accept analytics cookies), and sent to us only if you sign up for emails, so we know which newsletters and pages help. We also keep the page you first arrived on and the type of site that sent you (a search engine, another site, or none), and add them to your account once when you create one, so we know which pages help people join. If you tapped one of our sign-up buttons in the same tab just before, we add which one (a short tag naming the button, and the page it was on). Not with Do Not Track or Global Privacy Control switched on.

Help improve the site: tap counts and answer timing

Two more things help us improve the site. Both are on unless you turn them off.

Tap counts. On about one page view in four, the anonymous note above also lists which links and buttons on the page were tapped, named by the part of the page they are in and the name we gave them in our code. Now and then it also lists the links and buttons the page showed, so we can see what nobody uses. There is no cookie and no ID, nothing about where on the screen you tapped and nothing you type. The counts are only added into daily totals for each page and are deleted after 90 days.
Answer timing. When you answer practice questions while signed in, we note how long you take before your first answer, whether you change your answer and how often you switch between multiple-choice options. We use this only to personalise your practice.

To turn both off: use this switch in each browser you use. Tap counts are anonymous, so they can only be turned off in the browser. To turn answer timing off for your account on every device, email pbromfield@ibmathrevision.com.

5. Data sent outside the UK

Some of the companies that run parts of this site store or process your data outside the UK:

Google (Firebase): sign-in, database, file storage, hosting and our server code. Our server code runs in Google's us-central1 region in the United States, with a few older functions in europe-west1 (Belgium); other Firebase services may keep data in the United States or other Google locations.
Google (Gemini API): AI marking and feedback, which may be processed in the United States or other countries.
Stripe: card payments, processed in the United States and other countries.
Resend: a US company that delivers our emails, so your email address and the email itself are processed in the United States.
Emergent (emergentagent.com): storage for some uploaded files; its servers may be outside the UK.
Crisp (crisp.chat): live chat, only if you press “Chat with us”; its servers may be outside the UK.
ipapi.co: visitor location lookup, only if you accept analytics cookies; its servers may be outside the UK.

How we protect it: each provider gets only what it needs for its job; every connection to them is encrypted (HTTPS); card details go straight to Stripe and never reach our servers. We use each provider under the terms it offers its customers, and each publishes its own privacy terms. If you'd like to know more about a transfer, email us.

6. How long we keep it

Account and progress data: until you ask us to delete it. Payment records: as long as UK tax rules require. School invoice details: as long as needed for accounting and tax records. Updates emails: until you unsubscribe or ask us to delete them.

7. Your rights (UK GDPR)

You can ask for a copy of your data, a correction, deletion (within 30 days) or a machine-readable export, and you can complain to the UK Information Commissioner's Office. Email pbromfield@ibmathrevision.com to use any of these rights.

8. Children and younger students

Most IGCSE students are under 16. Children under 13 can use the site only with a parent’s or guardian’s consent, or through their school. A school that signs up its students does so under its school agreement with us, and the school gives any consent needed. We don’t ask your age when you sign up, so if you are under 13, ask a parent or guardian before you create an account. If we learn that a child under 13 has an account without that consent, we close it and delete its data. A parent can email us at any time to see or delete their child’s data.

A parent or guardian the student links (or approves) sees their practice, topics, homework and test scores on a read-only parent dashboard and can choose a weekly summary email of the same. That email is off until the parent turns it on; the dashboard first says what it contains and how to stop it, it carries no advertising, and we record when it is turned on or off and which notice was shown. It stops from the dashboard or the one-click link in any email. The student can stop sharing with a parent at any time from their account page.