Privacy

This platform is a practice tool, not an advertising business. There is no third-party analytics script anywhere in it — no pixel, no tag manager, no session recorder — and nothing here is sold, rented or shared with advertisers. What follows is a description of what the code actually stores.

What is stored about your account

If you create one: your email address, your name if you enter one, and a hashed password. The password itself is never stored and cannot be recovered from the hash — a reset replaces it. You can take a practice test without an account at all, in which case none of this exists.

What is stored about an attempt

The questions you were served, the answers you gave, which options you eliminated, any highlights and notes you made in a passage, how long each question took, and the per-module counts your score is computed from. The score itself is not stored: it is recalculated from those counts every time a report is opened.

The test interface also records when the test tab loses and regains focus and when full screen is entered or exited. That is there so an attempt can be understood after the fact — a tutor looking at why a module ran out of time — and it records the fact of the event and its timestamp, nothing about what else was on your screen.

An attempt started without an account is bound to your browser by a signed cookie rather than to a person. Creating an account afterwards does not import it.

What is counted as product usage

A small set of events is recorded so the people running the platform can answer questions like “do people who start a test finish it”. An event is a name and a handful of scalar labels: which test, which module, whether the attempt was anonymous, whether a name was given at sign-up. It is stored in this platform’s own database and goes nowhere else.

Those labels are checked at the point of writing. Anything that looks like an email address is dropped, free text is not accepted, and values are capped in length. An event never contains your answers, your notes, your highlights or any account field beyond an internal id.

Alongside the events, one row per browser records the device type derived from your user agent (mobile, tablet or desktop), the raw user agent string, and the width of your browser window when you started a test. That row is created by the first event you generate, so reading a page and leaving records nothing at all.

No IP address is recorded anywhere, in the events or beside them.

Cookies

All first-party. None of them for advertising, and none shared with anyone:

• Sign-in cookies, once you have an account and are logged in, so the site knows who you are between pages and can tell a real form submission from a forged one.
• An analytics session cookie holding one random identifier. It lasts 180 days, cannot be read by scripts on the page, and exists so that a sign-up can be connected to the attempt that came before it.
• A signed cookie for an attempt started without an account, so the attempt is still yours when you come back to the tab.

Your light or dark theme preference is kept in your browser’s local storage rather than in a cookie, so it is never sent to the server.

Services this sends data to

Two, both used for one specific job:

• Resend delivers every email this site sends. It receives the address the email is going to and the contents of that email. For a password reset that is a link. For the four product emails — your score report, a weekly summary, a reminder after a break, and a weekly group summary if you run a group — the contents include the figures shown in them, such as your score and how it moved. Each of those four can be turned off from a link at the bottom of any of them, without signing in, or from your account page; a password reset cannot, because it answers something you asked for. Whatever is switched on, no more than two of the four are sent in any seven days.
• Cloudinary hosts images that appear inside questions — a diagram or a graph. Those are uploaded by whoever writes the question, never by a student, and no student data is sent there. When you load a question containing one, your browser fetches the image from Cloudinary and they therefore see that request.

Nothing else leaves the server. The application and its database are the only places your answers and scores exist.

How long it is kept

Your account, your attempts and your answers are kept for as long as the account exists, because they are what your score history is.

The usage events and the browser rows described above are not deleted automatically. No retention window is set and no job prunes them today. This page will state a window when one is set, and the same number will be the one the deletion job uses — a period stated here and enforced nowhere would be worse than saying plainly that nothing expires yet.

A record of which kind of email was sent to you and when is kept for the same reason, and is not pruned either. It is what enforces the two-a-week limit, so it has to outlive the week it measures. It holds the kind of email and the time, never the subject and never the contents, and nothing records whether you opened one — these emails carry no tracking pixel and load no images at all.

Getting your data removed

There is no delete-my-account button and no self-serve export in the product today. A deletion request is handled by hand: ask on the contact page from the address the account uses. No turnaround time is promised here, because nothing in the software enforces one.

If a tutor set up your account or added you to a group, they can see your attempts and scores. Removing your data removes it from what they see too.

Who this is

This site is operated privately and is not affiliated with, endorsed by or connected to the College Board. Questions about anything on this page go to the contact page.