Privacy policy
Effective 11 November 2026
Piratini is a free pirate game you play in your browser. This page says what the game handles about you, why, who else receives it and what you can ask for. There are no accounts: the game knows you by the name you type and a random token in your browser.
Who runs this server
This server is run by the Piratini crew, who decides how the data below is used. Write to the host's contact address (this host has not set one yet) with any question or request about your data.
What the game handles and why
Your name and looks
The rooster name you type, its colour and looks, and any crew or ship name you give, are kept in your browser so the join card remembers them. They are sent to the server while you play, so other players can see who is who. On a server with the crew voyage (the campaign), its save file keeps the crew's names and progress until the host resets it. The battle keeps no names.
Your battle ship (the piratini_bt cookie)
When you open the battle, the server gives your browser a cookie named piratini_bt: a random token, nothing
else. It is the key to your saved battle ship: gold, owned ship and parts, locker, renown, victory prizes, your rank in a crew,
and the recovery code that moves the ship to another browser. It lasts a year from your last visit, is HttpOnly
(the page's own scripts cannot read it) and is only sent to this site. A record that never held anything is dropped after 7
days; one with a ship or gold in it is kept until you ask us to delete it or the alpha resets the battle.
Signing in (servers with sign-in enabled)
Where a server has sign-in enabled, pressing Join makes an anonymous account for you with Google's Firebase Authentication: a
random user id, nothing else, which then keys your saved battle ship instead of the cookie, so you keep it on another browser or
server. Nothing is made before you press Join. If you choose Sign in with Google in the settings, your Google account is
linked to that id and Firebase holds your Google e-mail address and name; the game shows your e-mail only to you and never sends
it to the game server, which sees only the id. Google (Firebase) processes this on our behalf as a processor. Your browser keeps
the sign-in in its storage (firebaseLocalStorageDb) until you sign out. Delete my data also deletes the
Firebase account (if it was made long ago, Google may ask you to sign in again first); Sign out keeps the account but
forgets it in this browser.
Your IP address
Your browser's address reaches the server with every connection. The server uses it, in memory, to cap how many connections and messages one address may send and to slow down password and recovery-code guessing. Its log prints an address only on a crew voyage join and when it refuses or limits an address for abuse; the game writes no address into its files (a chat report keeps only a salted hash of it, below). The log is the server process's output, kept as long as the host's log storage keeps it. piratini.io is served through Cloudflare, which sees your address and the traffic on its way to us.
Chat
Chat lines go through the server to the players they are for and are not kept. In the battle, swear words are masked by a word filter unless you turn "Filter chat" off in Settings. Names that are slurs are refused. When you press Report on a player, the server keeps a report for the host to act on: the time, your name and theirs with your crews, their last five chat lines, and both players' addresses only as salted hashes (not the addresses themselves).
Voice chat
Voice is off until you switch it on, every session, and is never recorded. Audio goes to the players near you (in a battle, your
crew and ships close by at sea) through a relay (a TURN server): run by the Piratini crew or, if this server uses it, Cloudflare's
Realtime TURN service. The relay sees your IP address and carries the audio, which is encrypted between the players' browsers, so
the relay cannot listen to it; other players cannot see your IP address, and the game server only passes the connection
set-up messages along, removing any address but the relay's. A server with no relay has voice switched off. Only if the host
of a server explicitly chose direct voice does audio go straight between browsers: then those players' browsers can see your
IP address and Google's public STUN servers (stun.l.google.com) see it too, and the game tells you so before voice
first turns on.
Analytics and ad measurement (piratini.io only)
On piratini.io the page loads Google Tag Manager, which runs Google Analytics and Google Ads conversion measurement. They tell us how many people play and what goes wrong: which mode you pick, when a join starts, succeeds or fails and why, how long you play (counted at 1, 5, 15, 30 and 60 minutes), the graphics setting and frame rate once, why a connection dropped, the first 100 characters of an error, and battle results (round, place, kills, a win, how long your ship lasted, crew size and hull). Never your name, chat, crew code, passcode or player id. Google also receives what any page sends it: your IP address, browser and device type, the page address and where you came from. Five minutes aboard your own ship in a battle round counts as a conversion for our Google Ads campaigns.
Google Consent Mode decides what Google may store. In the European Economic Area, the UK and Switzerland, analytics and ad cookies are refused until you accept them on the card the landing page shows; elsewhere they are allowed until you turn them off. You can change your choice any time with the "Analytics & ad cookies" switch in Settings (the gear on the join card, or the pause menu's Display tab). With cookies refused, Google still receives cookieless pings so an ad click can be counted. Other servers running this game load none of this.
If your browser sends the Global Privacy Control signal, ad cookies and ad personalisation stay refused everywhere, whatever you chose before; the settings switch then covers analytics only.
Privacy choices opens the game with the cookie choice showing.
Cookies and browser storage
Everything below lives in your browser. Clearing the site's data removes it.
| Name | Kind | What it is for | How long |
|---|---|---|---|
| Necessary | |||
piratini_bt | cookie | Your saved battle ship (above) | 1 year from your last visit |
firebaseLocalStorageDb | IndexedDB | Only where a server has sign-in enabled, after you press Join: your sign-in (above) | Until you sign out or clear it |
piratini_key | local storage | Your player key: a random key made when you first join a crew voyage, sent to that server so your rooster's name and progress stay yours. The server keeps only a scrambled form of it | Until you delete it |
piratini_site | cookie | Only on a password-protected test server: remembers that you typed its password | 30 days |
piratini_rejoin, piratini_refreshed, piratini_stale_reload, piratini_move, piratini_battle_back, piratini_story_* | session storage | Putting you back where you were after a reload, an update or a move to another battle server | Until the tab closes |
| Preferences | |||
piratini_name, piratini_color, piratini_look, piratini_more_looks, piratini_mode, piratini_crew, piratini_crew_code | local storage | Your name, looks, the mode and crew you picked, and the crew code you last typed | Until you clear it |
piratini_settings, piratini_keys, piratini_voice, piratini_voice_notice, piratini_battle_chat, piratini_hud_mode, piratini_sail_assist, piratini_gun_drill, chart_layers2 | local storage | Settings, key bindings, voice and chat switches, screen layout and helpers | Until you clear it |
piratini_tips, piratini_hint_uses, piratini_tutorial, piratini_battle_coach, piratini_battle_said, piratini_tracked_quest | local storage | Which tips and lessons you have seen, and the quest you follow | Until you clear it |
piratini_battle_stats, piratini_battle_prizes, piratini_battle_renown | local storage | Your battle record, prizes and renown, shown in the game | Until you clear it |
piratini_consent | local storage | Your analytics and ad cookie choice | Until you clear it |
| Analytics (piratini.io only) | |||
_ga, _ga_* | Google cookies | Google Analytics: tells one visit from another | Up to 2 years (Google's default) |
piratini_ga_once, piratini_ga_clock, piratini_ga_rounds | session storage | Sending each analytics event once a tab, and counting play time | Until the tab closes |
| Ads (piratini.io only) | |||
_gcl_au, _gcl_* | Google cookies | Google Ads conversion measurement: links a visit to the ad that brought you | Up to 90 days (Google's default) |
The Google cookies are set only where consent allows them (above).
Who receives data
- Cloudflare carries piratini.io's traffic and protects it from attacks, and where a server uses its TURN service, relays voice chat (your IP address and the encrypted audio).
- The voice relay's operator (the Piratini crew, or Cloudflare as above) sees your IP address while voice is on.
- Google runs the tag, analytics and ad measurement on piratini.io, the STUN servers that direct voice chat uses where a host chose it, and, where a server has sign-in enabled, Firebase Authentication (your account id, and your Google e-mail and name if you link Google).
- Other players see your name, looks and chat; your IP address only on a server whose host chose direct voice.
Both companies are based in the United States, so data reaches the US. They rely on the EU-US Data Privacy Framework and the European Commission's standard contractual clauses for that transfer.
How long it is kept
- Browser storage and cookies: as listed above.
- Battle ships: as long as they hold something, until deleted on request or reset; empty ones 7 days.
- Sign-in accounts (servers with sign-in enabled): until you delete them with Delete my data or ask us to.
- Crew voyage saves: until the host resets the save.
- Server logs (joins, refusals): as long as the host's log storage keeps them.
- Chat reports: in a file of about 1 MB plus one older file; the oldest reports drop out as new ones come in.
- Google Analytics: for the retention period set in our Google account.
Your rights
You can ask for a copy of the data held about you, have it corrected or deleted, object to how it is used, and withdraw consent at any time (the settings switch or Privacy choices does this for analytics and ads). Write to the host's contact address (this host has not set one yet); we answer within 30 days. For a battle ship, tell us its recovery code so we can find it. To erase what this browser and the server hold about you yourself, open the settings and press Delete my data: it drops your name, looks, settings, battle ship, gold and renown and ends your recovery code. If you are unhappy with the answer you can complain to your data protection authority.
US state privacy rights
We do not sell personal information. Google's ad measurement may count as "sharing" for advertising under some US state laws: you can opt out with the "Analytics & ad cookies" switch or Privacy choices, or by writing to us. A browser's Global Privacy Control signal is treated as that opt-out.
Children
The game is not directed to children under 13 and we do not knowingly collect their data. A parent or guardian who thinks their child's data is here can write to the host's contact address (this host has not set one yet) and we will remove it.
Advertising
No ads are shown in the game yet. Advertising may be added later; this page will be updated before it is.
Changes to this policy
When this policy changes, the new version is posted here with a new effective date.