Who operates Nourish
Nourish is operated by Joshua Mayr. Use the support form for questions about privacy, access, correction, or deletion. Include contact information and the type of request, without adding unnecessary health details.
What stays on your device
Your journal includes records you choose to create: food, water, weight, treatment plans and doses, symptoms, check-ins, notes, milestones, reusable meals, and personal targets. The app stores these locally with iOS data protection. App-managed sensitive journal files are excluded from automatic device backup where the app can set that protection.
Local reminders, appearance preferences, Health permissions, and imported Apple Health data stay on the device. The app does not require an Apple-linked Nourish account to keep a local journal. Purchase verification still uses an anonymous server-issued account identifier.
Optional cloud backup
When you sign in with Apple and enable backup, app-created journal records, profile preferences, and targets are transmitted to Nourish’s Cloudflare backend for recovery and synchronization. Apple provides an account identifier; Nourish does not ask Apple for your name or email. Imported Apple Health records and meal photos are excluded from the journal backup.
Disabling backup stops future synchronization from that device. It does not delete an existing cloud copy. Use account deletion to remove the cloud records. Changes made offline, including consent revocations, may need a connection to finish on the server.
Optional meal analysis
Photo and text analysis is a separate choice. When enabled and available, Nourish sends the selected meal photo or description to OpenAI to generate a draft food estimate. The app asks for permission before this processing. It does not send your treatment history, Health imports, weight history, or other journal context with the meal.
The app resizes selected photos and removes their original metadata before upload. Cloudflare stores processing photos privately; processing photos and analysis results are scheduled for deletion after 24 hours, with additional scheduled cleanup. Revoking AI consent cancels remaining jobs and removes their stored inputs and results from Nourish’s processing systems. Data already sent to OpenAI is subject to OpenAI’s policy and its applicable API retention controls; Nourish does not claim zero processor retention. Results are estimates that you review before saving.
Apple Health
Apple controls authorization for supported weight, step, water, and dietary data. Reading and writing are separately optional. Health imports are not used for advertising, sent to OpenAI, or included in Nourish cloud backup. Nourish tracks its own written samples so edits can replace them. You can manage permissions and stored Health records in Apple Health.
Purchases
Apple handles payment. RevenueCat processes subscription status, product and transaction identifiers, an anonymous billing identifier, and ordinary purchase-device metadata. Nourish sends no medication, symptom, food, weight, or journal attributes to RevenueCat. Nourish does not receive your payment-card details. See RevenueCat’s privacy policy and Apple’s privacy policy.
Food search
Online food search sends the food query or barcode to Nourish and the USDA FoodData Central service. Search for food, not personal health details. Public food records may be cached separately from journals. Source links identify the database record. Nutrition lookup does not require sending your journal history.
This website and support
The portion tools run in your browser and do not transmit portions or personal health information. The site has no advertising pixels, session replay, or analytics cookies. Cloudflare serves the site and processes ordinary connection data such as IP address, user agent, and request time under its service policies.
If you join the launch list, we store your email, the signup source, consent version, and date. The list is separate from private journal records. We use it for the updates you requested and remove the entry when you unsubscribe. Support requests store your email, category, message, and reference number until the request is resolved and for up to 90 days afterward. Please leave health details out of support messages.
Retention, access, and deletion
Your local journal remains until you delete it or remove the app. Cloud journal records remain until account deletion. We retain minimal deletion markers while an account exists to prevent deleted records from reappearing during sync. Temporary processing files are short-lived as described above. Export files are local and removed from the app’s export cache during cleanup; copies you share elsewhere remain under that destination’s control.
Saved records can be read, exported as PDF, CSV, or JSON, and deleted even after paid access expires. Account deletion removes active cloud records and sessions and queues remaining temporary files for removal. Infrastructure backup copies may remain until the provider’s backup retention expires. Deleting an account does not cancel an Apple subscription.
Security and service providers
Nourish uses HTTPS for network requests, private object storage, authenticated ownership checks, and iOS Keychain for session credentials. App and API logs intentionally exclude journal text, photos, and health fields. Cloudflare provides hosting, database, queue, and storage services. The production database and private processing bucket are provisioned with EU jurisdiction; edge request handling and other processors may operate in other locations. See Cloudflare’s privacy policy.
No system can guarantee that data will never be lost. Keep an export if you need an independent copy. Nourish does not sell health records or use them to target advertisements.
Audience and changes
Nourish is intended for adults managing their own records. It is not designed for children or emergency care. We will update this page when the app’s data handling changes and request new consent when needed for a new optional use.