Prep36 › Privacy Policy

Privacy Policy

Plain language, because you should not need a lawyer to read it.

Last updated November 18, 2026

Prep36 (prep36.com) is an ACT practice website operated by AdMax. This policy explains, in plain language, what information Prep36 handles, why, who helps us handle it, how long it is kept, and how you can remove it. Questions: hello@prep36.com.

On this page

The short version

Who Prep36 is for

Prep36 is made for high school students getting ready for the ACT, and for the parents, teachers and tutors who help them. It is not meant for children under 13.

Prep36 does not ask your age, and you can practice without giving us your name or email. If you are under 13, please do not create an account, buy a plan, enter your email in a form, or apply as a promoter. If you are under 18, check with a parent before you do any of those.

If you believe a child under 13 has given us personal information, such as an account, an email in a form, or a purchase, email hello@prep36.com and we will delete it. For a purchase, that means everything except the payment records the law requires us to keep. We will also ask Google to delete the Analytics data we can link to that purchase (see Deleting Analytics data, under Google Analytics). We will delete any activity log and recordings linked to that email. We cannot find the child's other Analytics data, or activity from a browser that never signed in, from an email. Google deletes the detailed data after 14 months, but summary reports can keep that browser's random id and labels longer (see How long, under Google Analytics).

What stays on your device

Prep36 saves your progress in your browser's local storage, on the device you are using. That includes:

One technical note sits in session storage instead, which your browser clears when you close the tab. It holds the question bank file address, so the app reloads only once after we update the site. If you arrived from one of our Google ads, the same storage also holds a short note (p36_ad_visit) so that visit is counted once, not once per page.

The copy on your device stays there. We cannot recover it if your browser data is cleared, and Prep36 does not sync progress between devices yet. Some of these items also reach us or our providers in other ways, as the sections below explain. Which questions you answered, whether each was right, and how long each took also reach our activity log. Your unlock code is stored in our database. An email you send through a Cram Kit form is stored with us. A checkout and any promoter code go to Stripe. An account is kept by Firebase.

Google Analytics also receives some of this, as events and labels tied to a random id. That includes your test date, your plan, practice test scores and lesson progress. It also includes the section of each answer and whether it was right, and numbers from the score tools and the study plan page (see Google Analytics). Prep36 never sends it your name, your essays or the other words you type.

Your choices. Settings, then Export progress, saves a copy as a file, and Import progress puts it back. The file holds all of your saved progress on that device, including your account email and sign-in details if you are signed in, so keep it private. Settings, then Reset everything, erases the progress saved on that device. That is your study plan and first name, scores, answers, essays, streaks, XP, lesson progress, settings, promoter details and any saved promoter code. It also signs you out there and sets that device back to the Free plan (enter your unlock code under Redeem to turn a paid plan back on). Reset keeps the helper items listed above, such as your unlock code, the email you typed into a Cram Kit form, the sign-in hashes, a test in progress, the random Analytics id and your choice about recording. To remove everything, clear the site data for prep36.com in your browser settings.

Google Analytics

What it records. It records the pages you open on prep36.com and the features you use. For example: starting a practice test, answering a question and whether it was right, finishing a test and its score, signing up, starting checkout, and buying. For a purchase it records the plan (Plus, Max, or a one-time pass such as the December 12 Sprint), the amount, the checkout id, which button led to checkout, and whether a parent bought it for a student. The score tools send the numbers you enter and the numbers they work out, such as a target score and a superscore. The search box on the guides page sends how many guides matched and the first match, never the words you typed. Analytics also records the site or link that brought you, including campaign tags such as a Google Ads click id if the link has one. It also records your browser, device type and screen size, and a rough location (country, region or city) that Google works out from your internet address.

Google's automatic measurement. Google's standard measurement is on for every prep36.com page that loads Google Analytics, the practice app and the guide pages alike. It records scrolling, clicks on links to other sites, file downloads, video plays and page changes inside the app. It records when a form is started and when it is sent, but not what you typed in it. It also records search words that appear in a page address, such as ?q= or ?search=. Prep36's own pages never put what you type into a page address, with one exception: a promoter link carries a promoter code made from the promoter's name and email (see Promoters).

What Prep36 never sends. Prep36 never sends Google Analytics the words you type: no names, emails, essays, notes, search words or unlock codes. The one exception is a promoter code in a page address (above). The score tools send numbers, and labels from a fixed list such as your weakest section. Analytics does get the checkout id of each purchase, and our thank-you page can turn a checkout id into that purchase's unlock code (see Unlock codes).

