PrepAMT Academy

LEGAL · PRIVACY

Privacy policy for PrepAMT FAA A&P test prep

This covers the website and the PrepAMT app for iPhone and Android. PrepAMT Academy, an independent A&P test prep service, holds your account, an email address and a way to prove it is yours, and it holds your studying: every question you answer, every gap you type into, every practice test you sit, and the test dates you are working towards. That is the whole of it, and section 02 lists it item by item. There are no advertising trackers, nothing follows you to other sites, and nothing is sold or shared for marketing. We do keep a short note of how you first found us, and section 03 says exactly what it is. Everything below was written by reading the code and the database rather than from a template.

Version . This replaces any earlier version.

01 WHO IS RESPONSIBLE

The controller

PrepAMT Academy is operated by Ancestorii Ltd, a company registered in England and Wales (number 17224876), which is the data controller for everything described here.

Registered office: 41 Pentre Road, Maerdy, Ferndale, Wales, CF43 4DP.

Every question, request or complaint about this policy goes to support@prepamtacademy.com. One address, monitored by a person.

Which law this is written to. UK GDPR and the Data Protection Act 2018, because the controller is established in the United Kingdom and those obligations follow the controller rather than the customer. If you are a resident of a US state with its own comprehensive privacy statute, that statute may give you additional rights on top of the ones in section 07. Write to the address above and we will honor them.

02 WHAT WE COLLECT

The data this FAA A&P test prep actually holds

This is the complete list, and it is longer than it was: this policy was first written when the database held accounts and nothing else, and the study application has been built since. Everything below exists in the schema today and was read out of it rather than assumed.

Your account.

  • Your email address. You give it when you create an account. It is how you sign in, how we send you a password reset, and how we would reach you about the service.
  • Your password, hashed, if you set one. We never hold the password itself: Supabase Auth stores a one-way hash, which cannot be reversed into the password you chose, including by us. An account created through Google or Apple has no password at all until you add one.
  • An identity record, if you signed in with Google or Apple. The provider, a stable identifier for you at that provider, and the email address and name it returned. Section 05 sets out exactly what is exchanged and what is not.
  • Account timestamps. When the account was created, when the address was confirmed, and when you last signed in.
  • Your sessions, and how each one started. Supabase Auth keeps a row per signed-in device holding the IP address and browser user-agent string the session was created from. It is a security record. It is what lets a session be recognised and revoked, and it and the sign-up throttle below are the only places in our database an internet address is stored about you. Like any web service, our hosting and database providers (section 04) also see the internet address each request comes from, in their own short-lived request logs.
  • The sign-up throttle. When an account is created, or a password reset is asked for, the IP address it came from is counted against the hour it happened in, so a burst from one place can be slowed down. The row holds the address, the hour and a count, and nothing that names you. A daily sweep deletes any row more than a day old. Together with the session rows, it is what lets us see when several accounts have been opened from one place, which the terms do not allow one person to do.
  • Your profile. The name you gave us or chose on your account screen, your time zone, the hour your study day rolls over, and your email preferences. There are 5 of those and nothing else in there: a countdown before a test date you have set, 3 weeks out and again a week out; the Sunday digest, which is off unless it is switched on; a note when a question you reported is ruled on; a receipt when you file one; and offers, which are on unless you turn them off. All 5 are yours to change, under Reminders on your account screen on the website, and every offer email has a link that turns offers off in one click.
  • That you agreed to these documents. When you ticked the box on the sign-up form, and the version date of the terms and this policy as they stood at that moment. A record of a consent that does not say what was consented to is not a record. If you join with Google or Apple, on the sign-up page or the sign-in page, pressing the button is the agreement, and the sentence beside it says so.
  • How you found us. When you create an account we keep a short note of how you got here: the name of the site that sent you (google.com, say, never the page or what you searched for), the campaign tags on the link if it had any, the first page you opened, whether you joined on the website, an iPhone or an Android phone, and your answer if you told us how you heard about PrepAMT. On the website the site, tags and page come from the cookie in section 08, so they are only there if you were in the United States and your browser had not asked us not to. If there is no cookie to read, in their place the note says whether we would have looked for one: that is, whether you joined from the United States with no Global Privacy Control or Do Not Track signal. It stays with the account and is deleted with it.
  • A deletion request, if you have made one. That you asked for the account to be deleted, when, the date it takes effect, and whether you cancelled it. Section 07 describes the whole mechanism. The record itself is erased with the account it belongs to.

