Brim privacy policy
Effective 17 September 2026, updated 28 October 2026 · applies to the Brim app for Android (package com.eurobuddha.brim) and iPhone (bundle com.eurobuddha.brim)
Brim is a food and health diary for adults, including people taking GLP-1 medicines. It is built so that your diary stays on your phone. There is no Brim account, no Brim server, and no analytics or advertising SDK in the app.
Who publishes Brim
Brim is published by Pickle Digital Ltd, a company registered in England and Wales (company number 16468184), registered office 1 Kings Avenue, London N21 3NA, United Kingdom. On Google Play the developer name is PandaApplications. For privacy questions or requests, contact eurobuddha@gmail.com.
Pickle Digital Ltd is responsible for this policy and is the controller of personal information sent to it, such as emails you send to the contact address. It uses that information only to reply and to keep a record of the request, on the basis of its legitimate interest in answering you, and deletes it when no longer needed. Your diary stays on your phone and is not held by Pickle Digital Ltd.
What the app stores, and where
- Your diary: meal photos, the words you type or dictate, calorie and macronutrient estimates, portions, water, symptoms, injections, daily pills, bathroom log, exercise, weight and body photos. Stored only in the app's private storage on your phone. Your phone may include the diary and photos in its own backup when enabled (Google or Samsung Cloud on Android, iCloud Backup on iPhone), subject to the provider’s settings and storage limits.
- Your profile: weight, height, targets, medication name, dose, injection day, start date, conditions, foods to avoid. Stored on the phone.
- Health Connect (Android) or Apple Health (iPhone) data (only if you connect it): weight and body composition, heart rate, resting heart rate, heart rate variability, blood oxygen, blood pressure, respiratory rate, body temperature, VO₂ max, sleep, steps, workouts and active calories, as written by your watch or apps such as Withings. Brim reads these to show them in Insights and to provide context for AI food suggestions when you allow a provider. It is copied into the app's private database and is included when you choose to save a Brim backup. If you grant nutrition write permission, the meals you log are written to Health Connect or Apple Health as nutrition records. Revoking access in Health Connect or the Health app stops further reads; deleting the app deletes the copy.
- Drink reminders (Android, on by default, switch off in Settings → Drink reminders): Brim reads the time of your phone's next alarm and your logged water to decide when to remind you. The alarm time and reminder schedule stay on the phone. Tapping "Drank 250 ml" on a reminder logs water in your diary.
- API keys you enter for AI providers are kept encrypted by the Android Keystore or the iOS Keychain and never leave the phone except to authenticate your own requests to that provider.
What leaves your phone, and to whom
AI sharing is optional. Adding an API key does not grant permission. Before any AI content is sent, Settings → AI setup names the provider, explains the data and uses, and asks for your explicit consent. Brim stores the provider, disclosure version and time of your permission on your phone. Existing keys also need permission.
- Food estimates: the plate photo (downsized), meal description, corrections and any prior estimate being corrected.
- Profile context for estimates and suggestions: weight and height if tracked, nutrition targets, medication name and dose, treatment timing, conditions, daily medicines and supplements, and foods to avoid.
- Food suggestions: today's meal names, nutrition and fluid totals, exercise calories, medicines taken, injection timing, symptoms and bathroom notes, plus what you tell Brim you have available. Some context can come from connected health data.
- Exercise estimates: your exercise description and profile context.
- Transcription: a voice recording sent to an allowed Groq or OpenAI provider. Brim deletes the temporary recording after the transcription attempt.
- Generated meal pictures: when enabled, saving a meal without a photo can send its name and portions to an allowed OpenAI, xAI or Gemini image service. Manually requesting a picture also sends this description. Body photos are never sent to AI.
Your preferred allowed provider is tried first. Other providers you separately allow may receive the same request automatically if it fails. Voice and pictures use allowed providers that support those features. Withdraw one provider's permission, or stop all AI sharing, in Settings at any time. This stops new requests; it cannot recall requests already sent. Stored diary entries remain available.
Each provider authenticates requests to your API account and receives your IP address. Text or images you supply may also identify you. Retention, use, deletion and international processing depend on the provider's API terms, your account and region; Brim cannot promise anonymity or zero retention. Review the relevant terms before allowing sharing:
Without an allowed provider, no AI content is sent. Barcode lookups still contact Open Food Facts with the barcode number; that service also receives normal connection information such as your IP address. API-key checks contact the provider to list models, without diary content.
Backups you save
Settings → Backup and restore lets you save a file containing meals, meal and body photos, health logs, profile settings and maintenance history. API keys, purchase credentials, adult acknowledgement and AI permissions are excluded. Restoring a Brim backup preserves the receiving device's existing permissions. The backup file is not encrypted by Brim. You choose its location through the system file picker; if you choose a cloud storage provider, that provider handles the file under its own policies. Delete exported copies separately from the app. Restore checks the file before adding missing entries and only replaces profile settings when you select that option.
What we do not do
- No Brim servers, accounts, analytics, crash-reporting SDKs or advertising.
- No sale of diary data or use for advertising. Health information is used to display your diary and, with separate provider permission, to inform AI requests. It can also be included in exports and backups you choose to save or share.
- Brim does not send body photos to AI providers. They are kept in private app storage and included in backups you choose to save.
Permissions
- Camera: photograph plates, scan barcodes, body photos.
- Microphone: voice notes, transcribed by an allowed Groq or OpenAI provider. When no such provider is allowed, built-in dictation uses strictly on-device recognition where supported (Android 12+ or compatible Apple speech recognition). If unavailable, type your note or allow a transcription provider. Your keyboard's own dictation is controlled by its settings.
- Health Connect / Apple Health permissions listed above, requested only when you tap Connect.
- Photo library (iPhone): only the photos you pick for a plate or body photo.
- Notifications: drink reminders. You can refuse or withdraw this in your phone's settings.
- Run at startup (Android): re-schedules drink reminders after the phone restarts. Nothing is sent anywhere.
- Internet: the AI and barcode requests described above.
Deleting your data
Delete any entry inside the app, or uninstall the app to remove everything it holds on the phone. To remove your phone backup copy, use your phone's backup settings (Google, Samsung or iCloud). Requests already sent to an AI provider are governed by that provider's retention policy.
Purchases
Brim is free for 14 days with everything open, then the core diary stays free and Brim Full is a single one-off purchase through Google Play or the App Store. Google or Apple handles the payment under its own terms and privacy policy; Brim receives no card or billing details and stores only a purchase record on the phone so that Full stays unlocked, including offline. There are no subscriptions, no ads and no accounts.
Children
Brim is for adults aged 18 and over, with or without GLP-1 medication. Before using the app you must confirm that you are 18 or over. Brim records that acknowledgement on your phone without collecting a date of birth. This is a self-declaration, not identity verification.
Medical disclaimer
Brim uses AI for estimates and food suggestions. It is not a healthcare professional, and its output can be inaccurate. Check portions and allergens. Do not use it to diagnose a condition, change medication or replace advice from your clinician. Discuss symptoms and suitable nutrition targets with your clinician.
Contact
Questions about this policy: eurobuddha@gmail.com.
Your privacy rights
Brim is available in many countries. Under UK data protection law, and similar laws elsewhere such as the EU GDPR or US state privacy laws, depending on the circumstances, you may have rights to access, correct, delete or obtain a portable copy of your personal information, restrict its use, or object to its processing. Contact the privacy email above to exercise your rights concerning information held by the developer. Your diary is held on your device, so the developer cannot remotely access, correct or delete it. Use the app's editing, deletion, export and backup tools for that information. For information held by an AI, payment or backup provider, contact that provider through its privacy channels.
You can withdraw permission for future AI requests in Settings at any time. You can also complain to the UK's Information Commissioner's Office (ICO) or to the data protection authority where you live.
Visiting this policy page
This page is hosted on eurobuddha.com by Hetzner. It has no analytics or advertising scripts. The web server records ordinary access and error logs, which can include your IP address, requested page, time, browser information and referring page. Its configured log rotation keeps 14 daily rotated log files. These website requests do not upload your Brim diary or API keys.
Changes
If this policy changes, the new version is published at the same address and the effective date above is updated.