Privacy Policy
Myn Snuggle Home
This policy explains how this application handles information and how to contact us about privacy.
Information we process
Myn Snuggle Home stores your optional local name, journal text, selected moods and dates, rituals, completion dates, reminder schedules, room names and tasks on your iPhone using SwiftData. Language, cloud preference and pending deletion status are stored in local preferences. An automatic random installation secret, access token and encryption key are stored in the device Keychain when cloud features are used. Cloud sync is optional and off by default. When enabled, the app sends an encrypted snapshot of your home data to our backend. The backend stores the latest encrypted snapshot, its update time, hashed installation and token identifiers, and the installation creation time. The encryption key is not sent to the backend. Requests to the API or this public website pass through Cloudflare and reach Railway infrastructure, which can process IP addresses, request times, URLs, response status and operational metadata. There are no user accounts, advertising identifiers, analytics SDKs, location collection, camera access, photo-library access or contacts access. JSON exports contain your home data in readable form at the location you choose.
How we use information
Local data supports your journal, ritual streaks, room tasks, daily mood history and preferences. Reminder schedules are used only for local notifications on your device. Optional cloud storage maintains one encrypted copy for this installation and allows recovery only while its secret and encryption key remain available. It does not provide account recovery or transfer through sign-in. Installation identifiers authorize requests and keep different installations' snapshots separate. Operational metadata and short-lived in-memory request counters support service delivery, error diagnosis, abuse prevention and readiness checks. We do not use your content for advertising or profiling.
Service providers and sharing
Railway hosts the backend and its persistent database volume and processes network and operational information as an infrastructure provider. Cloudflare provides the custom domains’ edge proxy and HTTPS delivery, and can process request content and network metadata passing through it. Private home content is already encrypted by the app before it reaches this infrastructure; authorization credentials are still used for delivering authenticated requests. The backend receives encrypted content rather than its readable journal, mood, ritual or room contents. Application code logs startup and internal error identifiers without intentionally logging request bodies, authorization tokens or IP addresses. Railway and Cloudflare may generate infrastructure logs separately. No third-party analytics, advertising, messaging or email delivery SDK is included. Apple's operating system handles device storage, Keychain, local notifications and the Files export interface. When you export a JSON file or open the policy in a browser, the storage destination or browser you choose may process it under its own settings. We do not sell personal data.
Data retention
Home data remains on the device until you delete it or remove the app, subject to your device and backup settings. Keychain items can remain after app removal under iOS behavior; retention is controlled by the operating system, and recovery after reinstall is not guaranteed. The server retains only the latest encrypted snapshot until it is replaced or deleted. Minimal installation authorization hashes and creation time remain after snapshot deletion so that the installation can continue to authorize requests; these records contain no readable journal content. Rate-limit counters are held in process memory with one-minute windows and are lost on restart. We do not specify a retention period for Railway or Cloudflare infrastructure logs or provider backups because their actual retention is controlled by the hosting configuration and provider. No separate application backup schedule has been configured. Deleted information may remain temporarily in database free pages, device backups or provider backups until those are overwritten or expire under the relevant system's lifecycle; deletion is not a promise of immediate physical erasure of every backup copy.
Deleting your information
Use Profile's Delete all data action to remove the journal, rituals, rooms, moods and local name and cancel local reminders. If cloud sync has been used, the app records a pending server deletion and removes the encrypted snapshot when a network request succeeds, even if cloud sync is then disabled. Keep the app installed and reopen it online so an offline deletion can finish. Disabling cloud sync alone stops further optional uploads and does not delete the existing server copy. The deletion endpoint retains only minimal authorization records, not the snapshot or its update time. Language preferences and the installation Keychain credentials can remain so that deletion retries and future authorized use work. Previously exported files and copies you made must be deleted from their chosen destinations separately. For privacy questions or requests concerning retained metadata, contact Roderick2Ashcombe@icloud.com. Do not send your secret, token, encryption key or private journal content by email.
Permissions and your choices
Notifications are optional and requested only when you enable a ritual reminder. If you decline, your journal, rituals, rooms and mood tracking still work. Change notification permission at any time in iOS Settings, or turn off an individual reminder in its ritual editor. The app then stops scheduling that reminder. File export uses Apple's document picker to save to a destination you choose; it does not request broad access to your files. There is no location, camera, microphone, photo-library or contacts permission. You can turn off cloud sync in Profile; local features continue to work offline.
Your privacy rights
You can review and edit your records in the app, export a JSON copy to Files, and delete local data and the optional server snapshot from Profile. Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing, request portability, or complain to a relevant data protection authority. Send privacy questions and rights requests to Roderick2Ashcombe@icloud.com. We may need proportionate information to locate a request without exposing another installation's data. There is no account lookup or password reset, and we cannot decrypt your snapshot or promise recovery if the installation secret or encryption key is lost.
Security
The app saves local records through iOS storage and keeps installation credentials in Keychain using a device-only accessibility class. Optional snapshots are encrypted on the device with AES-GCM using a randomly generated 256-bit key before upload. Network requests use HTTPS. The server hashes installation identifiers and bearer tokens and checks authorization on every snapshot read, write and delete. SQLite transactions, validation, payload limits and request limits help protect data integrity and availability. The service has no public endpoint for reading private snapshots without authorization. These measures reduce risk but cannot guarantee absolute security. Protect your device and any readable JSON exports, and never share installation credentials.
Children’s privacy
Myn Snuggle Home is designed for adults interested in home routines and wellbeing, rather than for children. We do not knowingly seek children's personal information. If you believe a child has provided personal information through the app or service, contact Roderick2Ashcombe@icloud.com so the concern can be assessed. Avoid entering another person's private information into your journal without an appropriate reason.
Changes to this policy
We may update this policy when the app, hosting or data practices change. The current policy is available through the app's Privacy Policy link and this public page. Its effective date identifies the current version. Material changes will be described in an updated policy and, when appropriate, in an app update. This policy describes the implemented practices rather than guaranteeing future features or a fixed provider retention schedule.