Your studying. This is the larger half, and it is the half the product is for.

  • Every multiple-choice question you answer. Which question, which of the 3 options you picked, whether it was right, the subject it belongs to, the sitting it was part of, and the time you answered. Answers are permanent: the ledger has no edit and no delete, which is what makes the readiness figures worth looking at.
  • Every fill-in-the-gap answer, word for word as you typed it, including a blank one, which the product records as a real “I don’t know” rather than a skip. Also which item it was for, whether the grader accepted it, and when.
  • What the free plan served you. Which questions and gap items were handed to you and in what order, so the free set can be counted and so coming back gives you the same set rather than a new one.
  • Which of the 3 written tests you are studying for, and the date you have booked to sit each one. Taking a test off your bench keeps the date rather than losing it, so it is there when you put the test back.
  • Every practice test you sit. Which test and which paper, when you started and finished, your percentage score, whether you passed, and your answer to every individual question on it, including which ones you left blank and which ones you flagged to come back to.
  • What you are entitled to. Whether you are on the free plan or Pro, when that access started and expires, how it was granted, and any note a member of staff attached to the grant.
  • Your subscription, if you have one. Stripe’s reference for your customer record and for the subscription itself, which plan you are on, the date the current month ends, and whether you have cancelled. That is what lets the account screen tell you when Pro renews without asking Stripe every time you open it. No card details are in this, and there is nowhere in our database that could hold any: not the number, not the last 4 digits, not the expiry, not a billing address.
  • Your App Store or Google Play subscription, if you bought Pro in the app. Apple’s or Google’s reference for the subscription (a transaction number or a purchase token), which plan it is, the date the current period ends, and whether it is canceling, retrying a payment or a test purchase. While you are buying, a short count of how often your account has asked us to check a purchase, cleared within a day. No payment details are in any of this, because Apple and Google hold those and never send them to us.
  • A few steps on the way to Pro. The days you used up your free set, opened the plan card, opened the Pro screen in the app, or started a purchase in the app, and the days the app could not show you a price or a purchase did not go through. 1 line per step per day, with the date and a short note of where it happened. When the app could not show a price, the note is the reason instead: the store’s error code, or that the phone was offline. If the store answered but offered no price, the note is the country your App Store or Google Play account is set to. For a purchase that did not go through, it is the store’s error code. None of it says anything about what you studied. We look at these as totals, to see where people stop, and each line is deleted after 13 months.
  • Offers. When we are running an offer: whether you have had your one offer, which email made it, how much it takes off and when it ends, and whether you used it. That record holds a one-way hash of your email address rather than the address itself, so that a second account at the same address is not offered it again. We also keep each offer email we sent you, with when it went and whether our email provider accepted it. If you open checkout while an offer is running, we keep Stripe’s reference for that checkout page and when you opened it, so that 1 email can follow if you do not finish. Those checkout notes are deleted after 90 days, and all of it goes with the account.
  • Which payments and cancellations we have already acted on. A list of the notifications Stripe, Apple and Google have sent us and the billing emails we have sent you, each recorded once. It exists so that a notification arriving twice cannot charge your account twice over or send you the same receipt again, and it is the same kind of record as the email ledger below.
  • Anything you report. If you tell us a question is wrong or that the grader refused a good answer, we keep the report: which item, the reason you chose, any note you typed, the answer of yours that was refused, and what our reviewer decided.
  • A record of the emails we have sent you. Which one, when it went out, how many attempts it took, and the reference our email provider gave it. It is what stops the same message being sent twice.

What we do not hold. No card details of any kind. Pro is paid for on Stripe’s own pages, or through Apple or Google in the app, and what comes back to us is a reference and a renewal date. There is no column in our database that a card number could go in, which is a stronger statement than a promise not to look. No device records, no push tokens, no advertising or analytics identifier of any kind, and no location data. The nearest thing is a random number the app makes when it is installed, which section 04 describes: it names nobody, we do not keep it, and it is not an advertising identifier. The app keeps your session and a copy of what you have studied on your own phone, encrypted, and that stays there rather than coming to us. The time zone in your profile, the IP addresses on your session rows and in the sign-up throttle, whether you were in the United States (which the note of how you found us shows), and, if the app ever could not show you a price, the country your store account is set to are the closest thing to it, and all 5 are named above rather than denied. Nothing here profiles you or makes an automated decision with a legal or similarly significant effect: the readiness figures are arithmetic on your own answers, shown only to you.

