Cookie Policy
Last updated 18 October 2026
The cookies and browser storage this site uses, what each is for and how long it lasts. We use nothing for advertising and nothing that follows you to other websites. Analytics counts page views, and plays of the film on the home page, without cookies, and you can switch it off on this page.
Who we are
This site is run by Teasr Technologies Limited (“teasr”), registered in England and Wales, company number 17430351. Questions about this policy: hello@teasr.co.uk. How we handle personal data more generally is in our Privacy Policy.
Cookies
| Cookie | Provider | First or third party | Category | Purpose | Duration |
|---|---|---|---|---|---|
sb-<project>-auth-token | teasr (via Supabase) | First party — ours | Strictly necessary | Keeps you signed in and proves each request is yours. Without it you cannot log in at all. | Until you sign out, or 400 days |
sb-<project>-auth-token-code-verifier | teasr (via Supabase) | First party — ours | Strictly necessary | A one-time security code set while you sign up or reset your password, so the link in the email can only complete the request it was sent for. | Until the sign-up or reset is completed |
teasr_ui | teasr | First party — ours | Appearance and functionality | Remembers the colour theme and the row density you chose in the signed-in product, so your choice is there on your next visit. It holds those two settings and nothing about you. | 1 year |
cf_chl_rc_i, cf_chl_rc_ni, cf_chl_rc_m | Cloudflare (Turnstile) | Third party | Strictly necessary | Set by Cloudflare's security check on the sign-in, sign-up and password-reset pages, which tells people apart from automated sign-up and password attacks. Cloudflare uses them to spot faults in the check itself. | Set and expired by Cloudflare, which does not publish a lifetime |
That is the complete list. We set no advertising cookies and no cross-site trackers. The Cloudflare cookies are set by Cloudflare, inside its security check, only on the sign-in, sign-up and password-reset pages; Cloudflare describes them in its own cookie list.
Storage in your browser that is not a cookie
The rules cover cookies and similar technologies, so these belong here too. None of them is sent to us.
| Key | Where | First or third party | Category | Purpose | Duration |
|---|---|---|---|---|---|
teasr.ask.dismissed | localStorage | First party — ours | Appearance and functionality | Remembers that you closed the assistant pop-up, so it does not reappear on every page. It records nothing about you and nothing you asked it. | Until you clear your browser storage |
teasr.data-room.held.<room id> | sessionStorage | First party — ours | Strictly necessary | Holds your unsent data-room decisions for this tab so they can be restored; cleared when you commit, discard or sign out. It holds the decisions and any decline reason you wrote, and no one's name. | Session only (this tab) |
teasr.doc-edit.draft.<document id> | localStorage | First party — ours | Strictly necessary | Holds the edits you have typed into your IM or teasr and not yet sent, so a closed tab or a lost connection does not lose them. It holds the wording you typed and nothing else, and is removed as soon as you send your changes. | Until you send your changes or clear your browser storage |
teasr.owner.check-to-save.v1 | localStorage | First party — ours | Strictly necessary | Set only when you choose to save your readiness check to an account, or to carry on to the free preview from your result: holds your answers while you sign up, so they can be saved. Removed as soon as they are saved, and ignored after a day. | Until saved, at most a day |
teasr.analytics.opt-out | localStorage | First party — ours | Strictly necessary | Set only if you switch analytics off on this page. It is how this browser remembers your objection, so no page view or film play is reported from it. It holds the value 1 and nothing else. | Until you switch analytics back on or clear your browser storage |
teasr.owner.owner-led-card.dismissed | localStorage | First party — ours | Appearance and functionality | Remembers that you chose “Not now” on the owner-led sale card on your home page, so it is not shown again in this browser. It records nothing else. | Until you clear your browser storage |
The security check on sign-in pages
The sign-in, sign-up and password-reset pages use Cloudflare Turnstile to stop automated attacks on accounts. When one of those pages loads, Cloudflare's script reads signals from your browser and connection (your IP address, your browser's user-agent and connection fingerprint, and which site is asking) to decide whether a person is there. It does not read what you type into the form. This is strictly necessary for the security of the service you are using, so it does not need your consent.
Cloudflare acts for us in running the check. It also uses the same signals, as a controller in its own right, to improve its bot detection; that use is described in Cloudflare's Turnstile privacy addendum.
Why you are not asked to accept anything
The law on cookies and similar technologies (regulation 6 of the Privacy and Electronic Communications Regulations, as amended by the Data (Use and Access) Act 2025) requires consent before anything is stored on or read from your device, with exceptions. Since 5 February 2026 those exceptions include:
- what is strictly necessary for a service you asked for, which expressly includes keeping it secure and preventing fraud;
- what is used only to produce statistics that improve the service; and
- what remembers your choices about the appearance or functionality of a site.
The second and third apply only if you are told clearly what happens, which is what this page is for, and given a simple, free way to object. Everything listed above falls within one of those exceptions, as its category shows. Advertising, targeting and cross-site tracking are not within any of them, and we use none of them. So nothing on this site currently requires your consent, and there is no banner.
Analytics, and how to switch it off
Vercel Web Analytics. Counts page views so we can see which pages are used and improve them. A small script served from our own domain reports the page's address, the page you came from, your browser, operating system and device type, and your country, which Vercel works out from your IP address. It sets no cookies. Before anything is sent, the address is cut down to the page's route: query strings are removed, and deal ids, invitation tokens and similar codes are replaced with a placeholder. Vercel counts visitors with a hash of the request that it discards after 24 hours, so it cannot follow you from one day to the next or across other websites. It also counts, with nothing about you attached, when the film on the home page is played, reaches halfway or finishes, and which button is pressed at its end. The figures are used only to improve this site.
Vercel processes this for us as our processor, and sees the request in the ordinary way any web host does. Our Privacy Policy says more, including where Vercel processes data.
You can switch analytics off here, free and without giving a reason. The choice is kept in this browser, so switch it off in each browser you use.
Loading your analytics setting…
Withdrawing consent, and managing what is stored
Nothing on this site asks for your consent, because nothing we use requires it, so there is no consent to withdraw. If that changes, this section will say how, and withdrawing will be as easy as giving it.
What you can do, and what each costs you:
- Switch analytics off with the button above. Nothing else on the site changes.
- Block or delete cookies in your browser settings. Blocking the sign-in cookie signs you out and stops you signing back in, because it is how you stay signed in. Blocking Cloudflare's cookies may stop the security check working, and then you cannot sign in or sign up.
- Clear your browser storage to remove the keys in the second table. Pop-ups and cards you closed will appear again, unsent data-room decisions in an open tab are lost, and analytics is switched back on.
When you pay
Payments are made on Stripe's own checkout page, not on this site. Stripe sets its own cookies there, to process the payment and prevent fraud, as described in Stripe's cookie policy.
Changes
If we add a cookie or a storage key, this page changes before it is set: the tables are generated from the same list the application is checked against. The date at the top shows when the policy last changed.