Privacy policy

1. Who is responsible

The controller for the game and this website is:

Ing. Ondřej Novotný, Ph.D. (developer name on Google Play: OndraN)
IČO 19525567, Nové sady 988/2, 602 00 Brno, Czech Republic
E-mail: 0ndr4N@proton.me

Write to this address for every question about your data. We have not appointed a data protection officer. Please include your Support ID (in the game under Settings › About) so we can find your captain.

2. What we process and why

2.1 Your game account

The game creates a guest account automatically on the first start. There is no e-mail, password or real name.

• Account identifiers: a random player id (shown as the Support ID), the captain name the game generates for you (an adjective, a noun and a number; never free text) and earlier names if you pick a new one, the account status and when it was created and last used.
• Sign-in data: a secret that signs your device in, and sign-in tokens. On our server we store only one-way hashes of them, plus a list of sign-ins (method, created, last used, revoked). On your phone the secret is stored encrypted with a key that never leaves the device.
• Google Play Games (optional): if you link your captain to Play Games, our server stores your Play Games player id so that you can restore your captain on a new device. It does not ask for your e-mail address and does not store your Play Games name or picture.
• Age band: on the first start the game asks for your year of birth. Only the result under 16 or 16 or older is stored (on the phone and on our server), never the year.
• Game progress: resources, ships, buildings, research, crew, contracts, tasks, achievements, event scores, battles and battle reports, messages from the game, and a ledger of every change to your resources.

Purpose and legal basis: to provide the game you asked for (Art. 6(1)(b) GDPR, contract). The age band is used to protect younger players (section 6); our basis is our legitimate interest and our duties towards minors (Art. 6(1)(f) and Art. 8 GDPR).

2.2 Fair play and security

• Our server checks results it receives from the game (for example how long a battle took or how much a ship could carry). Implausible results are recorded as anti-cheat signals (kind, severity, details).
• To protect the server from abuse it counts requests per network address. Full IP addresses are only held in the server's memory for this; the server does not write them to its logs or database.
• Technical logs of our server (time, request id, method, path, status, duration and, where relevant, the player id) contain no IP addresses, no sign-in tokens and no request contents.
• The web server in front of our server (nginx) logs each request with a shortened network address (the last part removed: IPv4 /24, IPv6 /48), the time, the path without parameters and the status. Its error log can contain the full IP address of a failed request.

Purpose and legal basis: fair play, preventing cheating, fraud and attacks, and running a stable service (Art. 6(1)(f) GDPR, legitimate interests).

2.3 Purchases

Purchases are optional and are paid through Google Play. We never see your payment details. To deliver and restore items and to handle refunds we process: the product, the Google Play order number, the purchase state and times, a one-way hash of the purchase token (the token itself for at most 3 days while a purchase is being confirmed), what was granted and any refund. To link a purchase to your captain, the game gives Google Play a one-way hash of your player id, never the id itself.

Legal basis: contract (Art. 6(1)(b) GDPR) and, for purchase records we must keep, legal obligations such as tax and accounting rules (Art. 6(1)(c) GDPR) and our legitimate interest in handling refunds and chargebacks (Art. 6(1)(f) GDPR).

2.4 Rewarded ads

Ads appear only when you tap a button to watch one in exchange for a stated reward. The ads come from Google AdMob. To grant the reward only after a completed ad, the game passes to AdMob a one-way hash of your player id (different from the purchase one) and an offer number; Google sends both back to our server in a signed confirmation. We store the offers and confirmations (time, placement, ad unit, ad network, reward, result) to grant rewards and apply daily limits.