And what happens when something new is added. This list is maintained by the same commit that changes the database. When a column that describes a person is created, the sentence describing it is written at the same time, not afterwards.

03 WHAT WE DO NOT DO

No ad trackers, no sale of data

There is no Google Analytics, no Tag Manager, no Meta pixel, no Plausible, PostHog, Mixpanel, Segment, Hotjar or Clarity, and no advertising script of any kind, on the website or in the app. This is not an aspiration: the source and its dependency lists were searched for every one of those names and none appears.

What we do count. The first time you arrive on the website from somewhere else, a small cookie of our own notes the name of the site that sent you, any campaign tags on the link, and the page you landed on. Your browser keeps it for 90 days, and we read it only if you create an account, then delete it. It is not shared, it is not used for advertising, and it cannot follow you to other websites. We set it only for visitors in the United States. What it becomes when you join is the note in section 02.

Do Not Track. If your browser sends Global Privacy Control or Do Not Track, we never set that cookie. The steps on the way to Pro in section 02 are still noted for a signed-in account, because they are about using PrepAMT itself and never leave us. Nothing on the site follows you to other websites, with the signal or without it.

The app has one thing the website does not. When it crashes, it tells us, through Sentry, which section 04 describes. That is a report that something broke, sent when it breaks. It is not a record of how you use the app, and nothing goes to Sentry while the app is working.

Nothing is sold. Nothing is shared with advertisers or data brokers. Your study history is yours: it is never sold, never published, never shown to another account, and never used to build a profile of you for anybody else’s purposes.

The sign-in cookies are strictly necessary. The one that notes how you found us is not, so we set it only for visitors in the United States, where the law lets us without asking, and never when your browser says no. That is why there is no consent banner. If that ever stops being true, a banner arrives in the same change.

04 WHO ELSE TOUCHES IT

Processors

There are 7, and they do exactly what is described here.

  • Supabase: authentication and the database. Everything in section 02 lives here.
  • Vercel: hosting. It serves the pages and, like any web server, handles the network requests that reach them.
  • Stripe: taking the payment, if you subscribe to Pro. Card details are entered on Stripe’s own pages and never reach our servers: we cannot see your card number and we do not store it. What we send Stripe is your email address and a reference for your account, so that a payment can be matched back to it, and, when an offer is applied at checkout, a reference for that offer; what we keep in return is Stripe’s reference for your customer record and your subscription, the plan you are on, the date it next renews, and whether you have cancelled. That is the whole of it. There is no card, no last 4 digits and no billing address on our side. Stripe is a controller in its own right for the fraud checks it runs on a payment, which is its own decision rather than ours and is covered by its policy. If you never subscribe, nothing about you is sent to Stripe at all.
  • Resend: delivering the email we send you. Your address and your name pass through it, and so does whatever the message says: a welcome when you join, a reply when you report a question, a countdown before a test date you have set, a receipt when you subscribe and a notice when a subscription is cancelled, and, if you switch it on, a Sunday digest whose subject line and body carry that week’s figures, how many questions you answered and what share you got right, and, now and then, news about PrepAMT, sometimes with an offer, including the offer that can follow a new account or a checkout left unfinished, which section 06 covers. The receipt carries the amount you were charged and the date the subscription renews; neither it nor the cancellation notice can be switched off, because they are records of a payment rather than messages we chose to send you. When your account is erased we send one email to say so, the only time your address goes anywhere after we have started deleting it, and it is not kept afterwards. The password reset is the one exception to all of it: it is sent by Supabase Auth rather than from our own code, over the same mail provider.
  • Kickbox: checking, at sign-up only, that the address you gave has a mailbox behind it. Your address is sent to them once, at that moment, and the answer is not stored. It is there so that an account is not created against an address that could never receive a password reset.
  • Sentry: crash reports from the app, and only from the app. When the app fails, it sends Sentry the error, where in our code it happened, the last few steps the app took before it (which screen was open, and which addresses it was calling, without what it sent), the phone’s model, operating system, language and time zone, the state it was in at that moment (such as free memory, battery and whether it was online), the app’s version, and your account reference, or before you sign in the random number from when the app was installed, so we can tell one person’s repeated crash from many people’s single one. Sentry is set not to keep your IP address, so a report says nothing about where you are. It never gets your email address, your name, your answers or your study history, and there are no screen recordings and no screenshots. The website does not use it.
  • Expo: delivering updates to the app. Each time the app opens, it asks Expo whether a newer version of its code is ready, so a fix can reach your phone without a new download from the store. That request carries the app’s version, whether it is on iPhone or Android, and the random number from when the app was installed, which Expo uses to count how many copies are in use. It is not linked to your account and carries nothing about you or your studying, though like any request it comes from your phone’s internet address. The website does not use it.

