Last updated October 2026
Data & cookies
Every cookie and browser-storage key BurnTest.io (a K&B Company LLC brand) uses, what it does, how long it lasts, and how to say no.
Strictly necessary
These keep the site and your account working, so they can't be switched off. All of them are set by burntest.io itself.
| Cookie | What it does | How long | Type |
|---|---|---|---|
bt_session | Keeps you signed in. | 30 days | First-party, HTTP-only |
bt_csrf | A random value that proves sign-in and account forms were sent from our own pages. | 1 year | First-party |
bt_oauth | Holds the Google sign-in handshake while you log in with Google. Deleted as soon as you're back. | 10 minutes | First-party, HTTP-only |
bt_pending_url | Remembers the website address you typed before you had an account, so it's ready on your first burn. | 1 day | First-party |
bt_geo | Your country, from our hosting network, so we know whether to ask for cookie consent first. | 30 days | First-party |
bt_consent | Remembers your cookie choice. | 180 days | First-party |
Staff only
Set only for BurnTest staff using the admin console. Customers and reviewers never get these.
| Cookie | What it does | How long | Type |
|---|---|---|---|
bt_admin | Keeps a staff member signed in to the admin console. | 14 days | First-party, HTTP-only |
bt_social_oauth | Holds the sign-in handshake while staff connect a BurnTest social media account. | 10 minutes | First-party, HTTP-only |
bt_gsc_state, bt_gsc_verifier | Hold the sign-in handshake while staff connect Google Search Console. | 10 minutes | First-party, HTTP-only |
bt_preview | Lets staff view the site while it's in private preview. Only set from a staff preview link. | 30 days | First-party, HTTP-only |
Measurement we run ourselves
We count visits and sign-ups ourselves, on our own servers, so we can see which pages lead to a burn.
| Cookie | What it does | How long | Type |
|---|---|---|---|
bt_aid | A random ID so we can count visitors and see the path from a landing page to a burn. | 1 year | First-party |
bt_sid | A random per-visit ID for the same purpose. | Until you close the browser | First-party |
bt_utm | The campaign tags or referring site that brought you here, so we can credit the right campaign if you sign up later. | 30 days | First-party |
bt_ref | The referral code from a friend's invite link, so they get their free burn when you sign up. | 30 days | First-party |
None of these carry your name or email, and only burntest.io reads them. If your browser sends Global Privacy Control or Do Not Track, we skip bt_aid, bt_sid and bt_utm entirely and send no measurement events.
We also use Vercel Web Analytics and Speed Insights, run by our hosting provider, to count page views and measure load speed. They set no cookies and don't identify you.
Analytics & advertising
We use Google Analytics 4 and the Meta Pixel to measure our ads and which pages lead to sign-ups. This is how they work:
- In the EU, EEA, UK and Switzerland they load only after you click Accept on the cookie banner. Elsewhere they load unless you click Decline.
- If your browser sends Global Privacy Control or Do Not Track, they don't load at all.
- Inside your account they can load only on the dashboard home, the new-burn form, the billing page and the reviewer sign-up form, to record that a sign-up or purchase happened. They never load on pages that show recordings, transcripts or reports, anywhere else in the reviewer area, or in account settings.
| Cookie | What it does | How long | Type |
|---|---|---|---|
_ga, _ga_* | Google Analytics: tells visits apart so we can see which pages and ads lead to a burn. | Up to 2 years | Third-party (Google) |
_fbp | Meta Pixel: lets Meta tell us which ads led to a sign-up or purchase. | 90 days | Third-party (Meta) |
bt_evt | A one-time note that you just signed up, so the next page can report it to the tools above. Cleared as soon as it's read. | Up to 10 minutes | First-party |
Other sites we send you to
Signing in with Google happens on accounts.google.com, and payments happen on Stripe's checkout page. Google and Stripe set their own cookies on their own sites, under their own privacy policies. We don't see or control those cookies.
Browser storage
A few small values live in your browser's local or session storage instead of cookies. They never leave your browser. Session storage clears when you close the tab; local storage stays until you clear your browser data.
| Key | What it does | How long | Where |
|---|---|---|---|
bt_sid | The per-visit ID above, kept for the tab. | Until you close the tab | Session storage |
bt.pv.<page> | Makes sure a page view is counted once per visit. | Until you close the tab | Session storage |
bt.blog.viewed.<post> | Makes sure a blog post view is counted once per visit. | Until you close the tab | Session storage |
bt.ref.dismissed | Remembers that you closed the "your friend gave you a free burn" banner. | Until you close the tab | Session storage |
bt.purchased.<pack>.<id> | Makes sure a purchase is reported only once. | Until you close the tab | Session storage |
bt.notes.<burn> | Reviewers: keeps the notes you've typed for a burn if you re-record or reload. Deleted when you submit. | Until you close the tab | Session storage |
bt.admin.sidebar, bt.admin.density, bt.extensionId | Staff only: admin console layout and a developer setting. | Until you clear browser data | Local storage |
Reviewers who install the BurnTest Recorder extension: it keeps the burn in progress in Chrome's extension storage. Details are in the BurnTest Recorder privacy policy.
How to control cookies
Use the Privacy choices link in the footer to accept or decline analytics and advertising cookies at any time. Your browser can also block or delete cookies; the strictly necessary ones come back when you next sign in.
Your data rights (download, delete, opt out of marketing email) are in Account settings and described under Your choices on the Privacy page.
This page is provided for transparency and is not legal advice. Questions: support@burntest.io.