AdMob itself collects data from your device, as Google describes in its own policy: the advertising id (unless you deleted it in Android's settings), the app set id, your IP address and approximate location derived from it, device and app information, ad interactions and diagnostics.

• Personalised ads only if you are 16 or older. In the EEA, the United Kingdom and Switzerland they also need your consent in the privacy message (IAB TCF purposes 3 and 4; Art. 6(1)(a) GDPR). Elsewhere, ads for players aged 16 or older can be personalised without asking first.
• US states with privacy laws (for example California): personalised advertising can count as "selling" or "sharing" personal information under those laws. You can opt out at any time in Settings › Privacy › Privacy options, which then shows Google's US state privacy message; AdMob afterwards limits how it uses your data for ads.
• Non-personalised ads still use device and technical data, for example to limit how often an ad is shown, to measure it and to prevent ad fraud. Where the law requires it, storing or reading information on your device needs your consent in the privacy message.
• Our own records of offers and confirmations: contract (Art. 6(1)(b) GDPR), because they decide the reward you asked for.

2.5 Usage analytics (Google Analytics for Firebase)

Only if you are 16 or older, and you can switch it off at any time in Settings › Privacy › Share usage analytics. Where the GDPR or a similar law applies (the EEA, the United Kingdom and Switzerland) it also needs your consent in the privacy message (IAB TCF purposes 1, 8 and 9).

What is collected: an app instance id and a Firebase installation id, device model, Android version, app version, language, country and approximate region derived from the IP address by Google, and game events such as levels reached, upgrades, contracts, battles, tutorial steps and purchases made through Google Play (product, price and currency). No player id, no captain name, no advertising id.

Purpose: to understand which parts of the game are used and where players get stuck. Legal basis: consent (Art. 6(1)(a) GDPR) where it is required; elsewhere our legitimate interest in improving the game (Art. 6(1)(f) GDPR), with the switch to object.

2.6 Crash reports (Firebase Crashlytics)

Only if you are 16 or older. When the game crashes, a report with the technical error, a Crashlytics installation id, device model, Android version, app version, free memory and disk space, orientation and the time is sent to Google. No player id or other personal details are added. You can switch it off in Settings › Privacy › Send crash reports; switching it off also deletes reports not sent yet.

Legal basis: our legitimate interest in a game that works (Art. 6(1)(f) GDPR). Where the GDPR applies, crash reports are only sent if you allowed storing information on your device in the privacy message (IAB TCF purpose 1), because Crashlytics keeps an id on the device.

2.7 Google Play Games and the privacy message

• The Play Games software in the game talks to Google at every start to check whether you are signed in to Play Games on the phone. Google collects usage and diagnostic data about its service for its own purposes (see Google's privacy policy).
• The privacy message (Google's User Messaging Platform) asks for and stores your consent choices on the phone (as an IAB TCF consent string) and sends a consent request with device and app information to Google. Legal basis: our legal obligation to obtain and record consent (Art. 6(1)(c) and Art. 7(1) GDPR).

2.8 Data on your phone only

Settings, privacy choices, planned notifications and purchases still being confirmed are stored on the phone. Notifications about your crew's work are created on the phone from your own timers; no push service is used. Android's own backup to your Google account (if you turned it on) includes only the game's settings, such as controls, graphics and sound. It does not include your account, your privacy choices or your age answer.

2.9 Data export and support

• When you export your data in the game, we store the time of the last export to allow one export a day.
• When you write to us, we process your e-mail address, your message and anything you include (for example your Support ID) to answer you and, for privacy requests, to show that we handled them (Art. 6(1)(b), (c) and (f) GDPR).

2.10 This website

The website sets no cookies and uses no analytics, trackers, external fonts or other third-party content. Requests are logged by the web server as described in section 2.2.

3. What other players see

Other players can see your captain name, your ship, its cosmetic items, your ranking positions and the outcome of battles with your ships. When you attack another captain's ship, that captain gets a battle report with your captain name. There is no chat and no free text. You can pick another generated name in your profile.

4. Who receives data

Google's privacy policy: policies.google.com/privacy. How Google uses data from apps that use its services: policies.google.com/technologies/partner-sites.

We do not sell your personal data for money and we do not share it for purposes other than those above. Personalised ads from AdMob (section 2.4) may count as "selling" or "sharing" under some US state laws; you can opt out of them in Settings › Privacy › Privacy options.

5. Transfers outside the European Union

Our game server and its backups are hosted in the European Union. Google (Google Ireland Limited and Google LLC) may process data in the United States and other countries. For transfers to the United States, Google LLC is certified under the EU-U.S. Data Privacy Framework; Google also uses the European Commission's standard contractual clauses (Art. 45 and 46 GDPR). Support e-mails are stored by our e-mail provider in Switzerland, for which the European Commission has adopted an adequacy decision (Art. 45 GDPR).

6. Age

The game is intended for players aged 16 and older. On the first start it asks for your year of birth in a neutral way and keeps only the age band. If the answer means you may be younger than 16:

• no usage analytics and no crash reports are sent;
• ads are never personalised, the ad requests are marked as being for a user under the age of consent, and only ads suitable for a younger audience are requested.

If you are a parent and believe your child gave us data, contact us and we will delete the account.

7. How long we keep data

8. Your rights

• Access and portability (Art. 15 and 20 GDPR): Settings › Your data › Export my data saves a copy of everything stored about your captain as a JSON file (once a day). You can also ask us by e-mail.
• Erasure (Art. 17): Settings › Your data › Delete account, or without the app as described on our account deletion page.
• Rectification (Art. 16) and restriction (Art. 18): write to us, for example if you answered the age question wrongly.
• Objection (Art. 21) to processing based on legitimate interests: switch off Share usage analytics or Send crash reports in Settings › Privacy, or write to us.
• Withdrawing consent (Art. 7(3)) at any time, with effect for the future: Settings › Privacy › Privacy options opens the privacy message again.
• Opting out of the sale or sharing of personal data and of targeted advertising (US state privacy laws): Settings › Privacy › Privacy options in the game, or write to us.
• Complaint to a data protection supervisory authority (Art. 77), in particular in the country where you live or work or where you think the law was broken. We are established in the Czech Republic, where the authority is the Úřad pro ochranu osobních údajů, uoou.gov.cz.

We answer requests within one month. To protect your captain we may ask you to prove that it is yours, for example with the Support ID shown in your game.

9. Automated checks

Automatic plausibility checks can hold back a reward or keep a score off the leaderboards until it is reviewed. They have no legal or similarly significant effect on you. If you think a check was wrong, write to us and a person will look at it.

10. Security

The game talks to our server only over encrypted connections (HTTPS). Secrets are stored as one-way hashes on the server and encrypted on the phone. The database cannot be reached from the internet, and backups are checked every day.

11. Changes

We update this policy when the game or the law changes. The effective date is at the bottom of the page. Important changes are announced on this page before they take effect. This version is effective from 2026-11-06.