Payments. This paragraph used to say there was no payment processor because there was nothing to buy, and that when there was, card details would be handled entirely by the processor and never reach our servers, and that this section would name it. It is named above. The rest of that sentence still holds: no card detail of yours is ever on our servers.

Apple and Google, if you buy Pro in the app. They are not our processors, for the reason section 05 gives. They take the payment as controllers in their own right, under their own privacy policies, and they know that you bought Pro from us. To match the purchase to your account we tag it with your account reference, which means nothing outside this service. They do not get your email from us, your study history or anything else in section 02.

Transfers. Processing may take place outside the United Kingdom. Where it does, transfers are made under the safeguards UK data protection law requires: an adequacy decision, or standard contractual clauses with the UK addendum. We name what each processor does rather than where it runs, because a hosting region changes without this document being touched, and a policy naming the wrong region is worse than one describing the safeguard.

05 SIGNING IN WITH GOOGLE OR APPLE

If you use a provider instead of a password

The sign-in and sign-up pages offer “Continue with Google” and “Continue with Apple”. Using one is entirely optional (an email address and a password does everything the same account does) and it changes what is shared, so it gets its own section rather than a line in the one above.

Google and Apple are not our processors. That distinction is not pedantry, it decides who answers to you for what. A processor acts on our instructions; Google and Apple do neither. For the sign-in itself each acts as its own controller under its own privacy policy, which is the one that governs what they do with the fact that you signed in. We are the controller only for what they hand back and we then keep.

What they learn. Choosing a provider sends you to that company, and it necessarily tells them that you are signing in to PrepAMT Academy and when. We never see your provider password, and they never see ours.

What we receive. Only what identifies the account. We ask for the default sign-in scopes and nothing else, so we get no access to your mail, your files, your contacts or your calendar, and could not read them if we wanted to:

  • A stable identifier for you at that provider. It is how we recognize you on the next sign-in, and it is meaningless anywhere else.
  • Your email address, and whether the provider has verified it.
  • Your name, and from Google a link to your profile picture, where the provider supplies them. The name is what the workspace greets you by, and you can change it on your account screen at any time.

That is stored alongside your account as an identity record, so the provider is linked to it and you can sign in the same way again. An account created this way has no password (there is nothing to hash and nothing to steal) until you set one.

2 things specific to Apple, both worth knowing before you choose it. Apple lets you hide your email address, and if you do we receive a @privaterelay.appleid.com address that forwards to you instead of your real one. That works perfectly well here and we treat it exactly like any other address. And Apple releases your name only on the first authorization. If you remove PrepAMT Academy from your Apple ID and come back, that is a first authorization again, and anything you changed in between is not resent.

The lawful basis is the contract, the same as for a password. You asked to sign in this way; receiving an identifier and an email address is how that request is carried out.

You can stop. Revoking our access from your Google or Apple account settings ends the connection at their end. It does not delete your account here. Write to support@prepamtacademy.com for that, and see section 07. If you delete your account in the iPhone app and you signed in with Apple, you confirm with Apple once more and our access is revoked at their end there and then. We do not keep what that exchange hands back.

06 WHY, AND FOR HOW LONG

Lawful basis and retention

Performance of a contract covers everything needed to give you an account and run the product you asked for: holding an email address and a password hash so you can sign in, and recording what you have studied so that the next screen can show you where you are. A study tool that forgets your answers is not a study tool, so keeping them is not incidental to the service. It is the service. It also covers your subscription record, if you have one: we cannot give you a paid plan without knowing that you are on one and when it renews.

