- NavalStrike runs on servers in Germany. There is no advertising, no third-party tracking, and no disclosure of data for advertising purposes.
- We store what the game needs: the account, the matches, the settings. We keep a small usage statistic ourselves, without third-party services; in it, we do not recognize visitors without an account from one day to the next.
- Three services outside our server are involved: Stripe for processing subscription payments, Black Forest Labs for the AI portrait (only if you initiate it yourself, Section 12), and Mistral AI for categorizing your feedback (without name or account ID, Section 15).
- All cookies and browser storage are technically necessary. The cookie notice is a notice, not a consent request, because there is nothing to consent to.
- You can delete your account yourself at any time. Child profiles are created and managed by parents.
1. Controller
The controller within the meaning of the General Data Protection Regulation (GDPR) is:
Falco Stief c/o Impressumservice Dein-Impressum Stettiner Str. 41 35410 Hungen Deutschland Email: ahoi@navalstrike.deThere is no data protection officer; there is no obligation to appoint one for a service of this size. For questions about data protection, you can reach us at the email address given above.
2. Principles
- Data minimization. We only ask for what the game needs. An email address, a password, and a captain name are sufficient for an account; first name and month of birth in the profile are optional.
- No third-party content in the browser. Fonts, images, music, and scripts come from our own server. When the game is accessed, no connection is established to Google, social networks, or advertising networks.
- Encrypted transmission. All connections use HTTPS; the browser is instructed not to attempt an unencrypted connection for one year.
- Legal bases. Unless otherwise stated, we process data to perform the user agreement with you (Art. 6(1)(b) GDPR) or on the basis of our legitimate interest in secure, stable, and fair game operation (Art. 6(1)(f) GDPR). Where consent or a legal obligation is the basis, this is stated in the respective section.
3. Hosting and Server Logs
NavalStrike is hosted by ALL-INKL.COM – Neue Medien Münnich, Inhaber René Münnich, Hauptstraße 68, 02742 Friedersdorf, Deutschland. On our behalf, the host processes all data stored on the server and in the database and sends our emails. A data processing agreement pursuant to Art. 28 GDPR is in place with the host.
The data centers are located in Dresden and Friedersdorf, the service center in Friedersdorf. All processing takes place within the European Union; a transfer to a third country is contractually excluded unless we consent to it.
The host in turn uses one subprocessor, which provides staff and computing infrastructure for contract management, support, and data center operations: Neue Medien Münnich GmbH, Bautzener Straße 56, 02742 Neusalza-Spremberg, Germany. It is bound by the same obligations as the host itself.
For technical reasons, the host's web server stores a log line for each request: IP address, time, requested address, response status, amount of data transferred, browser identifier, and, where applicable, the previously visited page. These logs serve security and troubleshooting purposes and are deleted automatically after 14 days. They are not evaluated routinely; they are evaluated only for a specific reason, such as after a malfunction or an attempted attack.
Legal basis Art. 6(1)(f) GDPR (operational security).
4. Cookies and Local Storage
NavalStrike uses only cookies and browser storage that are necessary for the game. There are no statistics, advertising, or third-party cookies. This is why the notice on your first visit is a notice and not a request for consent (Section 25(2) no. 2 of the German Telecommunications Digital Services Data Protection Act, TDDDG). In detail:
| Name | Type | Purpose | Duration |
|---|---|---|---|
ns_cookie_ack |
Cookie | Stores that the cookie notice has been displayed so that it does not appear on every visit. | 365 days |
ns_lang |
Cookie and localStorage | The selected language of the game. The server needs the cookie to deliver the page in that language right away; the entry in browser storage keeps the choice in case the cookie is deleted. Set only when you choose a language or open a link that specifies a language. | 365 days (cookie), until deleted in the browser (localStorage) |
ns_beta |
Cookie, signed, readable only by the server | Only during the closed beta: proof that the access code has been entered. Contains an expiration date and a checksum, no account data. | 90 days |
PHPSESSID |
Cookie | Only during the closed beta, only on the access page: remembers the access granted for the current visit and counts failed attempts. | Until the browser is closed |
ns_token |
localStorage | The login key, so that you remain logged in on your next visit. Only the browser and our server know it. | Until logout, at most until the session expires (Section 7) |
ns_name, ns_email, ns_auth_type |
localStorage | Display the logged-in account in the menu without asking the server each time. | Until logout |
ns_name_suggestion |
localStorage | The most recent randomly suggested captain's name and its language, so that the suggestion changes along with the language. Names you enter yourself are not stored here. | Until logout or deletion in the browser |
ns_diary_reactor |
localStorage | A random value under which your reactions (heart, arrow up or down) to logbook entries are counted, so that a second click takes the reaction back instead of doubling it. It is not linked to an IP address or device. With a registered account or child profile, the account counts instead (Section 9). | Until deleted in the browser |
ns_music_*, ns_sound_*, ns_voicelines_* |
localStorage | The audio settings: on or off, volume. | Until deleted in the browser |
ns_register_prompt |
localStorage | Only for guest accounts: when you were last asked to create an account, how often “Later” was chosen for each occasion, and how many matches were played in this browser. This way, the game asks at most once a day and no longer asks for an occasion after three refusals. | Until deleted in the browser |
ns_checkout_pending |
sessionStorage | Stores a started payment process until you return from the checkout page. | Until the tab is closed |
All entries can be deleted at any time via the browser settings. Without
ns_token, you will then be logged out; without ns_beta,
the access code must be entered again. Otherwise, the game continues to work
unchanged.
Legal basis Section 25(2) no. 2 TDDDG; Art. 6(1)(b) and (f) GDPR.
5. Playing as a Guest
The game can be used without registration. In this case, the game creates a guest account, for which we store: the chosen or randomly assigned captain name (Gast_ followed by five digits; in other languages the local word for “guest”, such as Guest_), the time of creation and of the last visit, and the game record (matches played and won, shots fired, hits, ships sunk, experience points, results against the computer), as well as the language of the game so that it carries over to other devices. An email address, a password, or the IP address are not included. Against the computer, the guest account is created only at the end of a ranked match, when the game reports the result (Section 9).
The guest account is tied to the login key in the browser (Section 4). If the key is lost, the account can no longer be accessed. Guest accounts that have not been visited for 30 days and have left no trace (no match, no lobby, no subscription, no family) are deleted automatically. If a guest account has played, it remains as long as its matches are stored (Section 9) and is then also deleted. Results against the computer do not count as a trace; they are deleted together with the guest account.
If you register from a guest account, we continue that account: the game record, experience points, medals, and matches are retained, supplemented by the information under Section 6 and the time of the transition. The confirmation email states the previous guest name and the experience points so that the owner of the address can see which game progress is to be linked to it. If the address is not confirmed within 30 days, the account becomes a guest account again; the address, password, and login ID are deleted in the process.
Legal basis Art. 6(1)(b) GDPR (user agreement).
6. Registration and Account
6.1 What We Store
- Mandatory information: email address, password (only as a bcrypt hash, never in plain text), and captain name. From the captain name, we derive a login ID, which is shown in the profile.
- Optional information in the profile: first name, year and month of birth, a captain portrait from the catalog or an uploaded photo (Section 12), a decorative frame, a profile motto. First name and birth details are not shown to other players.
- What the game generates: game record and experience points as for the guest account, the language of the game, the time of the last name change, the status of the email confirmation, family membership, subscription status, and, once the Ehrenloge is used, a customer ID of the payment service provider (Section 10).
6.2 Email Confirmation
After registration, we send a confirmation link with a random key that is valid for 24 hours. The account remains inactive until it is confirmed. The same procedure applies when the email address is changed. We store when the address was first confirmed. Newly created accounts whose address has never been confirmed after 30 days and that have neither matches nor experience points are deleted.
6.3 Check for Disposable Addresses
During registration, when the address is changed, and when a family member is invited, we check whether the email address belongs to a disposable email service. Such addresses prevent the user from being reached and are used for abuse. The check runs in three steps, all using only the domain part of the address (what comes after the @):
- Comparison with a list of known disposable domains on our server.
- Comparison with patterns typical of such services.
- A DNS query as to whether the domain can receive emails at all. Only the domain part is transmitted to the name service.
All three steps run on our server. An external checking service has no longer been used since September 11, 2026.
Legal basis Art. 6(1)(b) GDPR (account); Art. 6(1)(f) GDPR (abuse prevention in the address check).
7. Login, Sessions, and Abuse Prevention
7.1 Sessions
With every login, including as a guest, the server generates a random session key. The browser stores it (Section 4); the server stores only its hash, the time of creation and of the last access, the expiration date, and the browser identifier with which the session was created. A session is valid for 90 days and is extended with use. Log out ends it on the server immediately; a password change ends all other sessions of the account. Expired sessions are deleted daily.
7.2 Failed Logins
To protect passwords against brute-force guessing, we count failed attempts per account (with the time of the last failed attempt; the counter expires after 24 hours without a new failed attempt and is deleted upon successful login) and per IP address. For this purpose, the IP address is kept in a counter table for no more than one hour and is then deleted. From the fourth failed attempt onward, the waiting time until the next attempt increases; accounts are not locked.
7.3 Rate Limiting
So that a single computer does not overload the server, we count requests per minute: per account for logged-in accounts, per IP address for everyone else. The counter, including the IP address, becomes invalid after 60 seconds and is deleted no later than the daily cleanup.
7.4 Forgotten Password
When a new password is requested, we generate a random key that is valid for one hour and send it to the address stored in the account. The response to the request is always the same, so that no one can use it to find out whether an address is registered. Expired requests are deleted seven days after expiry.
Legal basis Art. 6(1)(b) GDPR (login); Art. 6(1)(f) GDPR (security of the account and of operations).
8. Family Accounts and Child Profiles
With a suitable Ehrenloge package, a main account can add further profiles. The following applies:
8.1 Child Profiles
Child profiles are created exclusively by the main account. For this, we store the captain name, a username, the password as a hash, a captain portrait from the children's catalog, the assignment to the main account, and, if set, a daily playing time limit. To enforce the limit, we count the minutes the profile has played per day. A child profile has no email address; its game record and matches are stored as for any other account.
The main account gives consent to this processing when creating the profile, as a parent or person with parental responsibility (Art. 8 GDPR). The main account can reset the password, change the limit, and delete the profile at any time; this withdraws the consent and anonymizes the profile (Section 17). If the main account is deleted, its child profiles are deleted along with it.
8.2 Member Accounts and Invitations
The main account invites adult family members by email. For this, we store the invited address, the captain name of the person inviting, an invitation key, and the expiration date. The invited person registers themselves with their own account; until they have confirmed their address, they are not assigned to the family. Expired invitations are deleted 30 days after expiry; open invitations lapse with the main account. A member account is an account of its own under Section 6, about whose holder we disclose nothing beyond the invitation except that the family membership and the resulting premium benefits exist.
Legal basis Art. 6(1)(b) GDPR (contract with the main account); Art. 6(1)(a) in conjunction with Art. 8 GDPR (child profiles, parental consent); Art. 6(1)(f) GDPR (email address of the invited person until registration, in the interest of the person inviting).
9. Matches and Other Players
For each match, we store the participants, the battle mode, fleet placements, every shot with target and result, the course of the game for reloading during the match, the winner, and timestamps. For lobbies, we store the join code, host, participants, settings, and whether someone joined via a shared invitation link.
Based on matches, the game record, and days of use, we award medals (“Awards” tab in the captain's file). For each medal, we store the level, the time, and the match in which it was earned. The profile of the respective account shows the current status. Other players in the same match receive, together with the match result, the list of medals newly awarded in it.
Matches against the computer run in the browser. At the end of a ranked match, the game transmits both fleet placements and the sequence of moves; the server replays the match with them and then awards experience points and medals. Of this, we store only the opponent, battle mode, outcome, shots fired, hits, ships sunk, moves, duration, the experience points awarded, and the time. Placements and the sequence of moves are discarded after the check. The profile of the account shows the number of matches and wins against the computer.
We store each credit of experience points individually with its reason (match, medal, daily order, streak, match against the computer), time, and, where applicable, the match, plus the total per calendar week. For each battle mode, we keep a record (matches, wins, shots, hits, ships sunk). For the daily order, we store the assignment for each day, the progress, and whether it was completed; for the streak, the number of consecutive days with a ranked match and the last such day. Child profiles do not see their streak.
The leaderboard shows logged-in players the top places of the week and overall, with captain name, captain portrait from the catalog (never an uploaded photo or AI portrait), rank, and experience points. Registered accounts with a confirmed address that have not turned off the listing in their profile are listed. Guest accounts are not listed; we only tell them their own place. Child profiles appear exclusively in a separate children's leaderboard, which only other child profiles can see; the main account can turn off the listing for each child profile in family management.
With the Ehrenloge, the battle archive shows the account itself its matches from the past year with opponent, outcome, hit rate, duration, and experience points. It reads the same data as above and stores nothing additional.
Anyone can react to entries in the logbook on the start page with a heart, an arrow up, or an arrow down. We store the reaction, the entry, the time, and – depending on how you are logged in – the number of your registered account or child profile or the random value from your browser (Section 4). Others see only the totals per entry. If you log in with an account, we transfer the reactions previously given in the same browser to the account so that they are not counted twice. Reactions of an account are deleted with the account, reactions without an account with the entry.
Other players are shown the information required for game operation: captain name, captain portrait including frame, rank, and, within the match, the moves. Public lobbies show the captain name and battle mode to everyone who opens the lobby list. The fleet radio on the start page shows all visitors, for 48 hours, completed one-on-one battles with the captain names of the winner and the loser, battle mode, number of moves, and time, as well as the captain names of new accounts after their email address has been confirmed. Child profiles and deleted accounts do not appear there, not even as opponents. The number of captains “in port” does not include any names. Email address, first name, birth details, and family membership are not shown to third parties; for child profiles, they are additionally accessible to the main account.
The course of a completed match is deleted after 7 days, the match itself after 365 days; closed lobbies without a match after one day. The game record remains in the account as a total, as do the medals awarded. We delete individual credits and weekly totals after 365 days, uncompleted daily orders after 30 days; completed ones count toward a medal and remain with the account.
Legal basis Art. 6(1)(b) GDPR.
10. Ehrenloge and Payments (Stripe)
Payments for the Ehrenloge are processed by Stripe: Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland. When you subscribe, you are redirected to a Stripe checkout page. There you enter your payment details and your name; this information does not reach our server.
The free seven-day trial runs without Stripe: we store only its start and end in the account and send a confirmation to the stored address. After it ends, we reset the premium frame, premium captain portrait, and premium motto, unless a subscription is active.
10.1 What Is Sent to Stripe
On your first subscription, we create a customer record at Stripe and transmit the email address stored in the account (none for guest accounts) and the in-game account number for this purpose. With each payment process, the selected package and the term are added. Discount codes are entered directly at Stripe.
10.2 What Comes from Stripe and What We Store
Stripe notifies us whether a payment was successful, as well as of changes to the subscription. We store: package, term, start, end, status, amount at conclusion, the Stripe IDs of the customer, subscription, and checkout session, and, for each invoice, the invoice number, amount, currency, status, payment method, and date. We keep the ID of every processed notification so that no notification takes effect twice. For display in the game (Premium → History), we retrieve from Stripe the brand and the last four digits of the stored payment method as well as the invoices; of this, we store only the payment method as a word (such as “card”).
10.3 Role of Stripe and Transfer to Third Countries
As a regulated payment institution, Stripe is itself the controller for payment processing and processes the data in accordance with its own privacy policy at stripe.com/de/privacy. Stripe may transfer data to Stripe, Inc. in the USA; this is based on the certification of Stripe, Inc. under the EU-U.S. Data Privacy Framework and the Standard Contractual Clauses of the European Commission.
10.4 Retention
Subscription and payment data are subject to retention obligations under tax and commercial law and are retained for up to ten years after the end of the year in which the payment was made (Section 147 of the German Fiscal Code, AO; Section 257 of the German Commercial Code, HGB), even after the account has been deleted. At that point, a personal reference exists only via the Stripe IDs.
10.5 Cancellation Without Logging In
The subscription can also be canceled without logging in (Section 312k of the German Civil Code, BGB). To do so, the account's email address is entered in the login dialog. Entering it does not yet cancel anything: we send a confirmation email to the address stored in the account, and only opening the link it contains declares the cancellation. This intermediate step is necessary so that third parties who merely know an email address cannot end other people's subscriptions.
For such a request, we store: the account number, the ID of the subscription concerned, the hash of the link sent, its expiration time, the time of confirmation, and a hashed value of your IP address. The hash of the IP address serves solely to fend off abusive mass requests and cannot be converted back into the address. The link itself is not stored in plain text.
The response to a request is always the same, regardless of whether an account exists for the address entered. Otherwise, this input could be used to find out who has an account with an active subscription here.
Unconfirmed requests are deleted seven days after the link expires. Confirmed requests remain as proof of when and by what means a cancellation was declared and are subject to retention under Section 10.4.
Legal basis Art. 6(1)(b) GDPR (subscription, cancellation); Art. 6(1)(c) GDPR (retention obligations and Section 312k BGB); Art. 6(1)(f) GDPR (hashed IP address for abuse prevention).
11. Emails
We send only emails that concern the account. There is no newsletter. In detail:
- Confirmation of the email address after registration and change of address; welcome email after confirmation.
- Link to reset the password upon request.
- Invitation to a family when a main account issues an invitation.
- For the Ehrenloge: welcome to the subscription, confirmation of cancellation, notice of a failed charge.
- Confirmation link for a cancellation without logging in (Section 10.5).
- Notice in case of non-use: If the game is not used for 30 days while a subscription is active, we point out once that the subscription continues and explain how to cancel; this is repeated no earlier than after another 60 days.
Emails are sent via our host's mail server (Section 3). We do not store whether an email was opened; the emails contain no tracking pixels.
Legal basis Art. 6(1)(b) GDPR; for the inactivity reminder, also Art. 6(1)(f) GDPR (fair performance of the contract).
12. Uploaded Photos and AI Portrait
In the profile, you can upload your own photo (JPEG, PNG, or WebP, max. 5 MB), from which a captain portrait in the style of the game is created. The file is stored under a random name in a directory of the account on our server and can be accessed via its address; the directory cannot be browsed, and uploaded files are never executed as programs.
A face is biometric data as soon as it is suitable for identification. Generation therefore starts only after explicit prior consent – via a checkbox that is not preselected. We record the time of this consent. Without it, no photo is transmitted and no generation is started.
Recipient For generation, the photo is transmitted to Black Forest Labs GmbH, Freiburg im Breisgau, Germany, which processes it on our behalf as a processor. The processing takes place within the EU; it does not involve a transfer to a third country. The sole purpose is to convert the photo into three image versions (avatar, large portrait, battle portrait). Only the photo itself is transmitted, no other account data; for the provider's abuse detection, an internal account number is included, which does not allow the provider to identify any person.
The generated images are stored on our server and become part of the profile only when they are explicitly accepted. Discarded results are deleted immediately.
We delete the uploaded photo as soon as a portrait has been accepted. If none is accepted, it remains stored for further attempts for no more than seven days after the last attempt and is then deleted automatically.
Each account can accept two portraits within three months; we keep track of the number with timestamps. Only photos that show the user themselves or for which the person depicted has given consent may be uploaded. The feature is not available for child profiles. The files are deleted as soon as they are replaced by new ones or the account is deleted.
Withdrawal Consent can be withdrawn at any time with effect for the future. Images already generated can be deleted by choosing a different captain portrait from the catalog; the lawfulness of the processing carried out until then remains unaffected.
Legal basis Art. 9(2)(a) GDPR (explicit consent to the processing of biometric data); for storing the photo, also Art. 6(1)(b) GDPR (optional profile feature).
13. Usage Statistics
To find out whether the game works on phones, which battle modes are played, and when the server is under load, we keep our own statistics. They run entirely on our server; no third-party analytics service is involved.
For each visit, we store a session line with:
- device type (phone, tablet, desktop), screen size, browser identifier, and, if available, the address of the previously visited page;
- a hash of the IP address, formed with a secret salt and the current date. It allows visits on the same day to be counted together, but cannot be converted back into the address and changes daily, so that recognition across days is impossible;
- start, end, and duration of the visit, the number of screens visited, and the number of matches started and completed;
- the entry address without parameters and, if the link carries one, a source
identifier (such as
?ref=discord), so that we can see which references to the game actually bring visitors; - the account number, if logged in.
For each account (including guest accounts), we also record the calendar days on which it used the game – only the date, no time and no activity. From this, we calculate how many new players return the following day or the following week; only totals are evaluated.
In addition, there are individual events from a fixed list: screen change, match won or lost, registration started, login and logout, email confirmed, family invitation opened, lobby created or joined, single-player match started, logbook opened, “Save progress” notice shown, accepted, or declined (with the occasion). The server does not accept any other events. The server itself records the start of an Ehrenloge trial as an event with the account number and counts it as a daily total. Nothing is stored on the device for the statistics; the browser keeps the ID of the statistics session only in memory.
We delete session lines, individual events, and days of use after 365 days, and days of use also with the account. Daily and hourly totals without personal reference (such as “visits per day”) are retained.
Legal basis Art. 6(1)(f) GDPR (improving the game and planning operations). You can object to this processing (Section 18).
14. Error Logs
If an error occurs in the game, the server writes a line to an error log and displays a random ID. If you tell us this ID, we can find the line. It contains the error message, the requested address, and, where applicable, the account number, but no passwords and no payment data. The log is truncated after no more than 30 days.
Legal basis Art. 6(1)(f) GDPR (troubleshooting and operational security).
15. Feedback from the Game
In the game, there is a Report a bug button on the right edge of the screen. Anyone who uses it describes in a form what happened and what was expected, and chooses how serious the issue is. The report is sent to us. For categorization, we additionally transmit the text – without your name and without your account number – to a service provider in the EU; for details, see Categorization by a language model below.
Together with the text, we automatically transmit:
- the captain name and, if logged in, the account number – never the email address;
- the screen you were on and the current battle mode;
- the browser identifier, the size of the browser window, the resolution of your screen, and the ratio between the two. Most display errors are size errors: without these three pieces of information, an error that only occurs in a narrow window or only on a very large screen cannot be reproduced;
- the build ID of the version used, the selected language and the time;
- the most recent error messages the browser has recorded in the background (no more than twenty);
- on request, a screenshot of the view from which you are reporting.
The screenshot is preselected in the form, shown to you as a preview before sending, and can be deselected. It shows what was visible on your screen – so also your captain name and captain portrait and, in the waiting room and in battle, the names and portraits of other players. This is data that is shown to you anyway; it is transmitted nonetheless, which is why it is mentioned here.
We delete reports 180 days after they have been processed, and the screenshots after just 90 days – the image shows more than the text and is needed only as long as the error is open. If you delete your account, the report remains, but without any link to your account: it describes an error in the game, not a person. The captain name remains as part of the report.
Reports cannot be submitted from child profiles; the button is hidden there.
Legal basis Art. 6(1)(f) GDPR (improving the game and fixing errors); for the screenshot, additionally your consent under Art. 6(1)(a) GDPR, which you can refuse by deselecting the checkbox before sending.
Categorization by a language model
So that we can tell from many reports what belongs together and what is urgent, we have them categorized by a language model: it writes a one-sentence summary, assigns the report to a category and an area of the game, and recognizes when two reports describe the same thing. On request, it also summarizes the reports of a period in a report.
This does not happen automatically, but only when we explicitly trigger it in the administration area. The categorization is a suggestion; we decide what happens with a report.
The recipient is Mistral AI SAS, Paris, France, which processes the data on our behalf as a processor. We explicitly call the endpoint with processing in the European Union; this does not involve a transfer to a third country. According to the provider, the transmitted content is not used to train its models.
Not everything stored with a report is transmitted. What is sent: the text of your report, the severity you chose, the screen, the battle mode, the build ID, the window size, the browser family (for example “Chrome”, not the full identifier), and the most recently recorded error messages of the browser.
What is not sent: your captain name, your account number, your email address, and the screenshot.
The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest lies in recognizing and grouping reported errors more quickly; we have safeguarded your interest in confidentiality by keeping everything that could identify a person here.
16. Recipients and Third Countries
Besides the provider, the following parties receive data:
| Recipient | What | Where | Basis |
|---|---|---|---|
| Host (Section 3) | Everything stored on the server and in the database; server logs; sending our emails | Germany (data centers in Dresden and Friedersdorf), one subprocessor also in Germany | Data processing on behalf, Art. 28 GDPR |
| Stripe (Section 10) | Email address, account number, package; payment data is entered directly there | Ireland; transfer to Stripe, Inc. (USA) possible | Independent controller; DPF certification, Standard Contractual Clauses |
| Mistral AI (Section 15) | The text of a feedback report together with screen, battle mode, build, and browser family – without name, account number, and screenshot, and only when we trigger the categorization | European Union (endpoint with EU processing) | Data processing on behalf, Art. 28 GDPR |
| Black Forest Labs (Section 12) | The uploaded photo and an internal account number – only for AI portrait generation, only after explicit consent | Germany (Freiburg im Breisgau) | Data processing on behalf, Art. 28 GDPR; consent under Art. 9(2)(a) GDPR |
| DNS resolution (Section 6.3) | Only the domain part of the email address | Via our host's name service | Art. 6(1)(f) GDPR |
The services we use to create fixed content of the game receive no data from you: the game texts are translated into other languages by a language model of Mistral AI SAS, Paris, France, on servers in the European Union; the voice recordings of fixed game texts are generated by ElevenLabs. Only the predefined texts of the game are transmitted in the process, no personal data. The finished translations and recordings are delivered by our own server; there is no connection to these services while you play.
Authorities receive data only if we are legally obligated to provide it. Data is not disclosed for advertising purposes or sold.
17. Storage Period and Deletion
17.1 Deleting Your Account
The account can be deleted at any time in the game (Open profile → Security → Delete account). This removes the email address, password, first name, birth details, captain portrait, customer ID, family assignment, and all sessions; the captain name is replaced by Gelöschter Kapitän (“Deleted Captain”) with a number; an active subscription is canceled. Uploaded photos are also removed from the server as files (Section 12). Child profiles of the account are treated in the same way, and member accounts are detached from the family. Open cancellation requests under Section 10.5 lapse with the account.
Completed matches remain in anonymized form because they are also part of the other players' game history; after that, no conclusions about the person can be drawn. Data that must be retained by law (Section 10.4) remains until the end of the retention period.
17.2 Overview of Periods
| Data | Deleted |
|---|---|
| Guest account without a match | 30 days after the last visit |
| Registered account | Upon deletion by the user (anonymization) |
| Confirmation key for the email address | Invalid after 24 hours |
| Password reset | Invalid after 1 hour, deleted 7 days after expiry |
| Session | 90 days after the last extension, then deleted daily |
| Failed attempts per account | 24 hours after the last failed attempt or upon successful login |
| IP address in login protection and rate limiting | 1 hour or 60 seconds respectively, no later than the daily cleanup |
| Family invitation | 30 days after the invitation expires |
| Unconfirmed cancellation request | 7 days after the link expires |
| Course of a completed match | 7 days after the end |
| Match | 365 days after the end |
| Closed lobby without a match | 1 day |
| Usage statistics (sessions, events) | 365 days |
| Days of use per account | 365 days, at the latest with the account |
| Medals awarded | With the account |
| Individual XP credits and weekly totals | 365 days, at the latest with the account |
| Record per battle mode, streak, completed daily orders | With the account |
| Uncompleted daily order | 30 days |
| Registration from a guest account, address never confirmed | Address, password, and login ID after 30 days; the guest account remains |
| New account, address never confirmed, without a match | 30 days after creation |
| Result of a match against the computer | With the account |
| Reaction to a logbook entry | With the account; without an account, with the entry |
| Host's server logs | 14 days |
| Error log | No more than 30 days |
| Feedback from the game | 180 days after processing |
| Screenshot attached to feedback | 90 days |
| Uploaded photo | When replaced or with the account |
| Subscription and payment data | Up to 10 years (statutory retention) |
The deletion periods are implemented by a cleanup run that takes place once a day. The host's backups may continue to contain deleted data for a short time; they are overwritten on a regular cycle and used only to restore data after an outage.
18. Your Rights
Under the GDPR, you have the following rights vis-à-vis the provider:
- Access (Art. 15) to the data stored about you.
- Rectification (Art. 16) of inaccurate data; most information can be changed in the profile yourself.
- Erasure (Art. 17); you can delete the account yourself (Section 17).
- Restriction of processing (Art. 18).
- Data portability (Art. 20): receiving the data you have provided in a common format.
- Withdrawal of consent (Art. 7(3)) with effect for the future, for example for a child profile.
Insofar as we process data on the basis of a legitimate interest (Art. 6(1)(f) GDPR), you may object at any time on grounds relating to your particular situation. We will then no longer process the data unless we can demonstrate compelling legitimate grounds that override your interests, or the processing serves the establishment, exercise, or defense of legal claims. For the usage statistics (Section 13), an informal email is sufficient.
For all requests, an email to ahoi@navalstrike.de is sufficient. To rule out disclosing other people's data, we ask that you send the request from the address stored in the account or state your captain name.
You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), for example with the authority responsible for the provider: Berliner Beauftragte für Datenschutz und Informationsfreiheit. A list of all supervisory authorities in Germany is maintained by the Federal Commissioner for Data Protection at bfdi.bund.de.
19. Children and Adolescents
An account of one's own with an email address can be created from the age of 16 (Art. 8 GDPR). Younger players take part via a child profile that a parent creates in their family (Section 8). Child profiles have no email address, do not see any payment features, and can only be managed and deleted by the main account. We do not ask for a date of birth during registration; the information in the profile is optional and is not used for age verification. If we learn that an account of its own was created by a child under 16 without parental consent, we delete it.
20. Data Security
- We store passwords exclusively as bcrypt hashes; no one on our side can read them.
- Session keys are stored on the server only as hashes; a database dump contains no valid access.
- IP addresses in the statistics are hashed with a secret salt and the current date and cannot be converted back.
- The browser receives protective instructions against embedding in third-party pages, guessing of file types, and unencrypted connections; uploaded files are never executed as programs.
- The server does not load scripts or fonts from third parties; everything that runs in the browser comes from us.
- Secrets such as database credentials and the payment service provider's keys are kept outside the source code and are replaced if misuse is suspected.
- The database and web space are backed up daily so that the data can be restored after a malfunction (Art. 32(1)(c) GDPR). The backups are kept by the host in Germany and are overwritten on a regular cycle; they are used for restoration only in the event of a malfunction.
There is no automated decision-making or profiling within the meaning of Art. 22 GDPR. The computer opponents in the game make decisions about moves, not about people.
21. Changes
This policy is updated when the game changes: with a new feature, a new service provider, or a changed period. The currently applicable version is available at this address; the date of the version is shown at the end of the page. In the event of material changes, in particular new recipients, we will point this out in the game or by email.