Privacy Policy

Ruin but Important

Effective date: 2026-10-20

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

Information we process

Ruin but Important stores campaign progress, hall and mechanism states, Keeper position, discoveries, unlocked passages and interface preferences locally on your iPhone. Optional server backup sends a campaign JSON document and an installation-specific authorization secret over HTTPS. The server stores the progress document, a SHA-256 hash identifying the secret, and its last-update timestamp. The secret is generated randomly and kept in this device’s Keychain; the server does not store its original value. There are no accounts, names, email registration, location access, advertising identifiers or analytics SDKs. Requests to the backup service and public website also reach Railway infrastructure, which receives network information such as IP address, request path, time and HTTP status. The public website uses no cookies or tracking scripts.

How we use information

Local data makes the entire 18-hall campaign playable offline and restores your latest state when you return. If you enable backup, the server holds a replacement copy for this installation and authorizes reading, replacing and deleting only that installation’s document. Network metadata is processed to deliver and protect the service. Temporary in-memory rate counters limit abuse. The public contact email is used only if you choose to contact the owner directly outside the app; the app has no contact form or email delivery service.

Service providers and sharing

The backend and public privacy page run on Railway, which processes requests and hosts the persistent SQLite database volume. Railway may process infrastructure and operational logs. App code logs only service startup and unexpected error codes with random request identifiers, not progress bodies or authorization secrets. No advertising, analytics, social sign-in or messaging providers are integrated, and progress is not sold or made public. The operator can access hosted application data for operation and responding to requests. Information may be disclosed when legally required.

Data retention

Local progress remains until you remove the app’s data through iOS or replace it using an explicit restore. An installation secret can remain in Keychain after app removal; persistence is controlled by iOS and recovery after losing the secret is not promised. Server progress remains until you request deletion; a later successful backup replaces the previous active document. There is no scheduled expiry. Rate-limit entries are temporary in-memory counters and are reset after their minute window when reused, pruned as capacity requires, or lost on server restart. No application-managed secondary backup schedule is configured. Railway infrastructure logs and any platform-managed recovery copies are governed by Railway’s practices; this application does not promise a retention duration for them.

Deleting your information

In Settings, Delete server backup removes the installation’s active database row and turns off further uploads. This does not erase your local campaign. If offline, the request remains pending and is retried when connectivity returns or the app becomes active; the UI confirms deletion only after the server succeeds. Re-enabling backup can create a new copy. SQLite secure deletion is enabled for deleted active rows, but this does not guarantee immediate erasure from infrastructure recovery copies or historical logs. Any such copies are subject to their normal platform lifecycle. Remove the app’s local data through iOS to remove its campaign and preferences. If the installation secret is lost, the operator cannot identify a backup by an email account because no such account exists.

Permissions and your choices

The app requests no camera, microphone, contacts, photos, notifications or location permission. Network access is used for optional backup and for opening this public policy in your browser. Turn off server backup in Settings to stop new progress uploads; use Delete server backup to remove an existing copy. Turning backup off does not delete data already saved. Device-level controls for network access and accessibility remain available in iOS Settings.

Your privacy rights

You may review your campaign in the app, restore an available server copy using this installation’s Keychain secret, disable backup or delete its server document. For privacy questions or requests concerning access, correction, deletion or other rights available under your local law, contact dorinda.allbones@icloud.com. Do not send the installation secret by email. The owner may need non-secret information to understand a request, and cannot locate a backup from a name or email address alone. You may also contact the relevant privacy authority where applicable.

Security

Client-server traffic uses HTTPS. Each installation uses an independent cryptographically random 32-byte secret in a device-only Keychain item. The server derives a SHA-256 identity and scopes each progress operation to that identity. There is no shared client credential. Request size, JSON depth, header and rate limits protect the API. Progress uses atomic local file writes with iOS file protection, while server data uses a persistent SQLite volume with transactional writes. These safeguards reduce risk but no network or storage system can be guaranteed absolutely secure. Keep your device protected; losing the secret can make its backup inaccessible.

Children’s privacy

This contemplative adventure is intended for players aged 16 and older, rather than directed at children under 16. The app does not ask for age or create accounts. If you believe information concerning a child was submitted, contact dorinda.allbones@icloud.com so the owner can assess the request. The owner cannot associate a progress document with a particular person without relevant identifying context.

Changes to this policy

This policy describes the processing implemented in this version. If the app or backend practices change, the policy and effective date will be updated on this page. Review it from the Privacy Policy link in Settings. Material changes will be described in the updated policy or app release information; no email notification system is operated.