Privacy Policy

Last updated: October 2, 2026

Boocheck (“the app”, “we”) is a meal-photo calorie and macro tracker for iPhone. This policy explains what data the app handles and why. We collect as little as possible.

Your account

Boocheck associates your meal log with an account identifier. You can preview up to five meals before subscribing. Sign in with Apple links your diary to your Apple sign-in identifier so you can recover it on another device. We receive the email address you choose to share with Apple, which may be an Apple private relay address. We store encrypted Apple credentials to support sign-in and revoke access when you delete your account.

What we store

To make the app work, the following is stored on our servers, associated with your account identifier:

• Meal photos you capture or choose, and the enhanced versions the app generates from them.
• Nutrition data derived from those photos — the recognized dish, estimated calories, and macronutrients (protein, carbs, fat).
• Meal descriptions and edits you type or dictate, and the AI responses used to update your diary.
• Your log — the meals you’ve recorded and their dates, plus goal settings such as a daily calorie target.

Automatic food detection happens on your iPhone first. You can choose individual photos instead of granting ongoing library access.

AI processing by OpenAI and Google

Boocheck uses AI services from two companies to analyze meals: OpenAI (through the OpenAI API) and Google (through the Gemini API). The app asks for your permission before it sends anything to them. The request names the data, the companies and the purpose. Until you tap Allow, the app sends no meal data to these services. Photos, descriptions and voice input are not analyzed, and nothing new is logged.

When you allow it, our server sends these providers only what is needed for each feature:

• Meal and label photos you take, choose, share, or allow the app to detect in your library. They are used to identify the food, estimate nutrition and create the enhanced meal image.
• Meal descriptions and chat messages you type or dictate. They are turned into diary entries or changes.
• Voice recordings you submit. They are transcribed into text.
• Your recent meal log (food names, portions, dates and nutrition values) and your calorie and macro goals. These are used to make nutrition estimates consistent, score meals, write the boo feedback and suggest healthier versions. When you ask the chat to change meals, up to three of your recent meal photos may be included.

We do not send your name, email address, Apple account details, account identifier, device identifiers, location or contacts to these providers. Photos that on-device detection identifies as non-food, or as containing people, never leave your iPhone.

OpenAI and Google process this data on our behalf under their API terms. Those terms limit its use to providing the service and do not allow it to train their models. The providers may keep requests for a limited period for abuse monitoring. They protect the data at least as well as this policy describes.

If we add or replace an AI company, we will update this policy and ask for your permission again in the app. You can withdraw permission at any time in Settings → AI meal analysis. The app then stops sending data to these services. Meals already in your diary stay stored on our servers until you delete them or your account.

What we do not do

• We do not sell your data.
• We do not show third-party advertising.
• We do not build advertising profiles about you.
• We do not require access to your contacts, location, or health records to function.

Camera and photos

Boocheck needs access to your camera and/or photo library only to let you add a meal photo. Photos are used to estimate nutrition and to display your log. You can revoke this access at any time in iOS Settings.

Subscriptions

If you purchase a subscription, the transaction is handled by Apple and by RevenueCat, our subscription management provider. We receive a subscription status (active or not) tied to your account identifier. We never see your full payment card details — those are handled by Apple.

Voice input

Live dictation uses Apple’s speech recognition services. When you submit an audio recording for transcription, the recording is sent through our server to our AI providers named above. The resulting meal description or command is stored with your diary. You can use text input instead.

Analytics and diagnostics

This website uses PostHog, hosted in the EU, to count page visits, the page that linked to this website, campaign tags in the link, clicks, and taps on the App Store button. PostHog derives an approximate location from your IP address. The website sets no cookies and stores nothing on your device, so a later visit is not linked to an earlier one. Website session recording is off.

Optional product analytics uses PostHog, hosted in the EU. It is off by default. If you enable “Share usage analytics”, we send screen visits and foreground engagement time, onboarding and import outcomes, technical processing counts/durations, purchase-interface outcomes, and screen recordings of your app sessions. Screen recordings hide all text and images before they leave your iPhone; they show screen layout, taps and navigation. Events use your opaque account identifier so activity on your devices can be associated with the same account. This identifier is pseudonymous, not anonymous. You can turn sharing off in Settings; that stops optional app and account-level backend analytics once the preference reaches the server.

Product analytics excludes your photos, photo-library identifiers, image hashes and URLs, meal names, descriptions, nutrition values, dietary goals, voice recordings, AI prompts/responses, and authentication credentials. Screen recordings capture no network requests or logs. Automatic interaction capture and analytics location enrichment are disabled.

Apple and RevenueCat still process purchases and subscription status to provide paid access whether or not optional usage sharing is enabled. RevenueCat subscription lifecycle reporting is separate from optional app analytics. We use PostHog’s EU-hosted error tracking for technical server reliability diagnostics. None of these services is used for advertising or cross-app tracking.

Data retention and deletion

You can delete your account and its server-stored meal data in the app under Account & privacy, including from the locked subscription screen. Uninstalling the app does not delete your server account or cancel your subscription. Cancel a subscription separately in your Apple account settings. We retain a one-way hash of a deleted account identifier to prevent accidental recreation by an old installation. Account deletion also queues removal of the associated PostHog person and historical events. This external deletion is retried separately; it does not delay deletion of your diary. For assistance or an analytics deletion request, contact us at the address below.

Children

Boocheck is not directed at children under 13, and we do not knowingly collect data from them.

Changes

We may update this policy as the app evolves. Material changes will be reflected here with a new “last updated” date.

Contact

Questions about privacy? Email us at support@boocheck.app.