Privacy Policy
Tango Town Life
This policy explains how this application handles information and how to contact us about privacy.
Information we process
Tango Town Life stores game position, collected items, acquaintances, quest and creative-activity progress, courtyard preparations and preferences locally on your iPhone. A random installation secret is created automatically and stored in the iOS Keychain when you use a server feature. There are no user accounts, passwords, profiles requiring an email address, ads or third-party analytics SDKs. If you enable backup or choose Back up now, the app sends a snapshot of this game progress and its revision to our server. The server stores an encrypted snapshot, update time and a hash of the installation secret. If you enable aggregate completion counts, the app sends only an allowlisted preparation-completed or finale-completed event (case, instrument, poster, dance, magic or courtyard); the database stores daily totals without an installation identifier in the analytics rows. Public content-version checks also send network requests. Requests expose ordinary connection information such as IP address, request time and technical HTTP metadata to the hosting infrastructure. We do not collect location, contacts, photos, microphone recordings or payment details.
How we use information
Local data lets you continue your story, remember items, settings and creative work, and play offline. Optional server snapshots provide a backup accessible only with the same installation secret. Daily aggregate event counts by preparation stage help us understand how often each part of the game is completed. They are event totals, not unique-player profiles or retention measurements. Public content endpoints let the app check the text version and retrieve supported content strings. Technical request processing and short-lived rate-limit records help operate and protect the service. Optional local notifications remind you to return to the town; notification content is scheduled on the device and is not an email or messaging service.
Service providers and sharing
The backend and public website are hosted on Railway. Railway processes network and infrastructure information needed to deliver and operate the service, and stores the backend database on its persistent volume. The application does not include advertising, social sign-in, external analytics or email-delivery providers. We do not sell game data. Infrastructure providers may maintain their own operational and security logs. We have not configured an application log of progress payloads, authorization headers or installation secrets. We may disclose information when legally required; no additional routine recipients are integrated into the app.
Data retention
Local progress and settings remain until you start a new local story, remove the app data or remove the app, subject to iOS device-backup behavior. Starting a new story replaces local game progress but does not itself delete an existing server snapshot. Keychain items can survive app removal under iOS behavior; we do not promise that reinstalling deletes or restores the installation secret. A server snapshot remains until replaced by a newer backup or deleted through Delete server backup. There is no automatic expiry configured. Aggregate daily completion counts are retained without a configured expiry. Short-lived rate-limit buckets are held only in server memory and reset as windows expire or the process restarts. We do not assert a fixed retention period for Railway infrastructure logs or platform backups.
Deleting your information
In Settings, Delete server backup removes the snapshot associated with this installation secret and disables automatic backup. It does not erase local progress or aggregate counts that have no installation identifier. A later explicit backup can create a new snapshot. Starting again replaces local progress. Removing local app data is managed through iOS; Keychain and device backups may follow separate platform behavior. The service does not offer account recovery or cross-device sign-in, and cannot locate a backup for you without its secret. Deletion removes the snapshot from the active database; database journal pages, infrastructure snapshots or device backups may retain residual copies under their normal storage lifecycle. No separate application backup schedule or guaranteed physical-erasure period is configured.
Permissions and your choices
Notifications are optional and requested only when you turn on the reminder in Settings. You can turn the reminder off in the app, which removes pending app reminders, or withdraw notification permission in iPhone Settings. Denying permission does not prevent play. No camera, photo library, location, microphone or contacts permission is requested. Backup and aggregate event sharing are optional switches and can be disabled at any time; disabling backup alone does not delete an existing server copy. The main game remains available without a network connection.
Your privacy rights
Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing, and to complain to your local data-protection authority. You can inspect and continue local progress, restore the current installation backup, delete the server snapshot and turn off optional processing from Settings. For privacy questions or requests, contact cal.underwood94@icloud.com. This address is a public privacy contact, not an account or an in-app email-delivery service. Do not send your installation secret in ordinary email. We may need enough information to understand a request, but cannot recover a lost secret or identify an anonymous aggregate event as yours.
Security
Public API traffic uses HTTPS. Private progress endpoints require a high-entropy installation-scoped Bearer secret; the server derives an identity hash rather than storing the raw secret. Snapshots are encrypted at rest with AES-256-GCM using a server environment key. This is server-side encryption, not end-to-end encryption: the running server decrypts a snapshot to return it to the authorized app. Secrets are kept in the device Keychain and server configuration rather than shared app credentials. Payload limits, revision checks and request rate limits reduce misuse. No method of storage or transmission is guaranteed completely secure. Losing the installation secret or the server encryption key can make a backup inaccessible.
Children’s privacy
The game is intended for players aged 12 and above and does not require a name, account or contact details. It is not designed to collect personal information from younger children. Optional backup and aggregate counts can be left disabled. If you believe a child has provided personal information to this service, contact cal.underwood94@icloud.com so the situation can be reviewed using the information available.
Changes to this policy
We may update this policy when the game or its processing changes. The current version and effective date appear on this public page. Material changes will be reflected here and, where appropriate, in the app. The current policy is accessible through Settings without signing in.