Privacy Policy

TheBowlers Together

Effective date: 2026-11-12

This policy explains how this application handles information and how to contact us about privacy.

Information we process

TheBowlers Together stores a two-player journal on your iPhone: pair and player names, levels and optional photos, session dates and club names, lanes, notes and photos, game scores and frame rolls, reviews, partner tips and replies, goals and next-game plans. It also stores reminder and date preferences. There are no accounts. Demo records are explicitly labelled and kept separate from your journal. If you choose encrypted backup, the app sends an encrypted copy of the journal to our server with a random installation secret. The server stores the encrypted snapshot, a hash of the installation secret and its update time. The encryption key stays in the iPhone Keychain. Requests to the service and public website also expose network information such as IP address, request timing and standard HTTP metadata to our hosting infrastructure.

How we use information

Local data provides the journal, bowling scoring, progress calculations, goals, partner observations, next-game planning and exports. Selected photos illustrate profiles and sessions. Optional notifications remind you about your planned session, review and next plan. Encrypted server storage provides a backup that can only be restored using the original installation secret and encryption key. Hosting processes requests to serve the API, public website and this policy, and to maintain service reliability.

Service providers and sharing

The backend and public website are hosted on Railway, which processes service data and infrastructure request information as our hosting provider. The server cannot read the encrypted journal without the client encryption key. No advertising, analytics, social login, email delivery or other third-party SDK is integrated. When you use the iOS share sheet, the destination you select receives the CSV or session image under its own practices. Apple system services handle the photo picker, Keychain and local notification permissions.

Data retention

The journal stays locally until you delete it or remove the app, subject to iOS device backup settings. The most recent uploaded encrypted snapshot remains on the server until replaced or deleted using the installation secret. Installation keys may remain in Keychain after an app reinstall, but their survival is not guaranteed and they are not transferable through an app account. The application does not set a fixed retention period for Railway infrastructure logs or provider-managed residual copies. SQLite storage may retain deleted bytes in its database or write-ahead log until reclaimed; deletion removes the active retrievable record rather than promising immediate physical erasure from all storage.

Deleting your information

Pair contains separate controls to delete the server backup and delete all local journal data, each with confirmation. Local deletion removes profiles, sessions, games, reviews, goals, tips and plans and cancels pending reminders; it does not delete the server backup or installation keys. To remove both copies, delete the server backup before clearing local data. Previously exported files or files shared with other apps must be deleted from those destinations separately. Removing the app does not itself issue a server deletion request. If the installation secret is lost, we cannot identify or restore that encrypted backup through a name or email account. Contact swic@rutaramanauskaite.sbs for privacy questions or deletion inquiries; do not send your secret or encryption key. No automatic server backup schedule or provider backup retention promise is made.

Permissions and your choices

Photos are selected only through the iOS system photo picker, which lets you choose specific images without granting access to your entire library. You can remove selected images by editing the profile or session. Local notification permission is requested only when you enable reminders. Disable reminders in Pair or revoke permission in iPhone Settings; the journal continues to work. No location, contacts, camera, microphone or tracking permission is requested.

Your privacy rights

Depending on your location, you may have rights to access, correct, export, delete or restrict processing of personal data. You can edit the local journal, export scores as CSV, share session images and delete local or server data in Pair. For requests or questions, contact swic@rutaramanauskaite.sbs. Because no account or readable server journal exists, verification and the ability to locate server records are limited; we will explain what is possible without asking you to disclose private installation keys.

Security

The app uses iOS file protection and atomic writes for its local journal, Keychain for a random installation secret and separate AES-256-GCM encryption key, and HTTPS for server requests. The server authorizes each backup by its installation bearer secret and indexes it by a SHA-256 hash. It stores only encrypted journal content and validates request size and format. Application logs do not intentionally include secrets or snapshot payloads. No system can guarantee absolute security. Anyone with access to your unlocked device or exported files may see journal information.

Children’s privacy

The app is a general-purpose sporting journal for friends and is not specifically directed to children under 13. It does not include child accounts, advertising or social communication. Avoid entering unnecessary information about another person and obtain appropriate permission before adding their name or photo. Contact swic@rutaramanauskaite.sbs if you believe child information requires removal.

Changes to this policy

We may update this policy when app features, processing or hosting arrangements change. The revised policy will be published on this page with an updated effective date. Review this page before using new optional data features. Material changes will be described in the app or accompanying release information where appropriate.