Privacy Policy
HlNGE: Dating
This policy explains how this application handles information and how to contact us about privacy.
Information we process
HlNGE: Dating is a private profile-writing editor for adults. Draft titles, names, age, city, occupation, additional details, interests, biographies, prompt answers, selected photos, private photo notes, crop settings and modification dates are stored in the app’s local documents. Language, hint preferences and the active draft identifier are stored in local preferences. The app does not require an account. Its example profiles and lifestyle images are fictional editorial content bundled offline. If you choose manual server backup, the app creates a random installation identifier and secret and a 256-bit encryption key stored in this device’s Keychain. It uploads only an AES-GCM encrypted copy of your drafts, including photos and notes. The server stores the installation identifier, a hash of the secret, the encrypted bytes and last-activity time. It does not receive the encryption key or readable profile contents. Network requests necessarily expose connection information to Railway hosting. The server uses network addresses temporarily in memory for rate limiting. Copy actions place only the selected profile text in the system clipboard; other apps may read it when you paste.
How we use information
Local data supports creating, editing, autosaving, reopening, duplicating and deleting profiles, arranging and preparing photos, previewing and copying text. Selected photos are copied into the app and may be resized and compressed; your source library image is not altered. Photo notes remain private and are excluded from copied profile text. Optional encrypted backups allow restoration on the same device only while its Keychain still retains both the installation credential and encryption key. The server uses identifiers, secret hashes and timestamps to authorize access, store backups and enforce expiry. Temporary network-address buckets limit abusive requests. Operational event and request identifiers help diagnose service failures. There is no advertising, tracking, matching, analytics or outbound email system.
Service providers and sharing
Optional backup requests and public website requests are handled by Railway, the application’s hosting and PostgreSQL infrastructure provider. Railway may process IP addresses, request metadata and infrastructure logs as part of operating its service; this policy does not assert an unverified provider log retention period. Application logs contain operational event names and generated request identifiers, not profile plaintext, photo contents, bearer secrets or full request URLs. There are no third-party analytics, advertising or social sign-in SDKs in the app. Photos you explicitly save are added to Apple Photos and may be handled by your Apple library and backup settings. Text you paste into another app is handled by that service under its own policy. We do not sell profile data or make installation backups publicly accessible.
Data retention
Local drafts remain until you delete them or remove the app, subject to device and operating-system backup settings. Keychain credentials and the encryption key can survive reinstalling on the same device, but this is not guaranteed and there is no account-based recovery if they are lost. Server installations and their encrypted backups expire after 180 days without a successful authenticated profile operation. Valid reads, including a read that finds no backup, uploads and deletion refresh activity. Expired credentials cannot access the data; expired rows are removed at server startup and by hourly cleanup. Deleting a server backup immediately clears its encrypted bytes from the active database but retains the installation identifier, secret hash and activity timestamp so future backups can work. These retained records also expire after inactivity. The application does not configure or promise a separate retention duration for Railway infrastructure logs or provider snapshots. Deleted bytes may remain in provider-managed backups until those copies expire under provider practices. Temporary rate-limit address buckets expire within at most one hour and are purged regularly.
Deleting your information
You can delete individual local drafts from the Profiles menu after confirmation. This removes the app’s active local copy, including imported photo copies and notes, without deleting the source photos in Apple Photos. Duplicated drafts and photos previously saved to the photo library must be deleted separately. Deleting a local draft does not change a previously uploaded backup; upload the revised collection or use Delete server backup in Settings. That action requires confirmation, authenticates with your installation secret and removes all encrypted backup contents for this installation from the active server database. It leaves local drafts intact. Provider backup copies are not individually edited by the app and may persist until the provider removes them. If your installation secret is lost, the server cannot identify you through an account or recover/decrypt your backup; inactive data expires as described above.
Permissions and your choices
The app uses the system photo picker to import only images you select and does not request unrestricted access to your entire photo library. When you choose Save photo to Photos, it requests add-only photo authorization and creates a new prepared image. You can decline this permission and continue editing and copying text. You may withdraw photo permission in iOS Settings; previously imported copies remain in drafts until you delete them. The app does not request location, contacts, camera, microphone or notification permission. Network backup is a manual optional action and is not needed for the offline library or local editing.
Your privacy rights
You can inspect and edit local drafts, copy their text, save prepared photos, replace your encrypted backup, and delete local drafts or your server backup using the app. For privacy questions or requests, contact eud1991.lascelles@icloud.com. This address is a public privacy contact, not an in-app messaging or email-delivery feature. Depending on your jurisdiction, you may have rights to access, correct, erase or restrict personal information and to contact a relevant data-protection authority. We may need enough information to locate the relevant installation and assess a request. Do not send your secret, encryption key or private photos by email. We cannot decrypt backup contents or restore a lost device key.
Security
The app encrypts backups on the device using AES-256-GCM with a per-installation key. The key and installation credential are stored in Keychain with a device-only accessibility setting; no shared application credential is used. HTTPS protects deployed network transport. The backend verifies a hashed installation secret for each private operation, uses parameterized database queries, limits payload size to 5 MiB of encrypted bytes, bounds requests and database connections, and keeps private backup responses uncached. Local draft files use iOS file protection and atomic replacement. These measures reduce risk but do not guarantee absolute security, protection against an unlocked compromised device, clipboard disclosure or provider failures. Keep your device secure and review what you share with other services.
Children’s privacy
This editor is intended for adults aged 18 and over and is not designed for children. It does not provide a dating network or verify anyone’s identity. Do not include children’s personal information or identifiable photographs in your profiles. If you believe information about a child has been processed, contact the privacy address so the matter can be assessed, and use the available local and server deletion controls where possible.
Changes to this policy
This policy describes the current app and backend practices. We will update this page and its effective date when those practices materially change. Review the policy through Settings or the public /privacy page before choosing optional backup or sharing content. Any future features that require different processing must be reflected in the policy before release.