nutritious.love ♥

Who operates Cherry

Cherry and nutritious.love are operated by Josef Richter (sole proprietor). For privacy requests, contact josef.richter@me.com.

Data we process

• Account data: the iOS app normally uses a random account identifier rather than a visible login. A recovery verifier, device attestation records, and authentication tokens protect that account. Web users may provide an email address for magic-link authentication.
• Nutrition data: food descriptions, nutrition values, meal times, saved foods, evaluations, and usage-limit records.
• Submitted media: meal photos, barcodes, nutrition labels, and temporary voice recordings that you explicitly submit.
• Subscription data: entitlement status and Apple/RevenueCat transaction identifiers. Cherry never receives your full payment-card details.
• Technical data: limited security, reliability, and error information such as IP address, device attestation state, and request diagnostics.

Optional automatic photo scanning

Automatic scanning is off by default and starts only after you opt in. When enabled, Cherry may examine new Photos-library images locally, including during background processing. A local privacy and eligibility check must identify a likely food image, barcode, or nutrition label before it is uploaded. Images that do not qualify or remain uncertain stay on your device. You can disable automatic scanning at any time in Settings. Photos you select through the camera, photo picker, or Share extension are intentional submissions and may be sent to the server after the local privacy check.

AI and service providers

Submitted food text, eligible images, labels, and temporary voice recordings are processed by OpenAI to provide transcription and nutrition analysis. Voice recordings are not retained after transcription. We also use Fly.io for hosting and database storage, RevenueCat and Apple for in-app subscriptions, Stripe for web payments, Resend for transactional email, Sentry for reliability monitoring, and consent-based PostHog analytics on the website. These providers may process data outside the European Economic Area under their applicable safeguards.

iCloud and device storage

The iOS app can store its random recovery secret in synchronizable iCloud Keychain and its anonymous identifier in Apple key-value storage so the account can be recovered on another device. Device-local credentials are shared with the Cherry Share extension through an Apple Keychain access group. Apple controls iCloud processing under your Apple account settings.

Retention and deletion

• Account and nutrition data remain on the server while your account exists. Uninstalling Cherry does not delete server data.
• Local image caches are bounded and may be removed by the system or when you delete your account. Server media is retained only as needed to provide meal history and the service.
• You can delete the account in Cherry under Settings → Privacy & account. The deletion removes meals, images, evaluations, saved foods, usage records, credentials, device attestations, and subscription linkage in one operation.
• After deletion, we retain only a one-way hash of the former anonymous account identifier and the deletion time to prevent that deleted account from being silently recreated. It cannot be used to recover the deleted content.

An App Store subscription must be cancelled separately in Apple subscription settings.

Your rights

Depending on applicable law, you may request access, correction, deletion, restriction, portability, or object to processing, and may withdraw consent where consent is the basis. Contact josef.richter@me.com. You may also complain to your local data-protection authority.

Changes and contact

Material changes will be communicated through the app or website. Questions can be sent to josef.richter@me.com.