User-provided data collection is off. Google Analytics has a setting called user-provided data collection. When it is on, a site can send Google details such as email addresses, and Google's tag can also look for them on a page by itself. Both parts are turned off for prep36.com. Google explains the setting on its help page about user-provided data collection.

Five labels in the app. The practice app also gives each browser five labels. p36_uid is a random 12 character id made once in your browser. p36_plan is free, plus or max (other if the app does not know the plan). p36_test_date is the ACT date you picked, or none. p36_signed_in is yes or no. p36_first_seen is the first day this browser used Prep36. The id is random. It is never made from your name, email or account. It lets us see how practice goes over time for one browser, for example whether students come back. The most direct links from that id to a person are signing in and buying. If you sign in, our activity log stores this id with your account email, so our team can see this browser's Analytics history under that email (see Activity log and session recordings). If you buy Plus, Max or a pass such as the Sprint from the app, the checkout carries this browser's Google Analytics cookie id to Stripe, with the number of the current visit (see Paid plans). The buttons on our parents page open that same checkout. So our team can connect that browser's Analytics history, including these labels, to the purchase and the email used at checkout. Tutor pack checkouts, on the For tutors page, carry no Analytics id. Analytics also records when each event happens. So our team could try to match a form entry or a new account to one browser's activity by its time. Our reports do not do that.

Why. To see which parts of Prep36 help students, and to fix what does not.

Who. Google, which runs Google Analytics 4 for us. Our Analytics account also has three of Google's data sharing settings turned on. Google's technical support staff can look at our Analytics data when they need to fix a problem. Google's sales staff assigned to our account can look at it to suggest better settings. And Google can combine it with other sites' data for benchmarks and models it may share with others. Google says it groups that data and removes what identifies you or us before it uses it this way. The setting that would share our Analytics data with other Google products is turned off. So is Google signals, which would connect visits to people's signed-in Google accounts. Prep36 may link Google Analytics to its own Google Ads account, with personalized advertising off (see Advertising). It is not linked to any other advertising account. Google explains its side on its page about how Google uses information from sites that use its services.

Cookies. Google Analytics sets two cookies on prep36.com, named _ga and _ga_ followed by an id, to tell visits from the same browser apart. They last up to two years after your last visit unless you clear them.

How long. Google keeps the detailed, event level data for at most 14 months and then deletes it. In that detailed data, a browser's id and its five labels are kept until 14 months after that browser's last visit. These limits do not cover summary reports, which can be kept longer. The random id is one of our report fields. So a summary report can still list one browser's id with its five labels and its totals, such as how many of its answers in each section were right. This means some Analytics data about one browser can last longer than 14 months. We can ask Google to delete one browser's data when we can find it (see Deleting Analytics data).

Deleting Analytics data. Analytics data is tied to a random id, so we usually cannot find it from an email address alone. But we can ask Google to delete Analytics data in these cases, by sending a deletion request for that browser's id through Google's own tool. Google carries it out on its own schedule, which can take weeks. It removes the data tied to that id, but totals already counted in summary reports do not change, and we cannot promise what Google keeps in its backups.

To ask, email hello@prep36.com from the address you paid with or signed in with. Google deletes the rest as described under How long, above.

Team visits. When our team tests the practice app, those visits are marked as internal so our reports leave them out. A flag in the team's browsers (p36_qa) and automated test browsers turn this on. It changes nothing for students.

Your choices. Block or clear cookies for prep36.com, use a content blocker, or install Google's opt-out browser add-on at tools.google.com/dlpage/gaoptout. Prep36 works the same with Analytics blocked. Clearing the site data also replaces the random id with a new one.

Advertising

Prep36 may advertise itself on Google Search. When it does, Google Analytics is linked to Prep36's own Google Ads account so we can see which of our ads led to practice, a sign-up or a purchase. When you arrive from one of our ads, Analytics records which ad brought you (campaign tags in the link and Google's click identifier) and sends those results to our Google Ads account.

Activity log and session recordings

