Our latest internal security audit found no leaked credentials, no privilege-escalation path and no cross-account reads — its one high finding, unbounded AI spend per account, was fixed with durable metering. The design below is what keeps it that way.
📱
On-device pose analysis
The camera feed is analyzed on your phone in real time and never uploaded. Media leaves the device only when you act on it: a meal photo to log calories, a machine picture to build a profile — or a post you explicitly publish to the community feed.
🎫
Scoped upload tickets
Every media upload goes through a short-lived signed ticket bound to your account and the exact object, with per-file type and size caps and a daily byte budget. Access expires in minutes, not months.
🔑
Verified API tokens
Every API request carries a Firebase ID token verified against Google's certificates with the issuer and audience pinned — unsigned, mis-issued or foreign tokens never get through.
🛡️
Server-enforced rules
Database and storage rules run on the server. Account tier, admin status and professional badges are never writable by any client — and care-circle access is granted by you and cut the moment you revoke it.
⚖️
Metered AI usage
Every AI call is metered per account with durable daily ceilings, so abuse of the shared infrastructure is capped hard — not just rate-damped — and every prompt is logged for review.
🇧🇷
LGPD-first health data
Health data is owner-only by default. Sharing is explicit, consent-based and revocable; deletion is available in-app, on the web, and cascades fully — account, media and logs.