Legal

Cookie Policy

Last updated: 28 September 2026 Three cookies No third-party domains

This page lists everything turbobattle.com stores in your browser. There are three cookies and three storage keys, all of them set by this site and read by this site. No advertising, no tracking, no pixels, nothing loaded from anyone else.

The short version.

Two cookies remember your answers — your age and your cookie choice. A third appears only on the contact page and keeps the form honest. Your virtual Bolts balance sits in local storage on your own device and never reaches us. Optional analytics are described below and are not running today. Refusing everything non-essential costs you nothing: every game works exactly the same.

Thin cyan and magenta light lines crossing a deep cobalt surface — Six small pieces of text in your browser. That is the whole of it.

1. What cookies and similar storage are

A cookie is a short piece of text a site asks your browser to keep and to send back on the next request. It has no code in it and cannot run anything. What it does depends entirely on what the site puts inside it and who gets to read it.

Browsers offer two other places to keep text, and both count as similar storage under the same rules:

Local storage holds data until something clears it. It is never attached to a request, so it does not travel to a server on its own.
Session storage works the same way but the browser discards it when the tab closes.

The difference that matters is direction. A cookie goes back and forth. Local storage stays where it was written. TurboBattle uses three cookies, one local storage key and two session storage keys, and the table in section 3 is the whole inventory.

2. How few we set, and why

Most of what a cookie banner exists to cover — advertising, audience building, cross-site identity — needs an account, a network of partners and a reason to follow you around. We have none of the three. TurboBattle is a free social casino with no sign-up, no password and no profile, so there is no identity for a cookie to attach itself to in the first place.

That leaves exactly three jobs worth a cookie:

We have to ask whether you are 18 or over. Remembering your answer is the only civil way to avoid asking again on every page.
We have to ask what you want done about cookies. Remembering that answer is the only way to stop the notice returning for ever.
The contact form has to tell a message you actually sent apart from one that another site tried to send in your name.

Nothing else on the site needs to remember anything about you, so nothing else does.

3. The complete list

This is the full inventory as the site stands today, read off the code rather than copied from a template. Every entry is first party: set by turbobattle.com, read by turbobattle.com, shared with nobody.

Every cookie and storage key used by turbobattle.com
Name	What it is for	Type	Lifetime
tb_age_ok	Records that you confirmed you are 18 or over, so the age check does not return on every page.	Cookie · strictly necessary	1 year
tb_cookie_choice	Records which button you pressed on the cookie notice, so the notice stops appearing.	Cookie · strictly necessary	1 year
PHPSESSID	Ties the contact form to its one-time token and blocks a second send within 60 seconds. Created on the contact page only.	Cookie · strictly necessary	Until you close the browser
tb_wallet_v1	Your virtual Bolts balance and the timer on the free top-up. Stays in the browser and is never sent to us.	Local storage · not a cookie	Until you clear site data
tb_session_start	Records the moment this tab was opened, so the break reminder can say how long the sitting has lasted.	Session storage · not a cookie	Until you close the tab
tb_break_next	Holds the time the next break reminder is due: 45 minutes into a sitting, then no more than once an hour.	Session storage · not a cookie	Until you close the tab
Optional analytics	Would count which free games get opened, in aggregate. Only ever set after you agree, and we name no vendor because none is in place.	Cookie · optional, consent first	Not currently set

Seven rows, and the last is empty. If that changes, this page is rewritten before a single line of it ships and the notice comes round again to ask you afresh.

4. The three cookies, one by one

tb_age_ok

Contents: the digit 1. Nothing else fits in it and nothing else is put in it.

It is written when you answer yes at the age check and lasts a year. Without it the age question returns on the next page you open. Answering no writes nothing at all — a refusal leaves no trace on the device, which is exactly why the question comes back next time.

The check works with JavaScript turned off: the buttons are a real form, the answer arrives by POST and the server sets the cookie. It is marked SameSite=Lax, and Secure whenever the page is served over HTTPS.

tb_cookie_choice

Contents: the word accepted or the word rejected. Any other value is treated as no answer at all, so a hand-edited cookie cannot pass itself off as consent.

There is a joke in this one nobody has managed to dig out: remembering that you refused cookies takes a cookie. The alternative is a notice on every page for the rest of your life, which helps nobody.

PHPSESSID

Contents: a random string, meaningless on its own. It is the standard session identifier of the language this site is written in, and it is created on the contact page and nowhere else on turbobattle.com. Open a game and no session starts.

It does two jobs. It ties the form in front of you to a single-use token, so a page on some other domain cannot quietly post a message under your address. And it lets the server turn away a duplicate sent within 60 seconds of the first, so a stray refresh does not deliver your message twice. It carries no personal data of its own; what you typed into the form is covered by the Privacy Policy.

5. Your balance lives in local storage

tb_wallet_v1 is not a cookie. It holds your virtual Bolts balance, the time of your last free top-up and a few counters the games use for pacing. It is written by your browser, kept by your browser, and read by nothing outside it.

It is never attached to a request, so it does not reach our servers at any point, on any page.
We keep no copy and cannot look yours up. There is no ledger on our side to check it against.
It belongs to one browser on one device. A phone and a laptop each keep their own.
Clearing site data, or playing in a private window, starts you again at 5,000 virtual Bolts, at no charge.

Losing it costs you nothing.

Bolts are play money: a counter inside our games, For entertainment purposes only. They have no cash value, cannot be exchanged for anything, and cannot leave the game. So a cleared balance is not a loss of value; it is a reset to 5,000 — which is where everyone starts.