Activity log. Besides Google Analytics, the practice app sends our own server a short log of how it is used, tied to the same random id described above (p36_uid). It holds a session id and the seconds the app was on your screen and in use. It holds which part of the app you opened. For each question you answered, it holds the question's id and section, whether you got it right, and how many seconds it took. It also holds the tests, lessons and drills you started and finished, your plan, and the first day this browser used Prep36. Our host adds your device type, operating system and browser, and a rough location (city, region and country) worked out from your internet address. The log does not store the internet address itself. It never holds words you type, essays, notes, unlock codes or Stripe ids.

If you are signed in. The log also holds your account email and how you signed in (email and password, or Google). That links this browser's activity, and the Analytics history under the same random id, to your email for our team.

Session recordings. We may record sessions to see how Prep36 is used and to fix what does not work. A recording is a replay of the page: what was on it, mouse movement and taps, scrolling, and the answers you pick. We make recordings with our own copy of an open source tool and keep them ourselves, so no replay company receives them. Typed text is hidden: every input box is masked, and names, email addresses and unlock codes shown on a page are hidden automatically. Masking is automatic and could miss something; if you see a problem, tell us. A recording does show the questions on the page and the choices you pick.

What is not recorded. We do not record the thank-you page, the unlock code page, Settings, the promoter page, the essay pages, the checkout page, this policy or the Terms. We do not record pop-up windows, such as signing in, your account, checkout and Send to a parent. Lesson videos are left out of recordings too. Recording does not start until the notice about it has been on your screen, it stops after 30 minutes without activity, and each browser has a limit per session and per day.

Who can see them. Both are kept in private storage at Vercel, and our team reads them in a private dashboard behind a login.

How long. Recordings are deleted automatically after 30 days. The activity log is deleted automatically after 14 months.

Turn it off. Use Turn off in the notice, or Settings, then Usage recording. Either stops both the activity log and recordings for that browser from that moment. Clearing the site data removes that choice, so you would need to turn it off again. A browser that sends the Global Privacy Control signal is treated as turned off. Team visits and automated test browsers are left out.

Deleting it. Email hello@prep36.com from the address on your account and we will delete the activity and recordings linked to that email. If you never signed in, the log is tied only to a random id, so we cannot find yours from an email address.

Accounts (optional)

You never need an account to practice. An account today does not move your progress between devices; that is not built yet.

How long. An email and password account stays in Firebase until you ask us to delete it. Signing out removes the account from your device, not from Firebase. A Google sign-in's name and picture are kept only in your browser, and signing out removes them there, along with its email. Signing out does not remove your email from our activity log (see How long). Either way, two things stay on the device after you sign out: a first name that signing in copied into your study plan, and the short scrambled code (hash) of the email. Reset everything removes the first name, and clearing the site data removes both.

Delete your account. There is no delete button yet. Email hello@prep36.com from the address on the account and we will delete it from Firebase.

Email forms

Some pages ask for your email. The free Cram Kit form is on the home page, the Cram Kit page, the About and Superscore pages, and the guide pages, including the guide for Spanish-speaking parents. Tutor and counselor pack requests are on the For tutors page. Each form has a link to this policy next to it.

What we store. Your email, which form you used and the page it was on, the time, and your browser's user agent (a short description of the browser and device, which helps us spot spam). The Cram Kit page saves its whole page address, including any tags in the link you followed, such as campaign tags or a promoter code. A tutor pack request also stores the pack size you picked.

Why. To give you the kit or answer your request and, as the Cram Kit forms say, to send occasional ACT prep tips.

Who. Google Firebase (Cloud Firestore) stores them. The website can add an entry but cannot read any back; only our team can, with an admin account. Our team's private dashboard shows only a shortened (masked) form of each email, such as j***@g***, and keeps that copy in private storage at Vercel. A computer on our team also shows an alert for each new entry, with the email in that same shortened form. Google Analytics does not get the email you type. When we send ACT prep tips, we send them from our hello@prep36.com mailbox at IONOS.

How long. Until you ask us to remove it, or until we no longer need it.

Your choices. To stop emails or have your address deleted, reply to any email from us or write to hello@prep36.com. Your browser also remembers that you unlocked the kit and the email you typed there; clearing the site data removes that.

Paid plans and payments

Monthly plans (Plus and Max) and one-time purchases are optional. One-time purchases are tutor packs and passes, such as the December 12 Sprint: one payment that keeps Plus on until December 14, 2026, with nothing to cancel. You pay on Stripe's own checkout page. Your card details go to Stripe and never reach Prep36.

What we get from Stripe. The email used at checkout, the plan, what was paid (including any discount and tax), and a checkout id. Stripe also keeps the billing details it asks for at checkout, which we can see in our Stripe account.

