Privacy Policy

ReviseWithAI is aimed at students roughly aged 13–18, most of them 16–18, so many of our users are under 18 and some are under 16. We don’t ask for a date of birth or check age at signup: an account needs only a first name, last name, email address, username and password. Because we can’t tell who is under 18, we apply the ICO’s Children’s Code protections to every account (see section 10).

ReviseWithAI is not intended for children under 13 to use on their own. If you are under 13, a parent or guardian should set up and manage the account with you. A parent or guardian who believes their child has given us personal data without suitable involvement can contact us (section 12) and we will remove it.

• Account details: first name, last name, email address, username, and a password (stored as a salted hash, never in plain text).
• A record that you accepted the Terms of Service and Privacy Policy when you registered: the date and time, and the version (currently 2026-10-01).
• Study data: the subjects, exam boards and topics you choose, your quiz answers, marks and feedback, scores, exam dates and study plans, and the notes you add or upload.
• Content you upload for the notes feature: pasted text, uploaded files, or content imported from Notion. Uploaded files are held only in a temporary file while they are processed and then removed; we keep the text we extract, not the file. If you connect Notion, we store an encrypted access token (encrypted at rest), not your Notion password.
• Usage data: which questions and quizzes you’ve completed, so we can schedule what to revise next, and a daily summary of your activity (quizzes done, time spent, topics studied).
• Friends: while a friend request is waiting to be accepted, the other person sees only your username, whether you sent the request or received it. Once a request is accepted, that friend can see your username and first name, and your score on your private friends leaderboard (section 10).
• Subject waitlist: if none of the subjects you pick before signing up is covered yet and you choose to join the waitlist, your email address, your level (for example GCSE) and the subjects and exam boards you picked. Joining the waitlist does not create an account.
• Billing: paid plans are handled by Stripe. We receive a customer and subscription reference, the plan, dates and status, not your card details. If someone else pays for you, we also store the payer’s numeric account id and, for a payer without an account, their email address.
• Your preferences (for example email settings).
• Feedback you send through the feedback form: the message, the name and email address shown on the form (pre-filled from your account, and you can change them), and the page you were on.
• Server logs (for example IP address, time and requested address) created by our servers and by Cloudflare for security and diagnosis. Error alerts we generate are scrubbed of personal data before they leave our servers (section 3).
• Advertising measurement: our website loads Google’s advertising tag (Google Ads), which sends Google information about your visit, such as the page address, your IP address and browser details, whether you arrived from one of our Google ads, and whether you signed up (section 4).
• Cookies and browser storage: see section 4.

UK GDPR requires a lawful basis for each use of your data. Here’s what we do and which basis applies:

