# Battleship Privacy Policy

Battleship keeps offline matches on your device. Configured builds also use online accounts and match services, with optional notifications and integrations for advertising, purchases, and crash reporting.

- App: Battleship (https://beenmoss.com/projects/battleship.md)
- Last updated: October 26, 2026
- Web page: https://beenmoss.com/projects/battleship/privacy

> Pre-release draft describing the current implementation. Online availability and service configuration vary by test build; final release disclosures remain under review.

## Offline play and local storage

Battleship is presented by bee n moss. Computer and same-phone matches do not require an account. The app saves their boards, ships, shots, turns, and recovery copies locally, along with settings, tutorial state, and cached purchase status.

Offline gameplay does not mean every enabled service is offline: advertising or purchase checks can contact their providers separately when a connection is available.

## Accounts and online matches

Configured online builds use Firebase Authentication with supported Google or Apple sign-in. The service processes an account identifier, a generated callsign and avatar, room and matchmaking state, fleet placements, shots, results, and match history. Provider availability depends on the test build; Apple release setup is still pending.

The game server validates online moves and uses database and live-update services to deliver the match. Opponents see your callsign, avatar, and permitted game information, rather than your sign-in credentials. Both fleets are revealed after a win, surrender, or turn timeout; a no-result match keeps fleets hidden.

## Notifications and diagnostics

When configured and permitted, Firebase Cloud Messaging uses a device token and notification preferences for match alerts. You can change notification preferences in Account and permissions in device settings.

Online builds include Firebase App Check for app verification and Crashlytics for release-build error reports. These services can process technical device, app, and diagnostic information. Their final production configuration and release checks are still in progress.

## Advertising and purchases

Advertising-enabled builds integrate Google AdMob and its consent flow. The SDK can process device and network information, identifiers, ad interactions, and consent choices. Default development ad units are test units; test advertising is not a promise of zero network traffic. Where offered, Settings provides advertising privacy options.

A one-time Remove Ads purchase and restore flow are implemented, but store products and billing acceptance remain in preparation. When enabled, Apple or Google handles payment and the game service verifies transaction identifiers, purchase tokens or signed transaction information, and entitlement status. The game does not receive payment-card details.

## Deletion and support

Local matches remain until removed from the device. Online account deletion removes the profile, device registrations, and preferences, and removes your identity from retained match records. Purchase verification records can remain to support restoration; deleting a game account does not delete the store’s transaction history.

Support receives the information you choose to email. Use the account-deletion page for the available steps or contact support@beenmoss.com with questions about your build.

[Ask about Battleship privacy](mailto:support@beenmoss.com?subject=Battleship%20privacy)