Legitimate interests covers the session records in section 02, which exist so a compromised account can be investigated and a session revoked; the sign-up throttle, which exists so a burst of sign-ups from one place can be slowed down, and which, with the session records, lets us see when one person is holding several accounts, something the terms do not allow and that we act on; the address check at sign-up, which exists so accounts are not created against mailboxes that do not exist; and the mail ledgers, which exist so the same message is not sent to you twice; and the record of which Stripe, Apple and Google notifications we have already acted on, which exists so that one arriving twice cannot charge or credit an account twice over; the app’s crash reports, which exist so that what breaks on a phone gets fixed; the app’s check for updates, which exists so that a fix reaches your phone without a new download; and the note of how you found us, with the steps on the way to Pro, which exist so we can see which sites and pages bring people who find PrepAMT useful, and where the way to Pro loses them. In each case the interest is a working, secure service and the data is the minimum that serves it.

News and offers. Now and then we email account holders about something new in PrepAMT, sometimes with a discount. That is on legitimate interests too: you signed up for this service, and news about it is something you would expect to hear. Each one says plainly that it is an offer, none goes to an account that is being deleted, and replying “stop” ends them for good. Stopping them changes nothing else: account emails, like receipts and password resets, still come.

2 kinds go out by themselves, when we are running an offer. A day after you create an account, if you have not gone Pro, we may send 1 email with an offer that lasts 72 hours, and 1 reminder 6 hours before it ends. And if you open checkout and do not finish, we may send 1 email about it a little later, which can carry that same offer if you have not had it. You get the offer once at most. None of these goes to anyone who has Pro or has paid for it before, and each one has a link that stops them in one click, as do the Offers switch on your account screen and a “stop” reply.

Consent covers the Sunday digest, and nothing else. It is off on every account unless it is switched on, and every one that goes out carries an unsubscribe address. The other 2 emails (a reply when a question you reported is ruled on, and a receipt when you file one) are answers to something you deliberately did, and they stop when you ask us to stop them. The subscription receipt and the cancellation notice are not on consent and are not switchable: they are records of a payment, in the same class as the password-reset email, and a customer is entitled to have been told what they were charged.

Retention. Almost everything is kept while the account exists, because almost all of it is what the account is for. The one exception is what the free plan handed out under the old daily allowance, which is purged after 90 days. The record of your one free set is not: it stays with the account, so you can go back over that set. The app’s crash reports are the other exception: Sentry deletes each one within 90 days, and deleting your account does not reach them sooner, because they hold your account reference, or the app’s random install number, and nothing else about you. Expo’s count of update checks is not linked to your account, so there is nothing in it for a deletion to remove. Delete the account and the rest goes with it (the record, any provider identity, the sessions, your answers, your practice tests, your reports, the per-account mail ledgers, the link to your Stripe customer record and your App Store or Google Play subscription record), really deleted, not flagged as deleted. We do not keep a shadow copy of any of it. The note of how you found us goes with the account, and the steps on the way to Pro go after 13 months, or with the account if that is sooner. The record of your offer goes with the account, and the notes of when you opened checkout go after 90 days, or with the account if that is sooner. Email that has already been delivered is in your inbox and in our provider’s sending records, and cannot be recalled from either.

3 of our records survive a deletion, and all 3 are named rather than glossed. The list of Stripe, Apple and Google notifications we have already acted on keeps its rows, with the link to your account removed. It is what stops a notification that arrives after the deletion being processed as if it were new, and without your account attached it says nothing about you. The record of what Stripe told us about each subscription (the plan, the renewal dates, the cancellation) keeps its rows the same way, reference removed, because it is the business’s account of a paid arrangement rather than a description of you. And the one-line ledger of report emails already sent keeps its rows likewise, so “was this sent twice?” stays answerable; the reports themselves, and everything you wrote in them, are deleted with the account. Beyond our records entirely, the payment itself is Stripe’s: a company that has taken money has to keep an account of it for tax and anti-fraud purposes for as long as the law requires, and deleting your PrepAMT Academy account does not and cannot reach into that. Stripe’s own policy governs it. The same goes for Apple and Google if you paid through them.

07 YOUR RIGHTS

What you can make us do

