Privacy Policy
Honey FamBee
This policy explains how this application handles information and how to contact us about privacy.
Information we process
Honey FamBee stores your draft, saved honey pairings, ingredient positions, tasting sets, serving notes, readiness marks, ratings, favorites, impressions, custom food names and optional selected photos on your iPhone. Workshop preferences are stored locally, including a language preference in system preferences. The built-in food catalog and illustrations are bundled with the app. When automatic backup is enabled, changes are encrypted on your iPhone and the encrypted collection, including custom photos and preferences, is sent to our backend. A random installation identifier, a hash of the installation access secret, creation time, encrypted backup and backup update time are stored in PostgreSQL. The access secret and encryption key are stored in your device Keychain. There are no accounts, passwords, advertising identifiers, location features or analytics SDKs. Requests to the API and public website also expose technical connection information such as IP address, request path, time and HTTP headers to Cloudflare and the Railway hosting infrastructure. The application server temporarily uses an IP-based request counter to limit abuse and logs generic failure events with random request identifiers without intentionally logging collection contents or credentials.
How we use information
Local data lets you arrange ingredients, save and reopen work, plan serving order, record your own tasting impressions and prepare shopping lists and export cards. The encrypted server copy is used only for backup and restoration by the installation holding its access secret and encryption key. Connection metadata and temporary counters support delivery, readiness checks, error diagnosis and abuse prevention. The app remains usable offline. It does not create ratings on your behalf or use your content for advertising.
Service providers and sharing
The backend and PostgreSQL database run on Railway, which processes stored ciphertext and technical connection information as the hosting provider. Cloudflare provides the public HTTPS proxy for api.honey-fambee.sbs and honey-fambee.sbs. It terminates HTTPS and forwards requests to the same Railway service, so it processes request paths, IP addresses, HTTP headers and encrypted backup payloads in transit. The collection remains encrypted by the iOS client; Cloudflare does not receive the collection decryption key. Cloudflare and Railway infrastructure may generate operational, access or security logs. We have not established fixed provider log-retention periods and do not promise them. No advertising, analytics, email delivery or social sign-in providers are integrated. When you export a collection file or share a set card, iOS delivers it to the location or application you choose; that recipient handles the exported data under its own practices. Opening the privacy policy or external honey information links sends a normal web request to the selected site.
Data retention
Local work stays on the device until you delete or replace it, subject to iOS storage and device-backup settings. The app does not set an automatic expiry for saved work. The server retains one latest encrypted snapshot per installation, replacing it on subsequent successful backups. Installation metadata and the latest snapshot remain until you use the server deletion control. The app does not configure a separate application-level archive of old snapshots. Cloudflare, hosting, database or device infrastructure may retain operational logs or backup copies according to its own configuration; immediate erasure of those copies is not promised. Exported files and cards remain wherever you saved or shared them until deleted there.
Deleting your information
In Workshop, Delete server backup removes both the installation record and its encrypted snapshot from the active database, removes this installation's local backup keys and switches automatic backup off after success. Delete local work removes drafts, pairings, sets, custom food names and app-held photos from local storage and switches automatic backup off; it does not delete the server copy. These are separate controls so you can choose what to keep. Delete the server copy first if you want both copies removed. Exported files, shared cards, saved Photos images and any system or provider backup copies require separate handling. Uninstalling the app is not a server-deletion request. We cannot restore or locate a private collection without its installation keys; keep a private exported collection file if you want to transfer to another device.
Permissions and your choices
The system photo picker lets you choose an optional image for a custom food without granting broad photo-library access. The selected image is resized and stored with your collection. Permission to add images to Photos is requested only when you choose to save an exported set card. You can refuse that permission and continue using the app or share the card through the system share sheet. You can revoke Photos permission in iOS Settings; revocation does not remove images already saved or copied into your collection. The app does not request camera, microphone, contacts, notifications or location access.
Your privacy rights
You can inspect and edit your records in the app, export your collection, switch automatic backup off and delete local or server data using Workshop controls. For privacy questions or requests, contact nerissa.yardley@icloud.com. This address is a public privacy contact only; the app has no contact form or outbound email system. Depending on your location, applicable law may give you rights of access, correction, deletion, restriction, objection or complaint to a data-protection authority. Requests must be assessed against the limited information we actually hold; we cannot identify encrypted content or recover lost installation keys from an email address.
Security
Backup requests use HTTPS to Cloudflare, which terminates that connection and proxies requests over HTTPS to the pinned Railway service origin. Before upload the iOS client encrypts the collection with AES-256-GCM using a randomly generated key held in the device Keychain; the server does not receive the decryption key. Each installation receives a separate random access secret. The server stores only its SHA-256 hash and authorizes protected requests using that secret together with the installation identifier. Database queries are parameterized and request sizes and rates are bounded. Local collection writes use iOS file protection and atomic replacement. Collection transfer files are intentionally unencrypted and contain your notes and selected photos but no server access secrets or encryption keys; keep them private. No system can guarantee absolute security.
Children’s privacy
Honey FamBee is designed for adult honey enthusiasts and hosts. It is not directed at children and does not ask for a child's name, age or contact details. If you believe a child has supplied personal information through content in a collection, use the deletion controls or contact nerissa.yardley@icloud.com with a privacy concern. The app does not provide a public profile, messaging or shared rating service.
Changes to this policy
We may update this policy when the app's processing or hosting changes. The current policy is available at this public privacy page and through the Privacy Policy link in Workshop. The effective date identifies the version currently in use. Any material processing change will be described in the updated policy; this policy does not promise notifications through an account or email system.