Privacy, plainly.
What we store, what we don't, who else touches your data, and how to get it back.
About Revise
Revise (revise.alltheway.ing) is developed and maintained by a one-person team as part of the alltheway.education family of educational tools for IB Diploma Programme students. This service is provided to support student learning through active recall, spaced repetition, and teacher-led classroom activities. This policy also covers ess.alltheway.ing, the ESS site, which runs on the same service and shares the same sign-in.
Our commitments to students
Student data on Revise is processed for educational purposes only. Specifically:
- We do not show advertising to students.
- We do not perform behavioural profiling for commercial or marketing purposes.
- We do not sell or rent student data to third parties.
- We do not share student data with third parties except the subprocessors listed below, who act on our behalf and only as needed to deliver the service.
- We do not use student questions, answers, flashcards, or performance data to train artificial intelligence or machine learning models. AI providers used by Revise (notably Anthropic) are contractually prohibited from training their models on data we send via their API.
- We collect only the personal data needed to run the educational service.
Data we collect
When you use Revise, we collect and store:
- Identity — your first name, last name, email address, and profile photo (if any), as supplied by your Google account. We do not ask for your name separately; we read what Google sends. You can instead sign in with any email address: we email you a link and a code, and the first time you sign in that way we ask for your name, since an email address does not come with one. Signing in with Google and by email to the same address is the same account. If your school sets your account up before you first sign in, we create it from the school's class list (your name, school email address, class and exam session), and signing in then links to it.
- Flashcards — the questions and answers you create.
- Study activity — your review history, FSRS scheduling state, streaks, and creation activity.
- AI feedback history — for cards you submit to the quality coach: the AI rating, principle, evidence, and direction line, and the result of the factual accuracy check.
- Card Lab drafts — in a Card Lab lesson, every version of a card you check, including the drafts you rework, so your teacher can see how the class got on (see Teacher and class features).
- Systems diagrams (optional) — in the ESS systems diagram builder, if you choose “Save my work”: each diagram you check, the feedback it got, how many hints you had used and when, so your teacher can see it (see Teacher and class features). Without that choice your diagram stays in your browser and is never sent to us.
- Card sorts and Diamond 9s (optional): if you are signed in, or choose “Sign in to save” where one is shown inside a lesson page: for a card sort, where you had put the cards each time you checked, how many were right at your first check and how many times you checked; for a Diamond 9, your finished diamond. The teacher who made the activity can see these with your name. Without signing in the activity works the same and nothing is saved.
- Capture–recapture (optional): in the ESS capture–recapture game, if you are signed in or choose “Save my progress”: each field site you finish, with the animals you caught and counted, your estimate, your sums on the calculator (each line and whether it was right, and whether you used “Show me”), your prediction, the assumption you named and the points it earned, so your teacher can see who has done what (see Teacher and class features). Signed out, your progress stays in your browser and is never sent to us.
- Exam drawings (optional): in the digital exam drawing tool, if you choose “Save to Revise”: the drawing (its shapes and the picture), its title, the question it answers, any syllabus point you tag it with, and its last 20 saves, so you can find it again under My drawings. For a task a teacher set, also whether you handed it in and the teacher's comment. Teachers who set tasks: the tasks, their starting drawings and who may open them. Without that choice your drawing stays in your browser and is never sent to us.
- Answer Lab responses: if your teacher switches Answer Lab on for you, each response you make to an exam question (the words you highlight, the ideas you jot down, your plan, the markscheme points you tick, how sure you say you are of those ticks and any one-line reflection), the feedback and score it gets, and your level on the ladder. Your teacher sees your responses; other students never do (see Teacher and class features). If you join a live Answer Lab session with the word on the board, the teacher running it sees your name, when you joined, which of its questions you saw and the responses you make in it, even if you are not in one of their classes; the classroom screen shows your work as “Response A”, “Response B” and so on, never with your name. You can offer a piece of your work for the board: the teacher sees that you offered it and how many times you have offered, and still chooses what goes up. The teacher can also cover every student's screen for a few minutes while they talk to the class; your work stays saved. In a live capture–recapture session you play rounds of the ESS game with the class; the teacher running it sees each step you finish (the animals you caught and counted, your estimate, your sums on the calculator, your prediction and the assumption you named) and can put your working on the classroom screen as “Response A”, never with your name; finished rounds also appear on your class's capture–recapture page. In a live essay session you plan an essay step by step (the words you highlight, your three main points with their evidence, explanation and link, your introduction and conclusion); the teacher running it sees your plan, and once it is handed in you get the markband it is heading for and a comment.
- ESS IA coach conversations — if you use the IA coach on the ESS site, what you write to it and its replies, so a conversation can carry on where you left it.
- IA guide progress — the checklist items you tick on the IA guides.
- IA draft feedback and deadlines: if your teacher uses the IA guide with your class, the feedback they write on your IA draft (up to three priorities, the parts of the guide to go back to, and a comment) and any deadlines they set for you alone. You see the feedback once your teacher publishes it; only you, your teacher and the administrator can read it.
- Reference lists (optional): if you use the referencing tool while signed in, the sources you add to your lists (titles, authors, web addresses and dates), so a list is there on any device you sign in on. Only you can see them. Signed out, a list stays in your browser and is never sent to us. When you ask the tool to fill a reference in, only the web address, DOI or ISBN you paste is looked up (on that website, Crossref or Open Library), and nothing about you goes with it.
- Revision reminders (optional) — if you turn reminders on, the address your browser gives us for sending notifications to that device, the type of device, and when we last sent one.
- Preferences — subject and level selections, and assessment dates you add to your calendar.
- Class membership — if you join a class via an invite code, we store the link between you and that class.
- Lab safety agreement — if your teacher sets the lab safety agreement as a ManageBac task: when you first opened the agreement form through the task's link, and whether you have submitted it: Revise reads only the email address and time of each response from the school's responses sheet, never your answers, and uses them only to mark that ManageBac task complete. Nothing from the sheet is stored.
- Known-as name (optional) — in class activities, such as a class ranking's results on the teacher's screen, you are shown by your first name, with the first letter of your surname if a classmate shares it. If you ask on the Settings page to be known by another name, we store the name you asked for; a teacher of one of your classes sees the request and approves or declines it, and an approved name is shown in place of your first name. Your teacher can also set one for you. You can go back to your first name at any time, which deletes it, and it is deleted with your account.
- Name recording (optional) — if you choose to record how your name is said on the Settings page: a voice recording of up to 10 seconds, and any “sounds like” spelling you write. See Name recordings below.
- Class quizzes — when your teacher sends a quiz to your class: the answers you give (and, where a question asks, how confident you said you were in your answer), when you started and handed in, and your score. While you take a quiz, Revise also records each time you leave the quiz page (switch to another tab or app for two seconds or more), for how long, and which question was on screen; the quiz tells you this before you start and each time it happens, and only your teacher sees it. Revise also records how long each question was on your screen, which your teacher sees only as a figure for the whole class (the middle time for each question), to check that a quiz was a fair length. You are not shown your score until your teacher publishes the results, and then only you see it. Your teacher sees every student's answers and scores. If your teacher shows a podium at the end, the top three are shown to the class by first name (or initials), never with scores. If you miss a quiz, your teacher can note why (illness, a trip, or unknown), which only your teacher sees. With your result you also get a short written summary of how you did (see AI usage). Your quiz answers are deleted with your account.
- Practice tests: if your teacher switches them on for you, you can test yourself on a lesson (your teacher may ask you to make and review its flashcards first). Revise keeps the answers you give, whether each was right, your score and when you started and handed in. You see your mark straight away; your teacher sees your practice tests too; other students never do. Nothing about practice tests is sent to an AI service. They are deleted with your account.
- Exam pack traffic lights: before a test, your class's Exam pack asks how sure you feel about each syllabus point, and whether you could answer each exam question your teacher has shared (red, amber or green). Revise keeps your latest choice for each point and question and when you made it, so it is there next time. Only you and your teacher see it. Nothing about it is sent to an AI service. It is deleted with your account.
- How you prepared for a test: after an in-class test, your teacher can add a summary of how you prepared for it to the top of your comment on that test in ManageBac (your school's system): how many syllabus and key term flashcards you made for its lessons against the number set, how many times you reviewed them and on how many days, and how many exam pack steps you completed, all counted up to the start of the test. Only these counts are sent, never your cards. Revise keeps no copy of the summary.
- Reporting a quiz question: if you report a question as wrong from your results, Revise keeps which question, what you said looked wrong and any note you wrote, and tells your teacher (in Revise and in the team chat, with your name). Other students never see it. Reports are deleted with your account.
- Cards sent for teacher review — if you opt to send a card for feedback, your teacher sees the question, answer, and the AI evaluation at the time you sent it.
- Technical metadata — basic sign-in timestamps and request logs needed to operate the service.
We do not ask you for special-category personal data (e.g. health, religion, ethnicity). You control the content of your flashcards; please do not enter sensitive personal information. Teachers may also keep their school's own records about their classes in Revise's staff tools; those are held for the school under the school's own privacy notice, and are not covered by this policy.
Browser extension (flashcard capture)
Revise offers an optional Chrome extension, “Revise flashcard capture”, that lets you turn a sentence you have highlighted while reading into a flashcard. Installing it is entirely optional and it is not required to use Revise.
- What it captures, and when. The extension reads selected text from the current tab only at the moment you click its toolbar icon. It does not track your browsing, does not read pages in the background, and does not run on web pages except to read the text you have deliberately highlighted when you click it.
- How the text travels. The highlighted sentence is stored briefly in the browser's local extension storage and handed to the capture page on revise.alltheway.ing. It is never placed in a URL. Once the capture page receives it, the temporary copy is cleared.
- What happens to it then. On the capture page you choose a syllabus point and ask Revise to draft a card. At that point the highlighted text and the chosen syllabus point are sent to Revise's backend, which uses Anthropic's Claude API to draft a card and grade its quality — exactly the same flow as in-app card coaching (see AI usage below). Text from cards you discard is not stored; only cards you choose to add are saved to your deck.
- Permissions, and why.
activeTabandscriptinglet the extension read your selection from the tab you clicked on.storageholds the selection just long enough to hand it over. The host permission forrevise.alltheway.inglets the extension open the capture page, deliver the selection to it, and check whether you are signed in. - No tracking. The extension contains no analytics, no advertising, and no third-party trackers, and it holds no API keys — all AI calls happen on Revise's server, never in the extension.
Age of users and minors
Revise is designed for IB Diploma Programme students, who are typically aged 16–19. Access is provided through school classes, and students sign in with their own Google accounts (commonly issued by the school) or with a link emailed to their school address.
Where schools enrol students under 16: in the school context, the school is the data controller and is responsible for obtaining any parental or guardian consent required under local law before inviting minors to the service. Revise acts as a processor on behalf of the school. Revise itself does not collect parental consent directly — schools should treat this notice as part of the information they share with parents when seeking that consent.
Where a student signs up independently (i.e. not through a school class), the student is the data controller of their own data and is responsible for confirming they are of an age at which they can lawfully consent to use the service under their local jurisdiction.
We do not knowingly collect data from children under 13. If you believe a child under 13 has created an account, please and we will promptly delete the account and associated data.
Teacher and class features
Teachers can create classes and invite students via shareable codes. If you join a class, your teacher can see your study progress (card counts, review activity, streaks, AI quality ratings) and, where you choose to send a card for review, the content of that specific card. Teachers do not have routine read access to the full content of your flashcard deck unless you explicitly send cards to them. If you have recorded how your name is said, the teachers of the classes you are in can play it. After a Card Lab lesson your teacher sees how the class got on as numbers (how many tries a card took, which rules came up most), never the text of your drafts. When your teacher sends your class a quiz, they see each student's progress, answers and score; you see only your own result, once they publish it. If you save your systems diagrams, the teachers of your ESS classes see each diagram you checked and the feedback it got; other students never do. If you save your capture–recapture rounds, the teachers of your ESS classes see each round you finished, with your numbers and working; other students never do. If you hand in an exam drawing to a task, the teacher who set the task sees your name and that drawing (the page names them before you hand in) and can return it with a comment; if the task says so before you hand in, they may also show your drawing to the class on screen alongside everyone else's, without your name. Your other drawings stay private. In Answer Lab your teacher sees each response you make, its feedback and your level, and may keep notes about your responses for themselves: the notes are not shown to you in Revise, but they are included in your data export. Teachers can also schedule lessons, manage exam questions, and run collaborative activities (whiteboards, card sorts, etc.) with their classes.
On the IA guides, the teacher of a class the guide is set for sees how many checklist items each student has ticked (never what they wrote), whether an ESS student has sent their three lines, and can write each student feedback on their draft and set them their own deadlines. A student sees their feedback on the guide once the teacher publishes it.
Class ranking (a lesson activity: students put a set of items in order, or say where they stand on each from 1 to 5, then discuss the results): when a teacher sets a ranking on a lesson, you take part signed in to Revise, and Revise keeps your name from your account, a link to your account and your answer (the order you put the items in, or the number you gave each one). A teacher can also give out a code so people without a Revise account can join; then Revise keeps the name you type, your answer, and a random code stored in your browser so you can change it. If you are signed in when you join with a code, your name comes from your account as on a lesson. Nobody sees a ranking until the teacher shows the results. Then the class sees the results without names; only the teacher's screen shows names, with who ranked most alike and most differently, so the teacher can pair people up to discuss. Nothing is sent to an AI service. A ranking set on a lesson, with every name and order in it, is kept until the end of the school year it was started in (it is deleted on 1 September); a ranking joined by code is deleted 30 days after it was started.
TOK essay workspace (tok.alltheway.ing/essay, for students in a TOK class whose teacher runs it): Revise keeps what you write in the lessons' answer boxes (with up to 20 earlier versions of each answer, so that you can get one back), the link to your essay's Google Doc, and which lessons you have opened. Your TOK teacher sees all of it for each student in the class, and a page that shows where two students' titles, examples or wording are alike (a simple count, with no AI); other students never do. Your essay itself stays in your own Google Doc: Revise stores only the link, and never opens, reads or sends the Doc or its text. Nothing is sent to an AI service. All of it is deleted one year after the exam session it belongs to (for the May 2027 exams, on 31 May 2028).
TOK lessons on the site (tok.alltheway.ing/lessons, for students in a TOK class whose lessons are there, the TOK essay's lessons included): you write your answers on the lesson page, and Revise keeps them (with up to 20 earlier versions of each answer, so that you can get one back) and which lessons you have opened. Your TOK teacher can read everything you write in a lesson, as you write it: each answer as it is saved, how much you have written, and when you last wrote. This is on purpose, and it is for your benefit. TOK is learned by thinking in writing, and a teacher who can see the class's thinking during the lesson can notice who is stuck and help at once, pick up a misunderstanding before it settles, choose answers worth discussing, give feedback on what you actually wrote, and write reports that rest on your work across a unit, not on one piece. Other students never see an answer unless it is on a question's class board. An answer reaches the board in two ways: you press “Share with the class” under it (a copy is put up, and you can take it back), or your teacher puts it up. Either way the board never shows names, and the class sees a board only when your teacher shows it. Revise keeps a record that you chose to share, which your teacher sees and which counts in your favour as a sign of taking part; it stays if you take the answer back. During a lesson your teacher may open the page one section at a time, and some answer boxes do not accept pasted text, so that what is written there is typed there. Some questions are answered by choosing: a class vote, a quick check, or how sure you are of an answer. Your teacher sees what each student chose, for the same reasons; the class sees only how many chose each option of a vote, never who, and only when your teacher shows the result. Your teacher can also cover every screen for a moment to bring the class's attention to the front (“Eyes on the front”); your work stays saved, and the page comes back by itself. For a single lesson your teacher may note that you were absent, or that your computer was not working, so that the lesson is not waiting for answers you could not give; only your teacher sees the note. Nothing you write in these lessons is sent to an AI service. All of it is deleted one year after the exam session your class belongs to (for the May 2028 exams, on 31 May 2029).
Name recordings
Students can record how their name is said, so their teachers say it right. Recording is optional: nothing is recorded unless you press Record on the Settings page.
- Microphone. Revise asks your browser for the microphone only when you press Record, and releases it when you stop. Revise can use the microphone only on its own pages, and on no other page.
- Who can hear it. You, and the teachers of classes you are an active member of, plus the site administrator (see Administrator access). Other students cannot hear it. When you leave a class, that class's teacher can no longer play it.
- Where it is kept. In a private Supabase storage area in the European Union (Frankfurt), which can only be reached through Revise's own checks. Each play uses a link that expires after 5 minutes.
- What is done with it. It is played back, and nothing else. When it plays, your browser evens out the volume and trims the silence; the stored recording itself is not changed. It is never sent to an AI service or any other third party, and it is not used to recognise or identify you by your voice. If your teacher sets a task in ManageBac (your school's system) asking you to record it, Revise marks that task complete once you have; the recording itself never leaves Revise.
- How long it is kept. Until you delete it or record a new one (the old recording is deleted as soon as the new one is saved), and never beyond your account: deleting your account deletes the recording too.
- Your control. You can listen to it, record it again or delete it at any time from the Settings page. It is included in your data export.
How we use your data
Your data is used solely to provide the flashcard, spaced-repetition, and classroom service. We use your study history to calculate optimal review intervals using the FSRS algorithm. We do not sell, rent, or share your personal data with third parties for marketing, and we do not use it to train AI models (see Our commitments to students above).
Subprocessors
We use the following third-party services to deliver Revise. Each one acts as a subprocessor and processes only the data needed for its stated purpose.
| Service | Purpose | Processing location |
|---|---|---|
| Supabase | Database, authentication, file storage, real-time collaboration | European Union (AWS eu-central-1, Frankfurt) |
| Vercel | Web hosting, deployment, and the server code that handles your data; cookieless page-view counts and page-speed measurements (Web Analytics, Speed Insights) | European Union (Frankfurt) for server code, with global edge caching of static assets. Vercel is a US company. |
| Sign-in (OAuth) — receives your sign-in request and returns your name and email | United States | |
| Anthropic | AI evaluation of flashcard quality and factual accuracy, Card Lab, the ESS IA coach and its summaries, teacher review suggestions, drafting and choosing class quiz questions (no student data), writing each student's quiz summary from their answers (no names), feedback on Answer Lab responses and live essay plans (the plan only, no name), drafting Answer Lab planning notes for exam questions (no student data), answering searches on the ESS, TOK and EE sites and geographyalltheway.com (the search text only). API data is not used to train models. | United States |
| OpenAI | Text-to-speech for syllabus points and the read-aloud on the IA guides, and turning the ESS, TOK and EE sites' and geographyalltheway.com's published pages and the searches typed into them into the numbers the search matches on. Only published text and search text are sent, never who searched. | United States |
| Resend | Transactional email (sign-in links and codes, bug reports, contact form, teacher invitations, an email to someone who has asked for a teacher account, and a check-in email to new teachers a week after approval, asking whether they need help; a copy of each is kept with the account) | United States |
| Zulip (Kandra Labs) | The administrator's private notifications: bug reports, contact messages, suggestions and teacher access requests; cards sent for teacher review (student name and the card's question); streak milestones (student name); quiz questions a student reports as wrong (student name and the question); practice tests handed in (student name, class, lesson and score); the ESS IA coach summary (which students used it, and anything a teacher should follow up); and a daily note of new accounts and activity from people outside the administrator's own classes (name, email, class, and how many cards, reviews and coach questions) | United States |
| Apple, Google, Microsoft, Mozilla push services | Deliver revision reminders to your device, only if you turn them on. Your browser chooses the service. The message is encrypted, so the service cannot read it. | United States |
| Notion | Source of lesson content and key terms managed by the teacher. No student data is sent to Notion. | United States |
| Raindrop.io | Source of weekly featured articles, videos, podcasts. No student data is sent to Raindrop. | European Union (AWS, Frankfurt) |
| Felt | Map rendering for the Examples → Felt map feature (admin only) | United States |
| Spotify | Embedded podcast playback (Spotify's own embed terms apply) | European Union / United States |
If you have a specific question about a subprocessor or want to see the relevant Data Processing Agreement (DPA), please .
Where your data is hosted
Personal data is stored exclusively in the European Union.
- Production database and files — your account, flashcards, study activity, class records, and name recordings are stored in Supabase in the European Union (AWS eu-central-1, Frankfurt, Germany).
- Backups — automated backups are managed by Supabase and remain in the same EU region. Retained for 7 days.
- Bookmarks source — the Raindrop.io account used for curating weekly resources is hosted in the European Union (AWS, Frankfurt). No student data is sent to Raindrop.
The web application itself runs on Vercel and is delivered via Vercel's global edge network. The edge nodes cache static assets (HTML, JavaScript, CSS, images) but do not store any personal data. The server code that handles personal data (database queries, authentication, AI evaluation) runs in Vercel's Frankfurt region, next to the database, not at the edge.
International data transfers
Our primary data store and error monitoring are hosted in the European Union (see Subprocessors above). However, some subprocessors are based in the United States — namely Anthropic, OpenAI, Vercel, Google, Resend, Zulip, Notion, Felt, Spotify, and the push services that deliver revision reminders. Where personal data is transferred outside the European Economic Area, the United Kingdom, or Switzerland, we rely on:
- EU–US Data Privacy Framework (and its UK extension / Swiss adequacy decision) where the receiving organisation is certified. Google, Vercel, and Anthropic are DPF-certified at the time of writing; we periodically verify this against the official DPF list.
- Standard Contractual Clauses (SCCs) — the European Commission's 2021 modules, together with the UK International Data Transfer Addendum and Swiss-equivalent clauses — in each subprocessor's data processing agreement where adequacy or DPF certification does not cover the transfer.
- Supplementary technical and organisational measures — encryption in transit and at rest, role-based access control, and the data-minimisation principle: we send each subprocessor only the data it needs to do its job. For example, the AI providers receive what you wrote but not your name, email, or session cookies.
Subprocessors based in the European Union (Supabase, Raindrop) do not require transfer mechanisms because the data does not leave the EEA.
Security measures
We use the following technical and organisational measures to protect your data:
- Encryption in transit — all traffic to revise.alltheway.ing is served over HTTPS/TLS.
- Encryption at rest — Supabase encrypts the underlying Postgres database and storage volumes at rest.
- Access control — database-level row-level security (Supabase RLS) restricts each user to their own data; teacher access to student data is scoped to active class memberships; one named administrator has elevated access (see Administrator access below). Name recordings cannot be read from the database by any user directly: they are reached only through server routes that check the request first.
- Authentication — sign-in is delegated to Google OAuth; we never see or store your Google password.
- Backups — managed automated backups via Supabase, in the same region as the production database.
- Environment segregation — development, preview, and production environments are isolated. Production uses a dedicated Supabase project and a dedicated set of secrets stored in Vercel's encrypted environment-variable store. Preview deployments cannot read or write production data.
- Strong administrator authentication — the administrator account signs in via Google OAuth and has two-step verification enabled on the underlying Google account. There is no password-based login path that bypasses this.
- Vulnerability management — dependencies are tracked by GitHub Dependabot, which raises alerts and pull requests for known vulnerabilities. Critical and high-severity advisories are reviewed promptly. The platform is patched on a continuous basis through Vercel deployments.
- Rate limiting — AI evaluation, grading, and other endpoints are rate-limited to prevent abuse.
AI usage and automated decision-making
Revise uses AI in these ways, all through Anthropic's Claude API:
- Flashcard quality coaching. When you submit a flashcard for evaluation, the question, answer, and related syllabus point are sent to Anthropic's Claude API. The model returns a traffic-light rating (green / amber / red), a principle from a fixed 7-rule taxonomy, an evidence quote, and a direction sentence.
- Factual accuracy check. At the same time, a second check looks for factual errors. A card with a clear error is held out of your revision sessions until it is corrected, so you do not learn something wrong; editing the card checks it again. Cards you import are checked the same way, usually overnight.
- Card Lab. The same coaching, used in a lesson, with spelling and grammar notes alongside.
- Answer Lab. When you submit a response, the question with its figures, its markscheme and your response (what you highlighted, your dump and your plan, without your name) are sent to the Claude API, which says which markscheme points the plan would earn and why marks were missed. It comments on your response; it never writes an answer. Your teacher can change its verdict. In a live essay session, your handed-in essay plan (without your name) is sent with the question's markscheme and markbands, and the reply names the band it is heading for and what would lift it.
- ESS IA coach (beta). When you ask the coach a question, what you write, your earlier messages in that conversation, and the step of the guide you are on are sent to the Claude API. It coaches; it does not write your work. Three times a day the administrator receives a summary of the coach's use: students are labelled “Student 1”, “Student 2” in what is sent to Anthropic to write it, and the names are added back in Revise afterwards.
- Search on the ESS, TOK and EE sites and geographyalltheway.com. What you type in the search box (ess.alltheway.ing, tok.alltheway.ing, the EE guide on ee.alltheway.ing, or geographyalltheway.com) is sent to Anthropic's Claude API, with passages from the site's own pages, to write a short answer that links to those pages, and to OpenAI to match it against them. Nothing about you is sent with it. The search text is kept for 12 months, without your name, account or address (only whether you were signed in), so the administrator can see what students look for and what the site is missing; it is then deleted. On geographyalltheway.com the written answer is for subscribers: that site tells Revise only that the searcher is a subscriber, with a code that limits how many searches one subscriber can make in an hour and cannot be traced back to them, never their name, email or account.
- Teacher review tools. When a teacher reviews a card you have sent them, they may use AI helpers to generate rewrite suggestions, split a bundled card into atomic cards, or re-evaluate under the latest grading rules.
- Quiz summaries. When your teacher closes a class quiz, your answers to it, with the questions, the right answers and their explanations, are sent to Anthropic's Claude API to write you a short summary: what you did well, what to fix, and a next step. Your name and nothing else about you is sent. Your teacher can read it, and you see it with your result once they publish.
- Class quiz questions. A teacher can ask Claude to draft quiz questions from their own lesson pages, and to choose questions for a quiz from their question bank. What is sent is the teacher's request, the lesson pages and syllabus, and the questions in the bank (with, for choosing, whether a class has already answered each one). Nothing about any individual student is sent. Every drafted question is read and approved by the teacher before any student sees it.
Your name and email address are not sent with anything you write. In every case, data is processed under Anthropic's privacy policy and Anthropic's API terms prohibit using API content to train Anthropic's models.
No automated decisions with legal or similarly significant effects are made. AI ratings are pedagogical signals to help you and your teacher think about card quality; they do not determine grades, school placements, or any other consequential outcome. Teachers retain full discretion over educational decisions.
Cookies and tracking
Revise uses only strictly-necessary cookies. We do not use advertising, marketing, or third-party analytics cookies, and we do not embed any third-party tracking scripts.
Specifically:
- Authentication cookies set by our authentication provider (Supabase) to keep you signed in and to refresh your session. These are first-party, secure and same-site, and are shared by revise.alltheway.ing, ess.alltheway.ing and tok.alltheway.ing so one sign-in works on all three. Revise's own pages can read them, because the sign-in library needs to. Without them, you cannot sign in.
- An activity cookie that records, at most once an hour, that you have used Revise. It is how inactive accounts are found and deleted (see Data retention). First-party, HTTP-only, and it holds no information beyond its own name.
- A classroom screen cookie, set only on a computer that a teacher uses as the classroom screen for a TOK lesson (tok.alltheway.ing/screen). It holds a random key that lets that computer show the lesson until the period ends. First-party, HTTP-only, and it identifies nobody.
- No analytics cookies. We count page views with Vercel Web Analytics and measure how quickly pages load with Vercel Speed Insights (on one visit in ten). Neither sets a cookie or identifies you: they record the page, the kind of device and browser, the country, and timings, and Vercel discards the request details that could link visits together after a day. We do not run Google Analytics, Plausible, PostHog, or any equivalent.
- No advertising or social-media tracker cookies.
We also use first-party browser storage that is not a cookie:
- Local storage — UI preferences such as theme, last-viewed tab, and planner view mode. Never sent to our servers. One exception: if you choose “Save my work” in the systems diagram builder, a random key is kept there and sent with each diagram you check, so it can be saved to your account from inside a Notion page; “Not you?” under the diagram removes it. The digital exam drawing tool does the same when you choose “Save to Revise” from inside another site, and “Not you?” there removes its key. So does a class ranking inside a Notion page when you choose “Sign in to take part”, so your ranking is saved under your account; “Not you?” there removes its key. The capture–recapture game does the same when you choose “Save my progress” inside a Notion page, and “Not you?” under the game removes its key. A class ranking joined by code without an account keeps a random code there instead, so you can change your ranking. The TOK site remembers which of its menu links to show you (My lessons, Essay), so they appear at once; this is forgotten when you are signed out.
- IndexedDB and service-worker cache — used for offline study and faster loading; see “Offline data storage” below.
Because no non-essential cookies or tracking technologies are used, no consent banner is shown. If we ever introduce non-essential cookies or analytics, we will update this section and provide an appropriate consent mechanism before doing so.
Collaborative whiteboards
When you use a collaborative whiteboard, your drawings and edits are shared in real time with other participants in the session via Supabase Realtime. Whiteboard content is stored on our servers (Supabase). Teachers can control whether students can edit or only view a whiteboard.
Exam questions and lesson content
Exam questions and lesson content (including key terms) are managed by teachers and stored on our servers. Teachers control which exam questions are visible to students. Lesson data and key terms are synced from external Notion databases managed by the teacher and do not contain student personal data.
Administrator access
One named site administrator (the developer of Revise) has access to aggregated usage data including total cards created, review activity, AI costs, and streak information. This is used to monitor the health of the service and support students and teachers. The administrator may access individual records when investigating a specific support request or a suspected abuse / security incident, but does not routinely browse student flashcard content. The administrator also receives the ESS IA coach summary (see AI usage).
Offline data storage
When you start a flashcard revision session, your card data (questions, answers, and scheduling state) is cached locally on your device using IndexedDB. This allows you to continue reviewing cards if you lose your internet connection. Pending reviews are stored locally and synced to our servers automatically when your connection returns.
- Locally cached cards are automatically deleted after 24 hours.
- Pending reviews are removed from your device once successfully synced.
- You can clear all local data by clearing your browser's site data.
- If you install Revise as an app (PWA), static assets are also cached locally by a service worker for faster loading.
- The systems diagram activities keep the diagram you are building in your browser, so it survives a reload. It is never sent to us.
- The digital exam drawing tool keeps your answer and any unfinished drawing in your browser, so they survive a reload. They reach us only if you choose “Save to Revise”.
Your rights
Depending on your location, you may have the following rights regarding your personal data:
- Access — request a copy of the personal data we hold about you. You can self-serve this from the data export link in your settings.
- Correction — request correction of inaccurate data. Most of your profile (name, email, level, subjects, assessment dates) is editable directly on the Settings page; for anything else, contact us.
- Deletion — request deletion of your account and all associated data. Students can self-serve this from the Danger zone on the Settings page. Teacher and administrator accounts have dependent records and need to contact us.
- Restriction — request that we restrict processing of your data in certain circumstances (e.g. while a complaint is being investigated). To request restriction, write to richard@geographyalltheway.com.
- Objection — object to how we process your data, where processing is based on legitimate interests. To object, write to the same address.
- Data portability — request your data in a structured, commonly used, machine-readable format. Use the self-service export for the standard JSON format, or contact us for a different format.
- Withdraw consent — where processing relies on consent (rather than contract or legitimate interest), withdraw that consent at any time by writing to the address above. We will normally suggest account deletion as the most complete way to do this.
We aim to respond to all data-subject rights requests within 30 days. You also have the right to lodge a complaint with a supervisory authority — for users in the EU/EEA, your national data protection authority; for users in Switzerland, the Federal Data Protection and Information Commissioner (FDPIC); for users in the UK, the Information Commissioner's Office (ICO).
Data retention
We retain personal data only for as long as it is needed for educational purposes:
- Active accounts — data is retained for as long as you maintain an account.
- Inactive accounts — accounts with no sign-in for 24 months (the duration of an IB Diploma Programme course) are flagged for deletion. The user is notified by email and given 30 days to sign in and keep the account active; if there is no response, the account and associated data are deleted.
- Class membership — when you leave a class, the membership record is removed; your own cards and study history remain in your account.
- Name recordings — kept until you delete or replace the recording, or delete your account.
- ESS IA coach conversations, Card Lab drafts, saved systems diagrams, saved capture–recapture rounds, saved exam drawings, Answer Lab responses, IA guide progress, IA draft feedback and deadlines, and reference lists — kept for as long as your account, and deleted with it.
- TOK essay workspace: your answers, what you shared to a class board, your Google Doc link and the lessons you opened are deleted automatically one year after the exam session they belong to (31 May 2028 for May 2027), or with your account if that comes first.
- TOK lessons on the site: your answers, what you shared to a class board and the lessons you opened are deleted automatically one year after the exam session your class belongs to (31 May 2029 for May 2028), or with your account if that comes first.
- Class rankings: a ranking set on a lesson, with the names and orders in it, is deleted on 1 September, at the end of the school year it was started in; a ranking joined by code is deleted 30 days after it was started. Your own entries are also deleted with your account.
- Revision reminders — the device subscription is deleted when you turn reminders off, or when your browser tells us it has ended.
- End of school engagement — if a school stops using Revise, the school can request bulk deletion of all student accounts associated with that school. Individual students may also choose to keep their account and continue using Revise independently after they leave the school.
- End of academic year — Revise does not automatically delete accounts at the end of an academic year, because students typically continue revising for IB exams across two years. Schools that prefer year-end deletion can request it from the administrator.
- Backups — Supabase-managed backups retain copies for 7 days beyond the live data, after which they are overwritten.
- On request — you can ask us to delete your account and all associated data at any time (see Your rights).
Data portability and account deletion
Signed-in users can download a complete export of their personal data — including flashcards, review history, assessments, class memberships, teacher review messages, your name recording, IA coach conversations, Card Lab drafts, saved systems diagrams, saved capture–recapture rounds, saved exam drawings, Answer Lab responses, your TOK essay workspace answers and Google Doc link, your TOK lesson answers and what you shared to a class board, and other activity — as a single JSON file.
Students can delete their account at any time from the Settings page — look for the Danger zone at the bottom. Deletion is permanent and cannot be undone. Teacher accounts cannot be deleted self-service because they own classes and lessons that students depend on; please to arrange teacher-account deletion.
Changes to this policy
We may update this Privacy Policy from time to time to reflect changes in our service, subprocessors, or applicable law. The “last updated” date below indicates when the policy was last revised. Material changes will be communicated to users via the service.
Contact
For any privacy-related questions, requests, or complaints, please or write to richard@geographyalltheway.com. Revise does not have a formal Data Protection Officer at this stage, given the size of the service; the site administrator handles privacy queries directly.
Last updated: November 2026