Write to support@prepamtacademy.com from the address on the account. We answer within 1 month, which is the statutory deadline rather than a target.

  • Access. A copy of what we hold about you: the account, the profile, and your study history as described in section 02.
  • Rectification. Correct anything wrong. Your name, time zone and day boundary you can change yourself on your account screen; anything else, write to us and we will.
  • Erasure. Delete the account and everything attached to it, yourself, from your account screen: the Leaving section asks you to type the address on the account, then opens a 14-day window. During those 14 days you can sign back in and cancel from the same card, and the switchable emails are paused; at the end of them the account is erased: a real deletion of every record listed in section 02, not a flag, with the 3 named survivors in section 06 keeping their rows with the link to you removed. One rule sits in front of it: if a paid subscription is still renewing, you are asked to cancel it first, under Manage billing, because deleting the account cannot reach into Stripe and would not have stopped the charges. If you pay through Apple or Google instead, you are warned and the deletion can go ahead, but they keep charging you until you cancel it with them. Writing to us instead still works, and is answered within the same month it always was. The steps are set out below.
  • Portability. Your data in a machine-readable format.
  • Objection and restriction. Object to processing based on legitimate interests, or ask us to hold rather than use the data while a dispute is resolved. For offers, the quickest way is the link at the foot of any offer email, or the Offers switch on your account screen.
  • Withdraw consent. Reply to the unsubscribe address on the Sunday digest, or write to us, and it stops. Withdrawing does not undo what was sent before.
  • Complaint. To the UK Information Commissioner’s Office, at ico.org.uk. You do not have to come to us first, though we would rather you did.

How to delete your PrepAMT account

This is for the PrepAMT app on iPhone and Android, and for the website. They are one account, so deleting it in one place deletes it in both. You do not need the app installed to do this. It is run by Ancestorii Ltd, a company registered in England and Wales (number 17224876).

  • In the app. Tap your initials at the top of any tab to open Account, then Delete your account, and type the address on the account to confirm.
  • On the website. Sign in, open your account, and go to the Leaving section at the bottom of it. Type the address on the account to confirm.
  • By email. Write to support@prepamtacademy.com from the address on the account. We answer within 1 month.

How long it takes. 14 days. The request opens a 14 day window in which you can sign back in and cancel it, and the erasure runs within the hour after the window closes. We then send one email to that address to confirm it is done, and we do not keep the address.

What is erased. Your account and sign-in, any Google or Apple identity linked to it, your profile and settings, every answer, gap and mock paper, your test dates, your reports and what you wrote in them, what you have been entitled to, and your subscription records with Apple or Google.

What is kept. The 3 records named in section 06, with the link to you removed. Email already delivered stays in your inbox. Stripe, Apple or Google keep their own records of any payment, under their own policies.

If you pay for Pro. Paying on the website, cancel under Manage billing first, because we refuse the deletion while that is renewing. Paying through Apple or Google, deleting your account does not stop them charging you, so cancel with them too. We cannot do that for you.

08 COOKIES

The cookies, named

The sign-in cookies, which are strictly necessary and keep you signed in for as long as you asked, and 1 more that notes how you found us.

  • The session cookies, set by Supabase Auth and named sb-…. They carry your session, an access token and a refresh token, and the server swaps an expiring token for a fresh one on each page request. They are cleared when you sign out.
  • 2 cookies of our own, named amt_, written only if you clear “keep me signed in on this device” before signing in. One remembers that you asked; the other is set to expire when the browser closes. When the first survives and the second does not, we know the browser has been restarted and we sign this device out. That is the entire mechanism, and it works per device: signing out here never signs you out anywhere else.
  • amt_first, set when you first arrive from another site, only in the United States and only if your browser has not asked us not to. It holds the name of the site that sent you, any campaign tags, the first page you opened and the date. It lasts 90 days, nothing in the page can read it, and we read it only if you create an account, then delete it.

There is no advertising cookie and no third-party cookie of any kind. Your light or dark choice is kept in your browser’s own storage and never leaves it. Block cookies and the site still reads; you simply cannot stay signed in, which is what the sign-in cookies are for.

09 AGE

Who this is for

PrepAMT Academy is for people preparing for a professional certificate and is not directed at children. You must be 16 or over to create an account, and the sign-up form asks you to confirm it in the same sentence that asks you to accept the terms and this policy. (The certificate itself requires you to be 18 before the FAA will issue it, though there is no minimum age for the knowledge tests: see the eligibility page.) If you believe a child has created an account, write to us and we will remove it.

10 CHANGES

Changes to this policy

This policy is versioned by date, and the version above is the one in force. When it changes materially (a new processor, a new category of data, a new purpose), the new version goes up here before the change takes effect, not after, and the version date above moves with it. So that date is how you tell whether anything has changed since you last read this.

The version you agreed to when you created your account is recorded against it, so “which one did I accept?” is a question with an answer rather than a guess.