• Running the product: creating your account, generating quizzes, marking your answers, and deciding what to show you next (contract).
• AI marking, question generation and note processing, performed by OpenAI’s API. We send OpenAI the question, the mark scheme and the text of your answer, or the text of your notes with the subject, exam board and topic name. We do not send your name, email address, username or account id. Because you type your answers and notes, please don’t put personal details about yourself or other people in them (contract).
• Service emails, sent through Mailgun: the email verification code when you register, the code when you change your email or reset your password, purchase confirmations and receipts, payment-failed notices, and the emails around parent-purchased plans (a request to a parent, a confirmation to the parent, a notice to the student that a plan has been bought for them, and an invitation to a student who has no account yet). These are needed to provide the service (contract) and to keep it secure (legitimate interest). Some of these go to people who don’t have an account with us, such as a parent or an invited student; section 7 explains our basis for those. If a payment fails, Stripe may also email the payer itself.
• Daily summary email: on days you have studied, we email you a short summary of your quizzes, study time, topics and scores. It is on by default. Our basis is legitimate interest: helping you keep up your revision routine, which you would reasonably expect from a revision service and which uses only data you have already given us. It contains no advertising or offers. Every one of these emails has an unsubscribe link, and you can turn it off at any time in Settings (“Daily Revision Reminders”). You have an absolute right to object (section 9). Settings also has switches for exam reminders and weekly progress emails; we do not currently send those. If we start, they will work the same way.
• We do not send marketing email.
• Payments, via Stripe, which acts as a separate controller (section 5) (contract, and legal obligation for the accounting records that follow).
• Security and abuse prevention: rate-limiting sign-in and password-reset attempts, limiting how much AI marking one account can use each month (a fair-use protection), and blocking abuse of paid features (legitimate interest).
• Error and resource alerts: when the service fails, an automated alert is posted to a private Discord channel that only the developer can see. Alerts contain the type of error and the route involved, and are scrubbed of personal data such as names, emails, tokens and request contents. Crash reports from your browser may also go to our error-tracking provider (Sentry) and to PostHog (see below), with personal data stripped and no session replay (legitimate interest in keeping the service working).
• Measuring how the product is used: our own servers record a few key steps against your account id (signing up, finishing onboarding, starting a baseline test, completing a quiz, a trial ending, starting checkout and paying) so we can count, in totals only, how many people reach each step. This is done by us, with no cookies, and the records are deleted with your account (legitimate interest in understanding and improving the service). We also use PostHog, a product analytics provider, to see which pages and buttons are used and where errors happen. It is set up without cookies or any browser storage, records anonymised session replays of how pages are used (everything you type is hidden, and all text is hidden once you are signed in), and is given only your account id, never your name or email. Before anyone signs up we also count, anonymously, how visitors arrive (for example which ad campaign or website sent them) and how far they get (landing page, sign-up page, sign-up), using a random visit id kept in your browser tab’s session storage: no IP address, contact details or cookies, deleted after 90 days, and not collected at all if your browser sends a Global Privacy Control or Do Not Track signal.
• Measuring our advertising (Google Ads): we advertise ReviseWithAI on Google. Our website loads Google’s advertising tag so we can see how many people arrive from our ads and how many of them sign up, which tells us whether an ad is worth paying for. The tag also lets Google add visitors to audience lists that advertisers can use to show their ads again to people who have visited their site. The cookies it uses are listed in section 4. Google receives this data as an independent controller (section 5) (legitimate interest in measuring and improving our advertising).
• Subject waitlist: we use the email you leave on the waitlist only to tell you when one of your subjects becomes available, and we never send marketing to it. We keep it until we have told you, or until you ask us to remove it by emailing hello@revisewithai.com; if you later create an account and delete it, the waitlist entry for that email is deleted too (consent, which you can withdraw at any time).
• Feedback: when you send feedback, the message, name, email and page are posted to a private Discord channel so we can read and reply (legitimate interest in improving the service and answering you).
• Refunds, disputes and legal claims (legal obligation and legitimate interest).

We don’t use your data for automated decisions that have a legal or similarly significant effect on you. AI marking scores your answers and feeds our revision scheduling, but it only decides what to show you next inside the product. If you think a mark is wrong, tell us and a person will look.

Cookies needed to run the site. We set the cookies below ourselves. None of them is used for advertising, analytics or cross-site tracking. Our own analytics (section 3) store nothing in your browser.

• __Secure-next-auth.session-token: keeps you signed in (up to 30 days; httpOnly).
• __Host-next-auth.csrf-token: protects sign-in forms against forgery.
• __Secure-next-auth.callback-url: remembers the page to return to after sign-in.
• rwai_new_account: shown for 5 minutes after you register so we can greet you once.
• sidebar:state: remembers whether you collapsed the sidebar (7 days), set only when you change it.
• rwai_site_gate: if the site is behind its shared access password, remembers that you entered it (30 days).

Google advertising cookies. Our website loads Google’s advertising tag (Google Ads), which sets or reads these cookies. It is not loaded on pages whose address contains an email address, a link code or a record number (for example invitation and sponsor links), so those addresses never reach Google. We use them to measure traffic from our Google ads and how well those ads perform (how many visitors they bring and how many of those sign up). We don’t use Google Analytics.

