Cookie Policy
Effective date: 1 October 2026
ReviseReady uses a small number of cookies and browser-storage entries that are needed to run the website, keep it secure, keep you signed in and remember choices you make. A cookie is a small piece of information stored on your device; browser storage (localStorage and sessionStorage) works in a similar way but is only read by this website.
No analytics, advertising or tracking
ReviseReady does not use analytics, advertising, remarketing, profiling or cross-site tracking technologies. Everything listed below is strictly necessary to provide the website or a feature you have asked for, so no consent banner is shown. If we ever add an optional technology, we will ask for your consent before it is used and update this page first.
Cookie and browser-storage register
Cookies
| Name | Provider | Purpose | Category / exception | Duration | First / third party | When created |
|---|---|---|---|---|---|---|
| __cf_bm | Cloudflare (network in front of our hosting) | Distinguishes real visitors from automated bots to protect the site from abuse. | Strictly necessary — security | 30 minutes | First-party (set on www.reviseready.co.uk) | On the first page or file request, for every visitor |
| __dpl | Lovable (website hosting) | Appears to keep a visitor on the same published version of the site while browsing. Precise purpose pending confirmation from Lovable. | Strictly necessary — deployment routing (pending provider confirmation) | 1 day | First-party (set on www.reviseready.co.uk) | On the first page load, for every visitor |
| __stripe_mid | Stripe (payment processing) | Fraud prevention: helps Stripe recognise the browser across payment attempts so it can detect and block fraudulent payments. Not used by ReviseReady for analytics or advertising. | Strictly necessary — payment security and fraud prevention | 1 year | First-party (set by Stripe's checkout script on www.reviseready.co.uk) | Only after you choose a paid plan and click “Continue to secure payment” |
| __stripe_sid | Stripe (payment processing) | Fraud prevention: identifies the current payment session so Stripe can detect suspicious activity during checkout. Not used by ReviseReady for analytics or advertising. | Strictly necessary — payment security and fraud prevention | 30 minutes | First-party (set by Stripe's checkout script on www.reviseready.co.uk) | Only after you choose a paid plan and click “Continue to secure payment” |
| m | Stripe (payment processing) | Fraud prevention: device identifier used by Stripe's fraud-detection service (Radar) to assess the risk of a payment. Not used by ReviseReady for analytics or advertising. | Strictly necessary — payment security and fraud prevention | About 400 days (observed in test, October 2026) | Third-party (set on m.stripe.com) | Only after you choose a paid plan and click “Continue to secure payment” |
| __cf_bm | hCaptcha (bot check used inside Stripe's checkout), delivered via Cloudflare | Security: distinguishes genuine people from automated bots during the payment step. Not used by ReviseReady for analytics or advertising. | Strictly necessary — payment security and fraud prevention | 30 minutes (observed in test, October 2026) | Third-party (set on .hcaptcha.com) | Only after you choose a paid plan and click “Continue to secure payment” |
| hmt_id | hCaptcha (bot check used inside Stripe's checkout) | Security: helps hCaptcha recognise a browser it has already checked, so genuine purchasers are challenged less often. Not used by ReviseReady for analytics or advertising. | Strictly necessary — payment security and fraud prevention | 30 days (observed in test, October 2026) | Third-party (set on api.hcaptcha.com) | Only after you choose a paid plan and click “Continue to secure payment” |
| __cflb | hCaptcha (bot check used inside Stripe's checkout), delivered via Cloudflare | Load balancing: routes the bot-check requests to the same server during the payment step. Not used by ReviseReady for analytics or advertising. | Strictly necessary — payment security | 30 minutes (observed in test, October 2026) | Third-party (set on api.hcaptcha.com) | Only after you choose a paid plan and click “Continue to secure payment” |
| _px3 | HUMAN Security (formerly PerimeterX), bot-detection service used by Stripe on its checkout | Security: records the result of an automated bot check on the payment page. Used only to protect the payment step; not used by ReviseReady for analytics or advertising. | Strictly necessary — payment security and fraud prevention | About 5 minutes (observed on the live site, October 2026) | Third-party (set on .stripecdn.com) | Only after you choose a paid plan and click “Continue to secure payment” |
| _pxde | HUMAN Security (formerly PerimeterX), bot-detection service used by Stripe on its checkout | Security: holds bot-detection data used to assess whether the payment request comes from a genuine person. Used only to protect the payment step; not used by ReviseReady for analytics or advertising. | Strictly necessary — payment security and fraud prevention | About 5 minutes (observed on the live site, October 2026) | Third-party (set on .stripecdn.com) | Only after you choose a paid plan and click “Continue to secure payment” |
| _pxvid | HUMAN Security (formerly PerimeterX), bot-detection service used by Stripe on its checkout | Fraud prevention: identifier that lets the bot-detection service recognise a browser it has already checked. Used only to protect the payment step; not used by ReviseReady for analytics or advertising. | Strictly necessary — payment security and fraud prevention | 1 year (observed on the live site, October 2026) | Third-party (set on .stripecdn.com) | Only after you choose a paid plan and click “Continue to secure payment” |
| pxcts | HUMAN Security (formerly PerimeterX), bot-detection service used by Stripe on its checkout | Security: links the bot-detection checks within a single payment visit. Used only to protect the payment step; not used by ReviseReady for analytics or advertising. | Strictly necessary — payment security and fraud prevention | Deleted when the browser is closed (observed on the live site, October 2026) | Third-party (set on .stripecdn.com) | Only after you choose a paid plan and click “Continue to secure payment” |
localStorage
| Name | Provider | Purpose | Category / exception | Duration | First / third party | When created |
|---|---|---|---|---|---|---|
| bonjour-gcse-tier | ReviseReady | Remembers whether you chose Foundation or Higher tier. | Strictly necessary — remembers a setting you chose | Until you clear browser data or delete your account on this device | First-party | When you choose a tier |
| gcse-progress-v1 | ReviseReady | Keeps a record on your device of practice tasks you have finished, your scores and feedback points, so you can see your progress. | Strictly necessary — feature you requested | Until you clear it, reset progress, clear browser data or delete your account on this device | First-party | When you finish a practice task |
| sb-…-auth-token | ReviseReady (sign-in service hosted by Lovable) | Keeps you signed in to your account. | Strictly necessary — session continuity | Until you sign out, the sign-in expires or you delete your account | First-party | When you sign in |
| reviseready-welcomed-<account id> | ReviseReady | Stops the welcome email being sent more than once. | Strictly necessary — account function | Until you clear browser data or delete your account on this device | First-party | The first time you open your dashboard after signing up |
sessionStorage
| Name | Provider | Purpose | Category / exception | Duration | First / third party | When created |
|---|---|---|---|---|---|---|
| oauth_next | ReviseReady | Remembers which page to return you to after signing in with Google. | Strictly necessary — sign-in you requested | Removed straight after sign-in, or when the tab is closed | First-party | When you start signing in with Google |
| tsr-scroll-restoration-v1_3 | ReviseReady (built-in page navigation) | Remembers your scroll position so the Back button returns you to the same place on a page. | Strictly necessary — site navigation | Deleted when the tab is closed | First-party | On the first page load, for every visitor |
When you delete your account, ReviseReady clears the localStorage and sessionStorage entries above on the device you used. You can also clear them at any time in your browser settings.
Homepage video
The explainer video on the homepage is a ReviseReady file served from our own website address through our hosting provider. It is not embedded from YouTube, Vimeo or any other video platform. Loading or playing it does not create any extra cookies or browser-storage entries and does not send requests to third-party video services; like every file on the site, it passes through Cloudflare, which may set the __cf_bm security cookie listed above.
More information
Questions about this policy can be sent to contact@reviseready.co.uk. For how we handle personal information generally, see the Privacy Notice or the shorter Privacy for Students summary.