Paper Battleship

A game of ink & instinct.

Privacy policy

Effective November 6, 2026

I’m Andrei Daniliuk, the developer of Paper Battleship. This policy covers the iPhone and iPad app, its online service and this website.

Solo play

Your saved solo game, records, Music and Sound effects settings stay on your device. You can play solo offline. The app does not send your solo save or records to the game server. Your device may include this data in backups, depending on your operating system and backup settings.

Ads and purchases on iPhone and iPad

The free app may show a Google AdMob ad when you leave selected completed solo games. Ads never interrupt an active game or multiplayer. Ad frequency and completion counters are stored on your device. The app does not send your solo match identifiers, guest identifiers, saves or results to Google.

Ads are requested without personalization. Publisher first-party ID is disabled and the app does not ask for permission to track you across other companies’ apps or websites. Non-personalized ads still involve data processing: Google’s advertising and consent SDKs may process IP addresses and approximate location, device identifiers and device information, ad views and interactions, and crash, performance and other diagnostic data. Google uses this information to deliver and measure ads, prevent fraud and operate its services. Google controls its processing and retention under Google’s Privacy Policy.

Where required, a privacy form appears on the main menu before ads can load. Settings → Privacy & data includes Ad privacy choices when Google requires that option. If privacy status, the Store product or purchase ownership cannot be resolved, play continues without ads. No gameplay analytics service is added; I use aggregate Apple and AdMob reports.

Remove ads permanently is an optional one-time Apple in-app purchase. Apple processes the payment; I do not receive your payment-card information. StoreKit verifies purchase ownership on your device. A local record of verified ownership supports offline access, and verified refunds or revocations remove that access. The purchase can be restored using the same Apple Account on your Apple devices. Family Sharing is not enabled. This purchase covers ad removal only.

Online play

When you play online, the server creates a guest profile for your copy of the app. It uses your sign-in details, game actions, ship positions, shots, results and connection details to run your matches and reconnect you if the connection drops. Your opponent receives the information needed to play, but not your hidden ship positions.

Your guest sign-in details are stored in the iOS Keychain. There is no account linking or way to restore a guest profile on another device. Keep party codes and invitation links private: anyone with a code may be able to join that party.

Notifications

Notifications are optional. If you allow them, the server saves an installation ID and an Apple push token, linked to your guest profile. These let Apple deliver alerts when a friend joins, is ready to play, or it’s your turn. You can turn game alerts off in the app’s Settings or change the app’s permission in iOS Settings. You can still play with notifications off.

Hosting and error reports

The online service and database run on Render in Oregon, United States. Render may process IP addresses and other connection details to deliver requests, protect the service and keep it running. This location does not guarantee that all of Render’s own records or processing stay in Oregon.

I use Sentry to help diagnose server errors. The reports exclude player identifiers, sign-in details, request bodies, IP addresses and game state. They are sent by the server, not by your device. I also count completed multiplayer results to see how the service is running. These counts do not measure individual players or solo games.

The app has no PostHog gameplay analytics or Sentry reporting from your device. Google’s ad SDK does process diagnostic data as described above. Older versions may still use reporting tools that have since been removed. Apple may share usage, performance and crash reports through its own services and sharing settings. TestFlight shares crash reports with developers.

How long data is kept

Detailed match data and records used to handle game actions and connections are normally removed seven days after a match ends. Match summaries are kept for up to 90 days, unless deleting a guest removes them sooner. Some match and join records may remain to stop old requests from reopening ended parties and to let the other player continue. These records are not anonymous.

An unused guest profile can be removed after 30 days of inactivity, once all its sign-in sessions have expired. A profile with a valid session is not removed by this rule. After deletion, a revocation hash remains for 10 minutes and a hashed deletion receipt for 30 days, so the server can confirm a deletion again if the original response was lost.

Sentry stores error reports in its United States data region. Reports received during the trial are kept for 90 days. New reports on the free Developer plan are kept for 30 days; changing plans does not shorten the time already assigned to older reports. Sentry says its error-report backups are deleted 90 days after each backup is made. Some provider access and processing may take place outside the selected region.

The current Render Hobby plan provides seven days of log history and lets the database be restored to a point within the previous three days. Render’s logs are not forwarded to another logging service. Render lists database-export retention as at least seven days. These windows describe what is available through Render; they do not guarantee when every stored copy is permanently erased.

Deleting your guest removes data from the live database. It does not rewrite old backups or remove existing reports held by providers. After a database restore, old sign-in details stop working and recovered matches are blocked, but historical guest and game records remain. The restore process does not automatically repeat deletions made after that backup.

Downloaded backups and copies used for recovery checks can also contain old data. Deleting a guest does not immediately erase those copies. Email me if you have a question about deletion or backups.

Delete your guest and game data

Open Settings from the main menu, choose Privacy & data, then Delete guest and game data. This removes your online guest and associated game data, and clears your local save, records and settings. It can end shared parties and cannot be undone. Online deletion needs an internet connection. If it fails, the app lets you retry. A device-only reset, if offered after a session has expired, does not confirm deletion from the server.

Deleting game data clears local ad-frequency counters. It does not refund or revoke your Apple ad-removal purchase. Use Restore purchases with the same Apple Account to recover ownership.

Deleting game data does not change the notification permission in iOS. An alert that was already sent may still arrive. Opening it checks the latest match state.

Contact and data requests

Email paperbattleship.support@gmail.com with questions or requests about your data. Please do not send passwords, guest sign-in details, notification tokens or private party codes. An email address alone does not always identify a game installation. I may need more information to confirm which data belongs to you.

The support mailbox uses Gmail. If you email me, it receives your email address, message and any attachments. I use these to answer your request and investigate the problem. Messages and attachments stay in the mailbox unless removed. You can ask to access, correct or delete your data, including support emails. Some information may need to be kept to meet legal requirements.

This website

These pages have no analytics scripts, advertising, forms or cookies. Render receives the connection details needed to serve them over HTTPS. Clicking an email link opens your email app; it does not send a message.

Policy updates

I’ll update this policy when the app or its data practices change. This version takes effect on November 6, 2026. The latest version will be on this page.