• _gcl_au (on revisewithai.com): lets Google link your visit, and a later sign-up, to an ad you saw or clicked (90 days).
• _gcl_aw (on revisewithai.com): set only when you arrive by clicking one of our Google ads, and records that click (90 days).
• GCL_AW_P (on google.com, googleadservices.com and doubleclick.net): set only when you arrive from one of our Google ads, and also records that click (90 days).
• IDE (on doubleclick.net): Google’s advertising cookie, used to measure ads and to show ads to people who have visited a website, including ReviseWithAI (up to 13 months).
• test_cookie (on doubleclick.net): checks whether your browser accepts cookies (a few minutes).

Google may also read or set its own cookies on its own domains (for example google.com and doubleclick.net), particularly if you are signed in to a Google account. Google decides how long it keeps that data, under its own policy: see how Google uses information from sites that use its services and how Google uses advertising cookies.

How to opt out. You can block or delete these cookies in your browser settings, or use a browser or extension that blocks third-party trackers. Blocking them does not affect how ReviseWithAI works. To stop Google personalising the ads it shows you, use Google’s My Ad Centre. The Global Privacy Control and Do Not Track signals switch off our own anonymous visit counts (section 3), but they do not currently switch off the Google tag.

In your browser’s session storage (cleared when you close the tab) we keep your current revision queue, whether you dismissed the subscription banner, and the answers you give while setting up before you sign up (level, subjects and grade-plan answers, removed once you sign up or join the waitlist), and the random visit id and arrival details used for the anonymous visit counts in section 3.

These providers act as our processors (service providers): they handle data only on our instructions, to provide their service to us. Each receives only what it needs:

• Amazon Web Services (AWS), us-east-1, USA: runs our web and API servers, including server logs.
• Cloudflare, USA and global network: proxies traffic to our domain (so it sees your IP address and requests) and routes incoming email sent to hello@revisewithai.com.
• Neon, AWS us-east-1, USA: our managed PostgreSQL database, holding your account and study data.
• Mailgun, USA: sends our emails, so it handles recipient addresses and message content.
• OpenAI, USA: marks answers and generates questions and notes content. OpenAI says API inputs and outputs are kept for up to 30 days for abuse monitoring (unless longer retention is required by law) and are not used to train its models unless the customer opts in; we haven’t opted in. See OpenAI’s data-controls page.
• Discord, USA: receives scrubbed error alerts and the feedback you send (section 3).
• Notion, USA: only if you choose to connect it, to import pages you select.

Stripe (USA and Ireland) takes payments, but is not our processor. Stripe is an independent controller of its own payment, fraud-prevention and accounting records. When you (or someone paying for you) check out, we share the payer’s details and the subscription details with Stripe as a separate controller, and Stripe uses them under its own privacy policy and legal obligations. It keeps those records even after we delete your account (section 8).

Google (Google LLC, USA, and Google Ireland Limited) runs the advertising tag on our website (sections 3 and 4). It is a third party, and not our processor: for this advertising data, Google acts as an independent controller under its Google Ads data protection terms, and uses the data under its own privacy policy. We do not send Google your name, email address, username or study data.

All the providers above process data in the United States, outside the UK. We rely on a safeguard under UK GDPR Chapter V for each:

• AWS (and so our servers and Neon’s hosting): AWS participates in the UK Extension to the EU–US Data Privacy Framework.
• Google: Google LLC participates in the UK Extension to the EU–US Data Privacy Framework, and Google’s data protection terms also include the UK Addendum to the EU Standard Contractual Clauses.
• Cloudflare, Neon, Mailgun, OpenAI, Stripe, Discord and Notion: the ICO’s International Data Transfer Agreement (IDTA) or the UK Addendum to the EU Standard Contractual Clauses, in the provider’s data processing terms. Some of these providers may also be certified under the UK Extension.

You can ask us for more detail on the safeguard for any provider (section 12).

A student can ask a parent or guardian to pay for their plan, or a parent can buy a plan for a named student. The payer’s email address is stored so we can link the purchase, send confirmations, and let them manage it. A payer doesn’t need a ReviseWithAI account. A payer without an account manages billing through Stripe’s portal link or by emailing hello@revisewithai.com. A payer cannot see the student’s study data, answers or notes.

