Cafeity Get the app

Legal

Security

Cafeity holds special category health data, so security is a product requirement rather than an operations afterthought. This page describes what is actually in place, and is equally clear about what is not.

Last updated 23 September 2026

In short

  • Encrypted in transit and at rest.
  • Per-record permissions — the database enforces that a record is reachable only by the account that owns it.
  • No advertising or tracking SDKs anywhere in the app.
  • Health data is never stored in iCloud.

This summary is here to be read. It is not a substitute for the document below, which is what actually applies.

How access is controlled

Every record carries permissions scoped to the account that created it, enforced by the backend rather than by the app. A client asking for someone else's record does not get it, regardless of what the client claims to be.

Server credentials are held server-side and never shipped in the app binary. Access follows least privilege.

Encryption

Data is encrypted in transit with TLS, and at rest by the storage layer. Progress photos are stored in access-controlled file storage under the same per-record permissions as everything else.

We have adopted HIPAA-grade technical safeguards — encryption in transit and at rest, access logging, least privilege — as a baseline. To be precise: Cafeity is not a HIPAA covered entity or business associate, and we do not claim to be HIPAA compliant. The safeguards are the standard we build to, not a certification we hold.

What is deliberately absent

There are no third-party advertising or marketing SDKs in the app or on any signed-in surface. This is checked automatically against the dependency list, because the FTC Health Breach Notification Rule treats disclosure through a tracking pixel as a breach.

Health data is never written to iCloud, never sold, never used for advertising, and never used as training data.

The AI boundary

AI features are off unless you separately consent to them. When enabled, the data described on the consent screen is sent to Google Gemini for that feature and nothing more. Declining leaves every other part of the app working.

What we have not done yet

Being straight about this is more useful than a page of reassurance:

  • Cafeity holds no security certification — no SOC 2, no ISO 27001. We are a small team, and Cafeity has not been audited.
  • No independent penetration test has been commissioned yet.
  • A Data Protection Impact Assessment is required before EU launch and is not yet signed off.
  • There is no bug bounty programme, though we will act on reports.

These will change, and this page will change with them. It will not gain claims before they are true.

Reporting a vulnerability

If you find a security problem, email support@shaheercare.com with enough detail to reproduce it. We will acknowledge it and keep you posted on the fix.

Please give us a reasonable chance to fix it before disclosing publicly, and please do not access, modify or delete data belonging to anyone else while investigating. We will not pursue good-faith research that follows those two rules.

If there is a breach

We maintain a documented runbook with a named owner and a 72-hour notification path to the relevant supervisory authority, plus direct notification to you where the risk to you is high. As a vendor of personal health records, we are also subject to the FTC Health Breach Notification Rule in the United States.

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

  • Privacy Policy — What we collect, why, who touches it, and how to get it all back or delete it.
  • 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.
  • 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.