Privacy Policy
Super Living Spaces
This policy explains how this application handles information and how to contact us about privacy.
Information we process
Super Living Spaces stores decorating progress, placed furniture, equipment connections, mission completion dates, room finishes, camera position, language, sound and hint preferences in a file on your device. The game works offline. If you enable optional cloud backup, the app creates an installation-specific random access secret and an AES-GCM encryption key in the device Keychain. It uploads an encrypted progress snapshot to our backend. The server stores a hash of the installation secret, its creation time, encrypted snapshots, version identifiers, schema version, client revision, timestamps and retry-protection digests. The encryption key and plaintext progress are not sent. Requests to the API and public website necessarily expose network information such as IP addresses, request time and HTTP metadata to the hosting infrastructure. We do not request an account, name, email address, contacts, location, photos or payment details. Device diagnostics may record backup failure codes and the public API address; the app does not upload these device logs.
How we use information
Local data lets you continue the game, preserve your rooms and use your chosen settings. Optional server data is used only to authorize access to this installation’s encrypted backups, restore saved progress and keep the latest three snapshot versions. Revision identifiers and digests prevent duplicate retries from overwriting a newer version. A bounded in-memory registration counter uses connection-peer addresses to limit abuse; it resets when the service restarts. Technical error logs contain request identifiers and generic failure categories, not backup payloads or access secrets. We do not use advertising, analytics, tracking or outbound email systems.
Service providers and sharing
The backup API and this public policy are hosted on Railway. Railway processes requests and provides hosting, network routing and persistent storage, and may process infrastructure and access logs. The server application uses Python and SQLite with no third-party runtime packages. The iOS app uses Apple system frameworks, including Keychain, CryptoKit and URLSession. There are no advertising or analytics SDKs and no other external application services. We do not sell progress or disclose it to advertisers. Infrastructure providers or the operator may need to process technical records to operate and secure the service or respond to applicable legal requirements.
Data retention
Local progress remains until you reset the local game or remove the app, subject to your device’s operating-system backup behavior. Keychain access material may survive an app reinstall on the same device; survival is not guaranteed. The service retains the latest three encrypted snapshot payloads for an installation until replaced or deleted. Older version metadata and retry-protection digests remain until you delete cloud data. No automatic time-based expiry is configured. We do not assert a fixed retention period for Railway infrastructure logs or provider-level recovery copies. This deployment uses a persistent volume; the application does not configure scheduled volume backups. Storage providers may retain residual or recovery copies under their own procedures, which are not immediately controlled by an in-app deletion.
Deleting your information
In Settings, Delete cloud data requires confirmation, deletes all live server snapshots, version metadata, retry receipts and the installation record including its secret hash, revokes that server credential and turns cloud backup off. The app removes its saved server credential after success. Local game progress remains. Turning backup off alone stops future uploads and does not delete existing server data. Reset local game separately erases local progress and settings and disables backup; it does not delete cloud copies. Remove cloud data first if you want both deleted. Network failure is reported and deletion must be retried. Deletion from live storage does not guarantee immediate erasure from infrastructure logs or provider-level recovery media. Without the installation secret the operator cannot identify the corresponding anonymous backup from an email address.
Permissions and your choices
The game requests no location, camera, microphone, photo-library, contacts, tracking or notification permission. Optional backup uses internet access without an iOS permission prompt. You can disable cloud backup in Settings and continue playing offline. Sound and music can be turned down to zero in the app; the app respects the system’s ambient-audio behavior. You can control operating-system device backups through your device settings. Removing or losing the Keychain secret or encryption key makes the corresponding encrypted copy unrecoverable; no cross-device sign-in or recovery service is offered.
Your privacy rights
You can inspect and change your local rooms and settings, choose whether to upload backups, restore an available version and delete cloud data from Settings. Depending on your location, you may have rights to request access, correction, deletion, restriction, objection or a complaint to your local privacy authority. Contact FergusCavell404@icloud.com with privacy questions or requests. This is a public privacy contact, not an in-app email delivery or account system. Do not send your installation secret or encryption key by email. Because no account or email-to-installation directory exists, a request may require information that lets us identify the relevant data without exposing secrets. We cannot decrypt a backup or recover a lost key.
Security
The app encrypts snapshots on the device with AES-GCM and sends production requests over HTTPS. A unique random installation secret authorizes each installation; the server stores only its SHA-256 hash and scopes backup reads, writes, version lookup and deletion to that record. Secrets and the encryption key are stored in device-only Keychain entries. Local progress uses atomic file writes with iOS file protection. The backend validates requests, bounds snapshot size and concurrent requests, applies registration throttling and uses transactional SQLite storage on a Railway persistent volume. No protection can guarantee absolute security. Anyone with the installation secret may request that installation’s encrypted copies or delete them; the separate encryption key is also needed to read their content.
Children’s privacy
The game is designed for a general teen and adult audience, with an intended audience of ages 14–35. It is not directed to children under 13, and we do not intentionally solicit identifying information from children. No account or age profile is collected. If you believe a child has provided personal information through a privacy inquiry, contact FergusCavell404@icloud.com so the concern can be addressed.
Changes to this policy
We may update this policy when game features, data processing or infrastructure changes. The current English policy and its effective date are published at this /privacy address and linked from app Settings. Material processing changes will be reflected in the policy and, where appropriate, in a future app update. Please review the current policy before enabling optional cloud backup.