Privacy Policy
The Bowler Cool
This policy explains how this application handles information and how to contact us about privacy.
Information we process
The Bowler Cool stores campaign progress, best attempt counts, the current round, play and language settings, a daily-challenge cache and any pending daily result on your device. A random 32-byte installation secret is stored in the device Keychain. When you request a daily challenge or open the public website, our Railway-hosted service receives network requests, including the connection IP address and ordinary HTTP metadata. Daily results contain the UTC challenge date, attempt count and success or failure. The server stores these fields with a SHA-256 hash of the installation secret; it does not store the raw secret. There are no accounts, names, email submissions, advertising identifiers, location collection or third-party analytics SDKs. The privacy contact email is only a published contact address.
How we use information
Local storage supports offline play, continuing rounds, settings, your invitation album and best attempts. The server provides the shared daily configuration and records installation-scoped daily results for daily participation statistics. A pending result may be retried when the application becomes active. The installation secret authorizes result replacement and deletion for that installation. Temporary in-memory connection addresses and installation hashes are used to limit abusive requests. Optional local notifications remind you about the daily throw and are scheduled on the device.
Service providers and sharing
The backend and its persistent database volume run on Railway. Railway processes network and hosting information to operate this infrastructure and may maintain its own operational logs. We have no advertising, analytics, email-delivery or social-sign-in providers in the application. Daily results are not exposed through a public record-reading endpoint. Apple provides iOS Keychain and local notification services on the device. Information may also be disclosed where required by applicable law. We do not sell personal information.
Data retention
Device progress and preferences remain until you remove the application or clear its local data. Keychain items can survive application removal, so uninstalling does not guarantee removal of the installation secret. The challenge cache is accepted only for the current UTC day; pending results from older days are discarded. Server daily-result rows older than the current 90-day window are pruned on the next accepted result submission; pruning is activity-driven rather than a scheduled guarantee. Temporary rate-limit entries are bounded and last only within the running server process. We have not configured an application backup system or a fixed retention period for Railway infrastructure logs. Infrastructure snapshots, if maintained by the hosting provider, follow that provider's lifecycle and are not individually edited by the app.
Deleting your information
In Settings, choose Delete server data while the app still has its installation secret and an internet connection. The server deletes daily-result rows authorized by that secret, and the app removes the secret and pending upload only after a successful server response. Local campaign progress remains. A later daily result can create a new installation secret. Removing the app alone does not send a server deletion request. If the secret is lost, we cannot reliably identify or recover that installation's records; the normal pruning rule still applies. Database deletion removes live records, but erased bytes or hosting snapshots may remain until storage is reused or the provider expires them. Contact EadweareGravenor@icloud.com for privacy questions or deletion assistance; do not send the installation secret by email.
Permissions and your choices
Notifications are optional and requested only when you select the reminder action in Settings. You can turn off the reminder in the app or withdraw notification permission in iOS Settings. Notification denial does not affect campaign or daily play. The application does not request location, contacts, photos, camera, microphone or tracking access. Internet communication for the daily feature uses the normal device network connection. The offline campaign works without notification permission or an internet connection.
Your privacy rights
Depending on your jurisdiction, you may have rights to access, correct, delete, restrict or object to processing and to contact your local data-protection authority. Write to EadweareGravenor@icloud.com to ask about these rights or this policy. We may need enough non-secret context to understand a request, and our ability to associate a record with you is limited because we use installation hashes rather than accounts. The in-app deletion action is the direct way to authorize deletion of your installation's server records. We do not offer account recovery or cross-device restoration.
Security
The application connects to the deployed API over HTTPS. A separate cryptographically random installation secret is kept in Keychain with device-only accessibility and sent as a bearer authorization value only for daily-result and deletion requests. The server stores its hash, validates request fields, limits request size and request rates, and does not log authorization values or result payloads in application access logs. There is no shared secret embedded in the app and no public endpoint to list installation results. These measures reduce risk but cannot guarantee absolute security of a device, network or hosting environment.
Children’s privacy
The game is intended for a general audience aged 12 and above and is not specifically directed at young children. It has no accounts, chat, advertising or purchases, and does not ask players for personal details. A parent or guardian who is concerned about a child's use can disable notifications, remove local app data, use the installation's in-app server deletion action or contact EadweareGravenor@icloud.com. We do not intentionally solicit personal details from children.
Changes to this policy
This policy may be updated when the application's data practices or hosting arrangements change. The current policy is published at this public privacy page, accessible from the website and the app's Settings. The effective date above identifies the current version. Material changes will be described in the updated policy and, where appropriate, within the application.