People who give us someone else’s email address, and the people it belongs to. Some email addresses come to us from another person rather than from their owner: the parent or guardian a student asks to pay, and a student a parent invites who has no account yet. We get the address from the student or parent who used the feature. Please only enter an address you are entitled to give us, such as your own parent’s or your own child’s, and not anyone else’s.

Our lawful basis for using these addresses is legitimate interest: completing the purchase or request that the student or parent started, and sending the service emails listed in section 3 (the request, confirmations, receipts, the notice that a plan has been bought, and the invitation). We use the address only for that purpose and never for marketing. If you received one of these emails and don’t want us to hold your address, email hello@revisewithai.com to object or ask us to delete it. An invitation or request that was never linked to an account, and the address on it, is deleted when the account that sent it is deleted (section 8).

We keep your account and study data while your account is active. When you delete your account from Settings, it happens straight away: there is no grace period and no way to undo it. Here is exactly what happens:

Held by others. Stripe keeps its own customer record (including the email entered at checkout), invoices and payment history under its own policy and legal obligations; we can’t delete those because they are tax records. Mailgun and OpenAI keep their own logs for a limited time under their own policies (OpenAI: up to 30 days). Messages you sent to our private feedback channel, and emails you sent to hello@revisewithai.com, are kept for up to 12 months and then deleted.

Logs and backups. Application server logs and web-server logs are rotated daily and deleted after 14 days. System logs are also deleted after 14 days and are capped in size (200 MB). Copies we make on our own server before maintenance are deleted after 30 days. Our database provider, Neon, keeps a rolling 6-hour history of the database so we can undo a mistake, so deleted data can remain in that history for up to 6 hours. We also keep a small number of point-in-time copies of the database (a test copy, and a restore point taken before a major update); data you delete can remain in those copies until we refresh or delete them. We don’t use backups or copies to bring a deleted account back.

The 6-year billing records are removed when they are no longer needed for tax purposes.

Under UK GDPR, you have the right to:

• ask what personal data we hold about you and get a copy of it (access);
• have inaccurate data corrected (rectification);
• ask us to delete your data, subject to the retention in section 8 (erasure), which you can also do yourself from Settings;
• ask us to restrict or object to processing that relies on legitimate interest, including the daily summary email (you can also just turn it off);
• receive the data you gave us in a portable format (portability); and
• complain to the UK’s data protection regulator, the Information Commissioner’s Office, at ico.org.uk, if you think we’ve mishandled your data. We’d appreciate the chance to put it right first.

To use any of these, email hello@revisewithai.com. We’ll normally respond within one month. Under-18s can make these requests themselves.

Because many of our users are under 18 and we don’t check age, we treat every user as though they might be a child and follow the ICO’s Age Appropriate Design Code (the “Children’s Code”) for everyone:

• We collect only what the service needs, and use it only for the purposes in this policy.
• We don’t sell personal data, and we don’t show advertising on ReviseWithAI. We send no marketing email.
• We don’t track your location. Our website does load Google’s advertising tag to measure our own Google ads; section 4 explains what it sets and how to block it.
• There are no public profiles and no public leaderboard. Nobody sees your first name, your score or any study data unless you both accept a friend request. The leaderboard shows only you and your accepted friends, with usernames and scores, and accepted friends can also see your first name. Anyone who knows your exact username can send you a request; while it is waiting they see only your username (and you see only theirs), and nothing more about you unless you accept. You can remove a friend at any time. Please choose a username that isn’t your full name.
• Settings are simple to change, and we explain them in plain language on our young people’s privacy page.
• If you are under 18 we suggest checking with a parent or guardian before buying a paid plan.

If what we collect or how we use it changes in a way that matters, we’ll update this page and the date at the top, and tell account holders by email where the change is significant.

Questions about this policy or your data: hello@revisewithai.com. Operated by Henry Smith, trading as ReviseWithAI (UK sole trader, no company registration number), 14 Norwood Terrace, Ilkley, LS29 7EY.