Last updated: September 21, 2026
Merid is a personal health assistant: you manually log food, workout, sleep, water, weight, labs, supplements and medication data, and the app uses AI (Google Gemini and Anthropic Claude, contracted by us) to cross-reference that information and return recommendations. This page explains what data is stored, what is sent to the AI, what is never saved, and who your data is shared with.
Merid is operated by Salomão Junior, an individual, who is the controller of the personal data processed in the app — the one who decides what is collected and why.
The same person acts as data protection officer (DPO, art. 41 of the Brazilian LGPD). The channel for anything privacy-related — a request, a question or a complaint — is privacy@merid.life and you get an answer within 15 days.
Health data is sensitive personal data, and the law requires us to state which basis each kind of processing relies on. There are four here:
Specific, highlighted consent (art. 11, I): for all health data — food, workouts, sleep, weight, labs, medication, glucose, cycle and progress photos. You choose to log each of them, and you can withdraw consent by deleting the entry, turning the module off or deleting your account. Withdrawing consent does not erase what was lawfully processed before, but it stops processing from then on.
Performance of the contract (art. 7, V): account, login, preferences and, for subscribers, the billing data needed to keep the plan active.
Legal and regulatory obligation (art. 7, II): tax and accounting records of payments, kept for 5 years (tax retention period) even after cancellation.
Legitimate interest (art. 7, IX): service security, abuse prevention and aggregate product usage metrics — always with data that does not identify you to whoever looks at it, and never for advertising.
Login is done through Google, through Apple, or through a magic link sent to your email. We store the name, email and profile photo the chosen provider gives us — we store no password, because the app has none. Your identity is the provider + account pair, not the email address: changing your email at Google does not move your data to another account.
Signup is open: every new user lands straight on the Free plan as soon as the login is confirmed, with no queue and no manual approval. Accounts that break the Terms can be blocked afterwards.
Food (photo of your plate): the photo is compressed and saved (Vercel Blob), so you can review the entry later.
Label/nutrition facts: the photo is used only to extract the values and then discarded — never saved.
Labs: the lab photo is never saved. Only the extracted markers (text/numbers) and the AI's comment are stored.
Medications (prescription): the photo or PDF of the prescription is never saved. Only a text summary of what was identified is kept.
Supplements (composition photo): the label photo is used only to extract the composition table and then discarded — never saved.
Workout (photo OCR): the photo only fills in the workout description as text; the image itself is not saved.
Photos/PDFs received via "Share" from your phone sit in a temporary space only until processed, and are deleted right after.
We never send your raw history to the AI. Insights questions and diet/workout suggestions use an aggregated summary (last 7 days, profile, goals) — not a line-by-line export of your entries.
The AI provider is chosen by us, not by you: today nearly all traffic runs on Google Gemini, with Anthropic (Claude) stepping in when the first one fails. That applies to every route, Labs and Medications included. Both receive the data only to produce the answer you asked for, and neither is allowed to use it to train models.
You never provide or see an API key: the AI cost is built into the service. The daily analysis limits exist to keep that cost predictable, and they never limit manual logging of your own data.
The "Tell us about your life" field (Profile) is summarized by AI once, when saved, into a few short factors — only that summary, never the original text, is sent in diet/workout/cardio suggestions and Insights. The original text stays saved only for you to reread and edit later.
Google: authentication (OAuth), when you sign in with Google.
Anthropic / Google Gemini: AI processing, as described above.
Open Food Facts: the barcode scanner queries this public database only by product code — no personal data of yours is sent.
Vercel: app hosting, database (Neon), file storage (Blob) and aggregated usage metrics (Analytics/Speed Insights).
Apple: authentication, when you sign in with Apple. If you use "Hide My Email", we only receive Apple's relay address.
Stripe: subscription payment processing. It receives name, email and the card details, which are typed into Stripe's own environment — Merid never sees or stores a card number. No health data is sent.
PostHog: product usage metrics, tied to an internal identifier, with no name, email or health content.
It does, and it happens every time you use the app. The infrastructure (hosting, database, file storage), the AI providers and the payment processor all operate outside the country, mainly in the United States. In practice: what you log is stored and processed abroad.
The transfer relies on your consent to the processing described in this Policy (art. 33, VIII of the LGPD) and on what is necessary to perform the contract with you (art. 33, V). We pick providers that offer contractual data protection clauses and security commitments equivalent to the ones required here — and that contractually commit not to use your content to train models.
We do not sell, rent or assign your data. We do not use it, nor allow it to be used, for decisions about credit, insurance, employment or any discriminatory purpose. We do not send it to a health plan, an employer or a family member — only to whoever you yourself authorise, if and when that feature exists.
We also do not use your data to train AI models, ours or anyone else's.
The app uses its own cookie to keep you signed in — without it there is no session. Beyond that, we collect product usage metrics (PostHog) and page performance metrics (Vercel Analytics), which record event and screen tied to an internal account identifier — not to your name or email, and never to the content of your health entries.
There is no advertising in Merid: no social network pixel, no ad network and no third-party marketing tracker.
Traffic between your device and the server is encrypted (HTTPS/TLS), and the database and file storage are encrypted at rest by their respective providers. All data is tied to your account and the app's queries are filtered by it — no screen reads another user's data.
No system is impenetrable, and we will not claim otherwise. What we do claim is what is described here: the minimum amount of data kept, immediate disposal of what does not need to stay (lab, prescription and label photos), and real deletion when you ask for it.
If you enable notifications, we store your device's subscription (the browser's technical endpoint) only to send alerts — no health data goes into the notification content beyond the alert text itself (e.g. "you missed logging sleep today").
Deleting a single record is done item by item, inside the module itself (with a 5-second undo).
While logged in, you can delete your entire account and all associated data with 1 click, below — immediate and permanent, with no one in between. The deletion runs as a single operation: either all of it goes or none of it does, so your account is never left half-erased.
Blocked account, or any case where you cannot sign in: request deletion via the contact email below.
What is deleted and what is kept: deleting your account immediately erases your profile, every log (meals, workouts, sleep, weight, lab results, medications, glucose, cycle and symptoms), photos and files. Database backups stop containing this data within 7 days. Only payment records (plan, amount and date) are kept, for 5 years as required for tax purposes, along with usage statistics that do not identify you. Stripe, Apple and Google keep their own records of the charges they processed.
The LGPD (art. 18) guarantees you, at any time and at no cost:
Account deletion you perform yourself, on this page. Other requests go through the privacy channel, answered within 15 days. If you believe we handled your request poorly, you may complain to the Brazilian data protection authority (ANPD).
In the event of a security incident that may bring relevant risk or harm to you, we will notify you and the Brazilian data protection authority (ANPD) within a reasonable time, as required by art. 48 of the LGPD — describing what data was affected, what has already been done, and what you should do.
Merid is meant for people 18 or older and does not knowingly collect data from children or adolescents. If we identify an account created by a minor, the data is deleted. A guardian who suspects this can request deletion through the privacy channel.
Questions, data deletion requests, or any other privacy request: privacy@merid.life