Effective September 24, 2026

Privacy policy.

BroCallory helps you estimate and track meals. Nutrition and body measurements can be sensitive, so this page explains what the app handles and how to remove it.

Information you provide

• Account: email address, sign-in information managed by Clerk, and any name you provide.
• Goals and profile: year of birth, sex selected for the app's calculations, height, current and target weight, activity level, goal, and onboarding preferences.
• Meals: food descriptions, photographs you take or choose, voice recordings you submit, transcriptions, estimated calories and nutrients, edits, meal history, and progress.
• Purchases: product and subscription status associated with your account. Apple or Google processes the payment; BroCallory does not receive your full card number.

How the app uses it

We use this information to sign you in, calculate your daily target, analyze meals, save your history, show progress, apply free-use limits, provide Pro access and answer support requests. Estimates generated from a photo, voice note or description can be inaccurate and can be edited before saving.

Services that process data

Clerk handles sign-in. Convex stores account and meal data, including uploaded photos. Meal descriptions and photos are sent through OpenRouter to an AI model provider to estimate nutrition; audio recordings are sent to Groq for transcription. RevenueCat processes purchase status. Apple and Google handle in-app payments. In release builds, Sentry receives error diagnostics and Expo Observe receives performance diagnostics. Product analytics through PostHog is optional and off by default in the upcoming release. You can enable it after reading the disclosure in Profile → Account → Usage analytics, and turn it off there at any time. Older test builds may collect these events automatically. We do not intentionally include meal text, photos, voice recordings or body measurements in app-use events. Diagnostic data can include device, app version and technical error information. Expo Observe uses a persistent pseudonymous installation identifier. The upcoming release keeps PostHog identifiers and pending events in memory for the app session; older test builds may use a persistent PostHog identifier. These identifiers can link events within an installation or session. We do not use these data for targeted advertising or share them with data brokers.

Permission for AI processing

The upcoming release asks for permission before sending meal information to OpenRouter and its model hosting providers (DeepSeek and GLM models), or recordings to Groq. Voice transcripts are then sent to OpenRouter for nutrition analysis. You may decline and keep viewing saved meals. Permission is stored for this account on this device and can be withdrawn in Profile → Account → AI data permission. Withdrawal prevents future requests until you agree again; it does not recall information already sent or delete your saved meals.

Camera, microphone and notifications

Camera and photo-library access is used when you choose a meal image. Microphone access is used when you record a voice note. You can deny or change these permissions in device settings. Meal reminders use local notifications on your device; the app does not need your contact list or precise location.

Retention and deletion

Saved meals, profile measurements and account progress remain until you delete them or delete your account. Photos uploaded for analysis are associated with your account; a photo you do not save as a meal can remain until account deletion. Voice recordings are normally removed from our storage after transcription, including when transcription fails. If a recording is uploaded but the app closes before transcription, an automatic cleanup removes it within an hour. To delete your account and associated data, use Profile → Account → Delete account and data, or use the web request if you no longer have the app. We request removal of the linked sign-in and purchase profiles from our providers. Some providers may keep limited records where required for security, fraud prevention or legal compliance; Apple and Google control their own transaction records.

Choices and contact

You can edit or remove meals in the app, revoke camera or microphone permissions in device settings, and contact us about access, correction or deletion. For privacy questions, email mixakievchanen@gmail.com. We may update this policy when the app or its providers change; the effective date above shows the current version.