Buying for a student. A parent can buy from our parents page. Checkout works the same way. Afterwards, the thank-you page shows the student's unlock code with buttons to copy it, text it or email it. Text it and Email it open your own apps, and nothing is sent until you send it there. On that device, the home page also shows the code until you hide it. Prep36's own code tells Analytics that the checkout was for a student and which of these buttons you used, never the code.

Unlock codes. So a parent can pay on one phone and the student can study on another, each purchase gets an unlock code. The code is stored in Google Cloud Firestore with the plan (and its end date, for a pass), the Stripe checkout id, when it was made, and whether and when it was redeemed. A code made by your browser holds nothing else. A code made by our payment server can also hold the buyer's email and the order (a Stripe checkout or payment id), so we can resend a lost code. So can every code our team makes by hand, for tutor packs and as free codes for partners and testers, along with a short note, such as which seat of a pack it is.

Who can see a code's details. Anyone who has a code can look up everything stored with it, the same way the app checks a code. So when a tutor gives a code to a student, or a parent gives one to their teen, that person can also see the buyer's email and order if they are stored with it. The thank-you page address that Stripe sends a buyer back to holds the checkout id. Our server gives that purchase's code to anyone who sends it that checkout id, so keep that address private too. Scripts from Google (Analytics and Sign-In) and Search Atlas run on that page and can read its address (see Files from other companies). Anyone who has a code can also redeem it, on more than one device. Keep codes private and give each one only to the person who will use it.

Deleting code details. If you ask us to delete your details, we remove your email, the order and the note from your codes, and the codes keep working. If you also want a code turned off, we delete it. A deleted code cannot be looked up or redeemed again, unless we make it again. A device that already unlocked a plan with it keeps that plan, because the plan is saved on that device.

Our payment server. When a checkout finishes, Stripe tells our server. It reads the plan, the checkout id, the buyer's email and the amount, makes or finds the unlock code, and can keep a purchase record with those details. Sometimes the thank-you page opens in a browser that did not start the checkout, or that browser could not make the code. Then it sends the checkout id from its page address to our server. The server checks that the purchase was paid and sends back its unlock code. The server can also report the purchase to Google Analytics with the plan, the amount, the checkout id, whether a promoter code was used, and the browser's Google Analytics cookie id and visit number. That lets the purchase join the visit it came from, and the Google ad behind that visit, if there was one. If the checkout had no cookie id, for example because Analytics was blocked, it uses an id made from the checkout id instead. A checkout opened from the app carries that cookie id to Stripe, along with any promoter code, so the purchase joins that browser's Analytics history. Tutor pack links carry neither, and our server does not report tutor packs to Analytics. Our team's private dashboard shows buyers' emails only in a shortened (masked) form, such as j***@g***, and keeps that copy in private storage at Vercel.

Purchase email. When the purchase email is turned on, our server sends the buyer one email with the unlock code, through an email service called Resend, to the address used at checkout only.

How long. Stripe keeps payment records under its own terms and the tax and accounting rules it follows. Unlock codes and purchase records stay so your code keeps working.

Cancel or ask. Email hello@prep36.com from the address you used at checkout to cancel, to get a lost code, or to ask what we hold about a purchase.

Promoters and referral links

You must be 13 or older to apply as a promoter. If you apply, your name, email, where you post and your promoter code are saved on your device. Your name, email and where you post are not sent to us or to Google Analytics. We have no list of promoters. To get paid once payouts open, you email hello@prep36.com from the address you signed up with.

Your code is made on your device. It is the first four letters of your name plus four characters worked out from your email, for example JANE-7K2Q. The code is part of your promoter link. So anyone who opens your link can see it. Stripe and Google Analytics can see it too when the link is used.

When someone opens a Prep36 link with a promoter code in it (?ref= and the code), their browser saves that code and the date with the rest of their progress. The code counts for 30 days. If they buy a plan in that time, the code goes along with their Stripe checkout, so the sale is credited to the promoter. After 30 days it is no longer used. It stays saved on that device until they use Reset everything, clear the site data, or open another promoter link. Google Analytics can also record the address of the link that was opened, which includes the code.

Share buttons and calendars

Share, Text it, Email it and Copy open your own apps or copy to your clipboard. Prep36 never sends a message for you. Score and progress cards are drawn on your device. Analytics records that a share button was used, which kind, and which page or item it shared, never the message.