The session reminder that interrupts a long sitting keeps two numbers in session storage: tb_session_start, the moment this tab was opened, and tb_break_next, the time the next reminder is due. The browser throws both away when the tab closes. The Responsible Social Gaming Policy explains what that reminder is for.

6. Nothing is loaded from another domain

The absent list is longer than the present one, and rather more useful.

No advertising, retargeting or conversion cookies, from anyone, under any name
No third-party analytics scripts or tag managers
No social buttons, share widgets, embedded video or comment systems
No cross-site identifiers, device fingerprinting or data sold onward to a broker
No content delivery network, and no web fonts served from someone else's domain

The last line is housekeeping as much as privacy. Everything this site needs — the two typefaces, every image, every script, every mark on a game board — is served from turbobattle.com. No outside party is told that you were here, and none of them has to be trusted on your behalf. It also means that blocking third-party cookies wholesale, which many browsers now do by default, changes nothing about how this site behaves.

What a cookie here can see

That you answered the age question
Which button you pressed on the cookie notice
That a contact form is open in this browser

What it cannot see

Who you are — there is no account to be
Which games you played, or how any round went
Your balance, which never leaves your device
Anything you do on any other site

7. Optional analytics, and why that row is empty

The notice at the foot of the screen asks about analytics because the answer is better collected before it is needed than after. As this page is written, we measure nothing. No analytics cookie is placed on turbobattle.com, whichever button you pressed, and we name no vendor here because there is none to name.

If that ever changes, all of the following hold, and we are stating them now so they are not invented later:

It runs only for visitors who have said yes. Silence and refusal both mean no.
It measures which free games get opened and how the site performs, in aggregate. Not individuals.
This page is rewritten with the vendor, the cookie name and the lifetime in the table above, before a single line of it goes live.
The notice comes round again, so nobody is carried over on an old answer.

8. The legal basis for each class

Two different rules apply at once. Storing or reading anything on your device is governed by the UK Privacy and Electronic Communications Regulations and the equivalent ePrivacy rules in the EU. Where that storage also involves personal data, the UK GDPR and the EU GDPR apply on top of it. The data controller is Turbo Battle Interactive Ltd. — see the Privacy Policy for the full detail.

Strictly necessary cookies

tb_age_ok, tb_cookie_choice and PHPSESSID are exempt from the consent requirement because each is strictly necessary to provide something you asked for: an age check that does not repeat itself, a notice that respects your answer, and a contact form that cannot be driven from another site. We do not ask permission for these, and turning them off is a matter for your browser rather than for us.

Two of the three hold no personal data at all — a digit and a word. The session identifier is processed on the basis of our legitimate interests in keeping the form secure and free of duplicates, which is a light interest weighed against a random string that is discarded when you close the browser.

Local and session storage

tb_wallet_v1 is strictly necessary for the game you opened: without it there is no balance to play with. It stays on your device, we never receive it, and so there is no processing by us to find a basis for. The two session-storage numbers behind the break reminder work the same way.

Optional analytics

Consent, and nothing else — given by pressing Accept all. It is not covered by legitimate interests, it is not bundled into anything else, and it is not set before you agree. Since nothing is running today, the practical answer is that no analytics basis is being relied on at all.

9. Giving, refusing and changing your answer

The notice appears once, on your first visit, with two buttons and no dark pattern between them:

Essential only keeps the three necessary cookies and adds nothing.
Accept all adds permission for analytics — which, today, adds nothing.

Your answer is not final and never was. Cookie settings at the bottom of every page forgets it and brings the notice back, on this page or any other. Press it, answer again, and the new answer takes effect at once.

Refusing costs you nothing.

Every game runs the same, every free top-up arrives on the same schedule, and no page is held back. Consent here buys us a number, not you an advantage. There is no version of this site that works better because you said yes.

The button needs JavaScript.

With scripts turned off it does nothing, and deleting tb_cookie_choice by hand has exactly the same effect: the notice returns on the next page you open. Everything else — the age check, the contact form, the whole of this document — works with scripts disabled.

10. Clearing cookies and site data yourself

Your browser is the final authority here and can throw the lot away without consulting us. The wording moves between versions, but the path is roughly the same everywhere.

Chrome, Edge and other Chromium browsers. Settings, then Privacy and security, then the entry covering site data. Search for the domain and delete it.
Firefox. Settings, then Privacy and Security, then Cookies and Site Data.
Safari. Settings or Preferences, then Privacy, then Manage Website Data.
On a phone. The same options live inside the browser's own settings rather than the system ones.

Most browsers also let you block cookies for one site, block all third-party cookies, or clear everything on exit. Any of those work against turbobattle.com, and none of them breaks a game.

Clearing site data takes the balance with it.

Site data for turbobattle.com covers the three cookies and tb_wallet_v1 in one gesture, so the games open again at 5,000 virtual Bolts. Nothing of value is lost, because nothing of value was held — but a balance you paid for goes the same way as a free one, and we cannot restore either. A private window keeps none of it once the window closes, and is the shortest possible version of this whole page.

11. Changes, and who to ask

This page is reviewed whenever the site changes what it stores, and the date at the top moves when it does. There is no archive of older versions, because there has been nothing dramatic to archive.

Anything about cookies, browser storage or personal data reaches the data controller at [email protected]. Anything else — a game misbehaving, a question about the counters — is better sent to [email protected] or through the contact form. A person reads every message and answers within two business days.

The Privacy Policy sets out what happens to a message once it arrives, how long we keep it, what rights you have over it, and who at Turbo Battle Interactive Ltd. is answerable for it. This page covers only what is stored on your own device.