Updated October 2, 2026

Privacy policy

Google sign-in and the account save behavior described below are being prepared for release. Until they are available, existing game saves stay in this browser.

This policy explains how BattleSea at battlesea.io handles your information. You can play as a guest or use Google to create a captain account.

Google sign-in and captain accounts

When you sign in, Google provides an account identifier, verified email address and basic profile information. BattleSea uses this information to authenticate you and associate you with your captain account. We store an account ID derived from Google's identifier, your email address, the permanent username you choose, account creation and username-selection timestamps, and session records.

Your chosen username appears in multiplayer. Other players are not shown your Google email address or private session credentials. Usernames may be shared by different accounts.

BattleSea does not receive your Google password. We do not retain Google access or refresh tokens. We do not sell Google account information or use it for advertising.

Ships, progress and multiplayer

Signed-in ships, progress, settings and ship portraits are saved in your browser on the current device. Each captain has separate saves. These saves do not sync between devices. Signing out keeps the captain's local saves so they can be restored on the same device.

Guest game progress is held in memory and is discarded when you reload, close the game or sign in. Guest progress is not imported into a captain account.

Multiplayer sends your username, ship design, match actions and connection information to the game server. Match state and checkpoints are stored to run matches, enforce room membership and support recovery. Opponents receive the game information needed to play. This multiplayer storage is separate from your device's saved career.

Cookies and service providers

BattleSea uses essential cookies for the Google sign-in flow and your account session. Server-side session records contain a hash of the session credential. Sessions expire after 30 days; signing out revokes the current session. Browser storage also holds local saves, preferences and temporary match-reconnection information.

Google provides authentication. Cloudflare delivers the website and network traffic, and Rivet hosts the game and account services. These providers process information needed to operate their services, including network information such as IP addresses and request metadata. Service logs and backups can remain after a browser session ends.

BattleSea uses account and connection information to provide the game, maintain sessions, resolve errors and protect access. This release does not include advertising or behavioral-tracking cookies.

Your choices and data requests

You can sign out in the Account menu, export your fleet through Settings, or remove local saves by clearing this site's browser storage. Clearing local storage does not delete the server-side captain record. Keep an exported backup if you want to retain your fleet.

You can remove BattleSea's Google access in your Google account connections. This does not by itself delete your BattleSea account or revoke an already active BattleSea session; sign out separately.

We retain your captain record to support returning sign-ins. To request access to or deletion of server-side account information, or to ask a privacy question, contact admin@battlesea.io from the email associated with your account. We may ask you to verify ownership before acting on a request. Necessary security records and provider backups may be retained separately.

If this policy changes, the revised version and its update date will appear on this page.