Cafeity Get the app

Legal

Privacy Policy

Cafeity records some of the most sensitive information a person has — what medication you take, what you eat, how you feel and what you weigh. This policy says exactly what happens to it. It is written to be read, not to be survived.

Last updated 23 September 2026

Who we are

Cafeity is published by Shaheer Malik, registered at Jubilee Town, Lahore, Pakistan. For anything in this policy, write to support@shaheercare.com.

Cafeity is an independent product. It is not affiliated with, endorsed by or sponsored by Novo Nordisk, Eli Lilly or any pharmaceutical manufacturer.

Where the UK or EU GDPR applies, Shaheer Malik is the data controller. Our representatives are [EU_REP] and [UK_REP].

What we collect

What you log. Doses, including the date, time, prescribed amount, medication name and injection site. Meals and drinks. Symptoms in your own words with your own severity rating. Weight and body measurements. Progress photos, if you choose to take them. Notes.

Your account. An email address and authentication credentials. A date of birth, used once to confirm you are 18 or over.

Technical data. Crash reports and basic diagnostics so the app can be fixed when it breaks.

On this website. If you ask to be kept posted, we store your email address and the date you signed up, and nothing else. If you write to us through the contact form, we store your name, email address, subject and message so we can reply. The website asks for no health information.

Under UK and EU law, almost everything in the first group is special category data under Article 9. That classification drives every decision in this policy.

Why we are allowed to process it

For the core service, our lawful basis is Article 6(1)(b) — processing necessary to provide the app you asked for.

For health data specifically, our basis is Article 9(2)(a): your explicit consent. That consent is asked for on its own screen, in plain language, with a clear affirmative action. It is versioned and timestamped so we can show what you agreed to and when.

Consent is not a one-off. You can withdraw any of it at any time in Settings → Privacy, with immediate effect.

The five separate consents

They are genuinely separate. Only the first is required to use Cafeity at all:

  1. Health data processing — required. Without it there is no app.
  2. AI processing by Google Gemini — optional. Decline and all tracking, charts and the Visit Summary still work.
  3. Progress photo storage — optional.
  4. Product analytics — optional.
  5. Marketing email — optional.

Withdrawing AI consent purges your AI conversation history and switches the AI features off. It does not touch anything you logged.

Signing in with Google

Cafeity offers Sign in with Google as one way to create or access your account. It is optional — you can use an email address and password, or Sign in with Apple, and nothing in the app depends on choosing Google.

What Google data we access. If you choose it, Google shares a standard OpenID Connect profile with us: your email address, your basic profile information (name and profile picture), and the Google account identifier for your account. We request nothing else. We do not ask for, and cannot see, your Gmail, Drive, Contacts, Calendar, Photos or any other Google service.

What we use it for. Exactly one thing: to create your Cafeity account and let you sign back into it. The email address becomes your account address so we can send you service messages, such as a password reset or a notice that your account is scheduled for deletion. The Google account identifier is used only to recognise you on your next sign-in.

How it is stored and protected. The sign-in happens in the system browser, never inside an in-app web view, and your Google password is never seen by or shared with Cafeity. Google returns a signed identity token, our backend verifies it, and only then is a session created. The resulting profile is stored in our Postgres database under row-level security and encrypted in transit and at rest.

Who we share it with. Nobody. Google sign-in data is not sold, not shared for advertising, not given to data brokers, and not sent to any other third party. It is not sent to our AI provider, and it is never used to train any AI or machine-learning model, ours or anyone else's.

How long we keep it. For as long as your account exists. Delete your account — Settings → Delete account, no ticket required — and the profile is deleted with everything else, on the schedule set out in our deletion policy. You can also disconnect Cafeity at any time from your Google account permissions page.

Limited Use. Cafeity's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

What the AI does and does not see

If — and only if — you give the separate AI consent, some of your data is sent to Google Gemini to power meal photo analysis, food parsing, Ora's answers and the weekly narration. The consent screen names the processor and states what is sent before you agree.

Every figure Ora quotes is calculated by the app first and checked against your own log. Ora will not name a condition, predict an outcome or comment on your dose — those are product limits, not phrasing.

Your data is not used to train Google's models or ours.

Who else touches your data

Only the processors listed below, each under a data processing agreement, and each only for the purpose named. Nobody else.

We do not sell your data. We do not share it for advertising. We do not use it for advertising ourselves. There are no advertising or marketing SDKs anywhere in the app, and the dependency list is checked automatically to keep it that way.

We will disclose data if a law compels us to. If that ever happens and we are permitted to tell you, we will.

Every third party that processes Cafeity data, and the only thing each is used for.
ProcessorWhat it doesNotes
SupabaseApplication backend: account, Postgres database and file storageRow-level security; every row is scoped to the account that owns it
Google (Gemini)AI features only — meal photo analysis, food parsing, Ora answers, weekly narrationOnly with your separate AI consent
AppleApp distribution, and subscription billing through the App StoreApple does not share your health record with us
CloudflareThis website, and the waitlist email storeWebsite only — no health data
Open Food Facts · USDA FoodData CentralThe food database Cafeity ships and queriesReference data only; your log is never sent to them

Where it is stored

Health data lives in your own account in our Postgres database, hosted by Supabase, and on your device. It is not stored in iCloud.

Access is enforced by row-level security in the database itself, not by application code. Every table carries policies comparing the requesting account against the row's owner, so a query for someone else's record returns nothing — even if the application above it has a bug.

Our database is hosted in the United States (Supabase, US West). Where your data is processed outside your own region, that transfer is covered by Standard Contractual Clauses.

Where AI inference happens outside the EEA, the transfer is covered by Standard Contractual Clauses and a documented transfer impact assessment, and the AI consent screen tells you so before you agree.

Your rights, and how to actually use them

Get a copy (Arts 15 & 20). Settings → Export produces a machine-readable JSON bundle plus CSVs plus a PDF. No support ticket, no waiting on us.

Delete it (Art 17). Settings → Delete account removes your record. The detail is on the deletion policy page.

Correct it (Art 16). Every record you log is editable and deletable from its own detail view.

Withdraw consent. Settings → Privacy, any of the five, at any time.

Complain. You can complain to your data protection authority — in the UK, the Information Commissioner's Office. We would rather you told us first at support@shaheercare.com, but it is your right either way.

If you are in California: we do not sell or share personal information as those terms are defined, so there is nothing to opt out of. We honour Global Privacy Control on this website.

Age

Cafeity is for adults. Onboarding asks for a date of birth and blocks anyone under 18. We do not knowingly collect data from children. If you believe a child has an account, write to support@shaheercare.com and we will delete it.

If something goes wrong

We keep a documented breach runbook with a named owner and a 72-hour notification path to the relevant authority. Where a breach is likely to result in a high risk to you, we will tell you directly.

Changes to this policy

If we change it materially we will tell you in the app before the change takes effect, and the date at the top of this page will change. Past versions are available on request.

Contact

Questions about this document go to support@shaheercare.com. We answer them.

Medical questions belong with your prescriber, not with us. Cafeity support cannot answer them and will not try.

The other documents

  • Data Deletion Policy — Delete it yourself in two taps, what goes, what stays, and how long backups hold on.
  • Terms of Service — What you are agreeing to, and the limits of what Cafeity claims to be.
  • End User Licence Agreement — The licence to use the app itself, including the terms Apple requires.
  • Security practices — How the health record is protected — and, honestly, what we have not done yet.
  • Medical Disclaimer — What Cafeity is for, what it will never do, and where every number comes from.
  • Licences and Attributions — The open-source code, food databases and design assets Cafeity is built on.