Privacy Policy
KIO Prime Timing
This policy explains how this application handles information and how to contact us about privacy.
Information we process
KIO Prime Timing stores your custom recipe names, ingredients, instructions, durations and selected photos, selected dishes and portions, saved menus, shopping items and checkmarks, favourites, cooking sessions and completion history, equipment and preferences on your iPhone. Language preference is stored in app preferences. The built-in recipe catalogue and artwork are included in the app. Cooking does not require a server connection. If you enable optional backup, the app sends custom recipes and saved menus, including any recipe photos contained in them, to our backend. The server also stores record identifiers and update times, a random installation identifier and creation time, and a hash of an automatically issued installation secret. The secret itself is stored in this iPhone's Keychain. Requests to the API, public home page and this policy also reach Railway infrastructure, which receives network information such as IP address, requested URL, time and client information. We do not request an email address, account, password, location, contacts or advertising identifier.
How we use information
Local data supports recipe editing, portion calculations, shopping lists, equipment-aware schedules, timer restoration, favourites, repeatable menus and cooking history. Optional server storage provides a backup accessible only with this installation's secret. The secret hash authorizes access to that installation's records. Temporary IP and installation counters limit abusive requests. Generic server lifecycle and error events, request identifiers and status codes help operate and diagnose the service. We do not use app data for advertising, marketing or analytics.
Service providers and sharing
Railway hosts the HTTP application and PostgreSQL database and processes requests and stored backup data as infrastructure provider. Hosting infrastructure may retain operational request logs. The application uses Apple's system photo picker, Keychain and local notification services; selected photos are copied into app storage, and timer alerts are scheduled on the device rather than sent through a remote push service. Device backups may be handled by Apple according to your device settings. There are no advertising, analytics, email delivery, social sign-in or other third-party service SDKs in the app. We do not sell personal information or provide a public recipe-sharing service. Information may also be disclosed where required by applicable law.
Data retention
Local recipes, menus, preferences, shopping information and history remain until you remove them or erase app data. Server backup records have no automatic expiry and remain until individually deleted through synchronization or removed with Delete all my data. Disabling backup stops synchronization but does not erase existing server copies. Unsent changes remain in the local SQLite queue until successfully synchronized or erased. Rate-limit counters are bounded transient process memory and reset when the server process restarts. The app does not set a retention period for Railway infrastructure logs or provider backups; these may persist under the provider's configuration and lifecycle. We do not promise immediate erasure from backups or a specific log retention duration. The local backup database also keeps acknowledged payloads to avoid uploading unchanged content; these are removed when their deletion is acknowledged or all app data is erased.
Deleting your information
You can delete custom recipes and saved menus in the app. If backup is enabled, deletions are queued and applied to this installation's live server records when a connection is available. Deletions made while backup is disabled are retained for the next enabled synchronization if this installation has a server secret. Settings includes Delete all my data, which removes this installation's live server data and revokes its secret, then clears local recipes, menus, shopping data, sessions, history, preferences and pending changes. If a server secret exists, a successful server response is required before local erasure; offline failure preserves your local data so you can retry. Removing the app alone does not send a server deletion request, and Keychain entries may remain. Loss of the installation secret prevents access and recovery; there is no account-based recovery. Erased live database rows may remain temporarily in infrastructure backups until those backups expire under the provider's lifecycle. Recipes and photos may also remain in snapshots inside saved menus or cooking history until those records are removed or all data is erased.
Permissions and your choices
Photo selection uses the system photo picker and grants access only to the items you select, rather than your entire library. Remove an imported photo by editing its recipe. Local notification permission is requested only when you enable timer notifications. You can turn alerts off in the app or withdraw permission in iPhone Settings; cooking and timer deadlines still work, but background alerts may not be delivered. Sound can be disabled separately. No location, microphone, camera or contacts permission is used. Optional backup can be disabled at any time; this stops transfers without deleting copies already stored on the server.
Your privacy rights
You can review and edit your recipes, saved menus and local records in the app and use its deletion controls without creating an account. For privacy questions or applicable rights requests, contact lorcanbrackenbury@icloud.com. Depending on your jurisdiction, rights may include access, correction, deletion, restriction, objection or a complaint to your local data protection authority. We will consider requests under applicable law and may need information sufficient to establish authority over the relevant data. Do not email your installation secret. We cannot identify or restore an installation's private records from an email address because no email account is associated with them.
Security
The app connects to the public API over HTTPS. Every backup installation receives its own cryptographically random secret, kept in Keychain with device-only accessibility after first unlock; the backend stores only its SHA-256 hash. Every protected database operation is scoped by the authorized installation. PostgreSQL is accessed using server-side credentials, not credentials embedded in the app. Local data files use iOS file protection after first unlock, and saved documents use atomic writes. Requests, storage and database connections are bounded. Application logs do not include recipe payloads or secrets. No security system is perfect; protect access to your iPhone and do not disclose its installation secret.
Children’s privacy
KIO Prime Timing is intended for home cooks and is not directed at children. We do not knowingly request children's personal information or provide child profiles. Cooking involves heat, sharp tools and food safety considerations; children should use cooking activities only with appropriate adult supervision. If you believe a child has provided personal information through optional backup, contact lorcanbrackenbury@icloud.com so we can consider the appropriate action.
Changes to this policy
We may update this policy when the app's processing or hosting practices change. The current policy is available from Settings and at this public privacy URL, with its effective date. We will update that date when publishing a revised policy and provide additional notice where required by applicable law. Questions about changes can be sent to lorcanbrackenbury@icloud.com.