Privacy Policy
SugarBooks Portfolio
This policy explains how this application handles information and how to contact us about privacy.
Information we process
SugarBooks Portfolio stores the recipes, ingredient quantities and prices, preparation instructions, tags, selected dessert photos, cake and flavor drafts, order titles, dates, statuses and notes, stock and shopping items, cost calculations, selling prices, portfolio work and preferences that you enter. These records are stored in the app's SQLite database on your iPhone. The dedicated customer-name field stays on your device. Cloud storage is optional and off initially. If you enable it, the app sends your other workshop records, including selected photos and notes, to its own backend. Do not put customer details in notes if you do not want those details synchronized. The server issues a random installation secret, which the app stores in the iPhone Keychain; the server stores only a hash of that secret and the installation creation time. There are no user accounts. Requests to the backend, home page or policy also expose ordinary connection information such as IP address, request path and timing to the hosting infrastructure. The app contains no advertising or analytics SDKs and does not collect your location or photo library as a whole.
How we use information
Local records support your recipe book, scaling, cake estimates, pricing, order timelines, inventory, shopping list and portfolio. Optional cloud storage keeps a private server copy and synchronizes changes after connectivity returns. The installation secret authorizes access to your own records without a login. The backend uses temporary in-memory request counters for abuse prevention and error request identifiers for diagnostics. Local notifications remind you of future baking stages only when you enable reminders. Selected portfolio records can be rendered into a PDF on your device and shared through the system share sheet at your direction.
Service providers and sharing
The backend and public pages are hosted by Railway, which processes stored cloud data and network requests as our infrastructure provider. Railway and its underlying infrastructure may process operational connection and service logs. Our application logs startup information and error identifiers or error codes, not installation tokens or record contents. We do not sell personal data or add advertising, analytics, email-delivery or social-network services. Apple system services handle the photo picker, Keychain and local notifications on your device. When you use the share sheet, the app or destination you choose receives the PDF under that destination's own terms. Public home and policy pages require no login and set no application cookies.
Data retention
Local workshop records remain until you delete them or remove the app. The workshop database directory is excluded from device backups by this app; the installation secret uses a device-only Keychain accessibility class. The Keychain may retain a secret after app removal, so uninstalling alone must not be relied on to remove cloud data. Cloud records remain until you delete them. Deleting an individual record removes its cloud content when synchronization succeeds and retains a minimal deletion marker so pending changes cannot silently bring it back. Unsynced changes remain locally pending until they can synchronize. The backend does not create application backups. No fixed retention period is asserted for Railway's infrastructure logs or any infrastructure-level snapshots, whose lifecycle is controlled by the hosting provider; deletion from the active database may not immediately erase those copies.
Deleting your information
Use the record's Delete action to remove a recipe, order, portfolio work or calculation; stock and manual shopping items also have deletion controls. Recipe deletion archives linked cost calculations rather than deleting them. Individual changes made offline reach the server on the next successful sync. Settings contains Delete All My Data, which deletes all rows belonging to this installation from the active backend database, revokes its secret and then clears local workshop records, photos, sync cursors and pending notifications. An internet connection is required if a cloud secret exists; if the request fails, local records are kept so deletion can be retried. Turning cloud storage off stops synchronization but does not erase server copies. There is no account-based recovery or transfer to another device. If the installation secret is lost, we cannot identify or recover that private workspace from an email address. Removing the app does not itself request server deletion. Infrastructure logs or snapshots, if present, are subject to the hosting provider's lifecycle rather than immediate per-record removal.
Permissions and your choices
You choose individual images with the system photo picker when adding or changing a recipe or portfolio photo. The app receives only your selected image and resizes it for storage; no broad photo-library access is requested. You can cancel the picker or remove a selected image from a record. Notifications are requested only when you save an order with Stage Reminders enabled. You may turn reminders off in the order and save it, or withdraw notification permission in iPhone Settings; saved timelines continue to work without notifications. The app requests no camera, microphone, contacts or location permission. Network access is used for optional cloud storage and opening the public privacy page.
Your privacy rights
You can inspect, edit and delete your records in the app, export selected portfolio work to PDF, and stop optional cloud storage. Depending on where you live, you may have rights to request access, correction, deletion or restriction of personal data and to contact your local data-protection authority. Send privacy questions or requests to leo.rivington@icloud.com. This address is a public privacy contact, not an account or an in-app email-delivery feature. Do not send your installation secret by email. Because there are no accounts or identity recovery records, requests concerning an installation may require you to use its in-app controls; an email address alone cannot establish access to its private data.
Security
The client uses HTTPS for the deployed API. A cryptographically random installation secret is stored in Keychain with device-only protection, and the backend checks its hash before every private-data request. Database queries scope records to that installation. The local database uses iOS file protection, and record changes and pending synchronization state are persisted in SQLite. The server stores cloud records on its Railway service volume and limits request sizes and request rates. These measures reduce risk but do not guarantee absolute security. Cloud records are not end-to-end encrypted; the backend and its hosting infrastructure must be able to process them. Keep your device protected and avoid sharing its installation secret.
Children’s privacy
SugarBooks Portfolio is intended for adult bakers and confectionery businesses and is not directed to children. It has no child profiles, social features, advertising or account registration. If you believe a child has provided personal information through this app, contact leo.rivington@icloud.com. Use the app's deletion controls when the relevant installation is available.
Changes to this policy
This policy describes the current app and backend behavior as of the effective date above. If processing changes, the policy and its effective date will be updated at this public Privacy Policy page, which is linked from app Settings. Material changes will be described in the updated policy and, when required, brought to your attention in the app before the changed processing applies.