Privacy Policy
Estra Banquet Relay
This policy explains how this application handles information and how to contact us about privacy.
Information we process
Estra Banquet Relay stores your recipe names and preparation stages, equipment settings, selected menu, serving time, cooking timers, actual stage durations, dinner history and training results locally in an iPhone SwiftData database. Optional synchronization sends recipe templates, recipe deletion timestamps and scenario identifiers, three result scores and update timestamps to our server. An automatically issued random installation secret is stored in the iPhone Keychain; the server stores only its SHA-256 hash and a random installation identifier. We do not request an account, name, email address, password, location, contacts, photos, camera or microphone. Railway receives network requests, including technical connection and request information such as IP addresses, routes, timestamps and response status. Visiting this website also creates a network request. The app contains no advertising or analytics SDK.
How we use information
Local records are used to plan equipment and chef availability, check serving constraints, run parallel cooking timers, compare planned and actual durations and retain your training progress. Optional server processing saves and synchronizes recipe templates and scenario results for the same installation, resolves changes by their update timestamps, and authorizes access to that installation's records. Technical request information supports hosting, reliability and abuse prevention. The server temporarily counts requests by network connection address for rate limiting. No data is used for advertising or email delivery.
Service providers and sharing
The application backend and PostgreSQL database are hosted by Railway, which processes server records and technical infrastructure information to operate the service. Apple provides the operating system, Keychain, device storage and local notification services; cooking notifications are scheduled locally, without our server sending push messages. Your device backup provider may hold local app data if you enable device backups. We do not sell personal data or integrate third-party analytics, advertising, social sign-in, messaging or map providers. Only the installation secret authorizes access to the corresponding private server records. The public home and privacy pages do not require that secret, an account or cookies.
Data retention
Local recipes, settings, dinner history and results remain until you remove them, erase installation data or remove the app's data. Server recipe templates, result records and deletion tombstones remain until the installation data is deleted; there is no automatic expiration period configured. The secret is a device-only Keychain item and may survive removal of the app; it is not transferable through the app. In-memory rate-limiting entries expire after one minute. Application logs contain fixed operational events rather than recipe content or secrets. Railway controls infrastructure logs and any platform backup retention; this application does not establish or promise a retention duration for those copies. Device backups can retain earlier local data under your backup settings.
Deleting your information
Kitchen setup contains a Delete all installation data action. When a secret exists, the app first requests authenticated server deletion of the installation and its recipe and result rows, then removes the Keychain secret and local recipes, menus, history, timers and progress. If the server cannot be reached, the app retains local data and the secret and offers retry rather than claiming deletion succeeded. Recipe deletion removes its live content and retains a deletion timestamp locally and on the server for synchronization until full installation deletion. Disabling sync stops subsequent synchronization but does not erase existing server records. Deletion affects active storage; earlier device or infrastructure backups may persist under their providers' lifecycle and are not immediately rewritten by this action. There is no account recovery or promise to recover records after loss of the secret.
Permissions and your choices
Cooking mode asks permission for local alerts and sounds when you start a stage. Notifications remind you to check the dish; denial does not prevent planning or visible timers. You can change notification permission in iOS Settings at any time. Language is selected through the system's app language settings. No geographic, photo, camera, microphone or contact permission is requested. You can disable optional synchronization in kitchen setup. Withdrawing notification permission or disabling sync does not delete saved records; use the deletion action for that purpose.
Your privacy rights
You can inspect, edit and delete your recipe templates in the app, review dinner history and scenario results, and delete all installation data through kitchen setup. Contact EirwenRooke@icloud.com for privacy questions or requests concerning access, correction, deletion or other rights available under applicable law. This address is a public privacy contact, not a login or a delivery system in the app. The server does not associate installations with email addresses, so a request may require information sufficient to identify the installation without disclosing your secret. We cannot recover installation access when its secret is lost.
Security
The deployed application API uses HTTPS. A separate cryptographically random secret is issued to each installation, held as a device-only Keychain item and represented only by a SHA-256 hash on the server. Every private request is authorized against that hash and database queries are scoped to the installation; no shared client credential provides access to private records. Server input validation, payload and connection limits, bounded database connections and parameterized SQL reduce common failures and misuse. The app uses the iPhone's storage protections. Secrets and recipe payloads are not written to application logs. These controls reduce risk but do not guarantee absolute security.
Children’s privacy
The product is intended for adult home cooks planning dinners. Its training puzzles are kitchen-planning exercises, not a service directed at young children. We do not knowingly solicit personal information from children. Cooking involves heat, sharp tools and food safety; children should use the application only with appropriate adult supervision. If you believe a child's information has been stored through this service, contact EirwenRooke@icloud.com.
Changes to this policy
We may update this policy when application features, server processing or hosting practices change. The public Privacy Policy linked from kitchen setup will show the updated policy and its effective date. Material processing changes will be reflected in the application and this policy. The effective date above identifies the current version.