Share to Google Classroom, on the teachers page, opens Google Classroom with the assignment link filled in. Add to Google Calendar opens Google Calendar with the event name, date and a short description filled in. The calendar file (.ics) is made on your device.

Widgets on other websites

Schools and other sites can embed the Prep36 score calculator, test countdown, superscore tool and question of the day. Inside another website these widgets load no analytics and save nothing in the browser. They are still files from prep36.com, so our host receives the normal web request. On prep36.com itself, the superscore tool remembers the scores you type, on your device.

Question of the day. Teachers can show the question of the day (prep36.com/embed/daily) on a class page or a projector. On any site, prep36.com included, it loads no analytics, sets no cookies, saves nothing in the browser and loads no files from other companies. Picking a choice and showing the answer happen in that page only, and nothing about them is sent to us. Inside another page, it tells that page only its own height, so the frame fits. Outside our own teachers page, its More free practice link carries campaign tags, so Analytics can tell that a visit came from the widget. The same questions come as an RSS feed at prep36.com/daily.xml, with links that carry campaign tags too. Our server builds the feed from a fixed list of questions. It reads nothing about you, stores nothing and calls no other service.

Files from other companies

Like most websites, Prep36 pages load some files from other companies. When your browser fetches one, that company receives your internet (IP) address, your browser type and the page address. Each company handles this under its own privacy policy.

Hosting, logs and search engines

Prep36 is hosted by Vercel. To send you each page, Vercel gets the request (your IP address, browser and the page). It keeps basic server logs for a limited time under its own terms. Vercel also stores our activity log and session recordings, in private storage. Our payment server's logs show email addresses only in a shortened form, such as j***@g***, and never show unlock codes. They do show checkout ids, which our thank-you page can turn into unlock codes. Only our team and Vercel can see these logs. To slow down guessing, the part of our server that hands out codes counts the requests from each internet address for 10 minutes. It keeps that count in memory, and our code does not log the address.

When we publish or change pages, we tell search engines which page addresses changed, through IndexNow. That message holds only our page addresses, no visitor data.

Pinterest. The images we post as pins on Pinterest are files at prep36.com/pins, which Pinterest copies. A pin links to a Prep36 page with campaign tags, so Analytics can tell that a visit came from a pin. Prep36 pages load no Pinterest code. What you do on Pinterest is covered by Pinterest's own privacy policy.

Cookies

Prep36's own code sets no cookies; it keeps what it needs in local storage, as described above. Google Analytics sets the _ga cookies. Google and Stripe can set their own cookies on their own sites when you use Google sign-in or checkout, and the other files listed above may use their own under their own policies. Firebase sets no cookies on prep36.com.

Who we share information with

We do not sell or rent personal information. We do not share it with other advertisers. We share it with the service providers named on this page, which run parts of Prep36 for us. They are Google (Analytics, Firebase, Fonts and Sign-In), Stripe, Vercel, Search Atlas, Resend, and IONOS, which hosts our hello@prep36.com mailbox. Google can also use Analytics data in the few other ways our Analytics settings allow (see Google Analytics, under Who). These providers may handle information in the United States and other countries.

Other people can see your information when it is passed on. For example, anyone who has an unlock code can see what is stored with it (see Unlock codes). So can anyone who has the checkout id of the purchase that paid for the code, which is in the thank-you page address. Share buttons send what you choose to send. Anyone who uses your browser can see the progress saved in it. We also share information when the law requires it.

How long information is kept

Your choices and requests

When you email us

If you write to hello@prep36.com, we get your email address and your message. Mail sent to that address goes to a mailbox at IONOS, the company that hosts email for prep36.com, and our team reads and answers it there. Replies to our purchase email go to the same mailbox. We keep messages to answer you and to remember what we did about your request.

Keeping information safe

Prep36 uses HTTPS on every page. Payment and email keys stay on our server, never in the web page. Our database rules let the website add email form entries but never read them. Besides our team, only someone who has the exact code, or the checkout id of the purchase that paid for it (it is in the thank-you page address), can look up an unlock code. That person can see everything stored with the code. Checkout ids are also in Analytics, in Stripe and in our server's logs. No website is perfectly secure, so share only what you need to.

Changes to this policy

If this policy changes, the date at the top changes, and the new version applies from that date.

Contact

Questions or requests: hello@prep36.com. See also the Terms of Service.