Privacy-First GLP-1 Tracking with Pokii

Quick answer

• Storage: Structured data via iCloud; progress photos via iCloud Drive.
• No: Ads, public feed, or selling tracking data for targeting.
• Health: Optional, scoped read/write (weight, nutrition, water)—not heart rate, steps, or sleep.
• Export: Pokii JSON backup you share or schedule yourself.

Where your data actually lives

Pokii's structured data — your shots, doses, check-ins, weight, and body measurements — syncs through your personal iCloud account. In practice, that means your data is stored on your device and synced across your signed-in Apple devices, the same way Apple syncs Photos or Notes. It isn't sent to a Pokii-run analytics server or a third-party data broker as part of that sync.

Progress photos work the same way: they're stored via iCloud Drive rather than uploaded to some separate media host. If you ever want a portable copy of your data outside of iCloud, Pokii also supports manual export as a Pokii JSON backup through the share sheet, with an optional daily auto-backup and a full restore path from that JSON file. That backup format is also how you'd move data between devices or recover after a reinstall — it's an export you control, not a background upload you don't see.

Because sync runs through your personal iCloud account rather than a company-hosted database, Pokii doesn't operate a central server holding everyone's shot history and weight data in one place. Your account is scoped to your own iCloud, under your own Apple ID.

No ads, no public feed, no ad-driven data use

Pokii doesn't run ads, and there's no ad-driven social server behind the app. There's also no public social feed — nothing you log in Pokii (a shot, a check-in, a progress photo, a note about side effects) is posted anywhere other people can see it. This is worth being explicit about because GLP-1 dosing and weight data are sensitive by nature, and an app that's designed around a public feed or an ad business has different incentives than one that isn't. Pokii's model doesn't include either of those, so there isn't a feed to opt out of and there isn't ad targeting built on top of your tracking history.

The app is funded through optional App Store subscriptions, not advertising. Your tracking data isn't traded for features — permissions and exports are about what you choose to connect, not how much you share.

What permissions Pokii asks for

Pokii's Apple Health integration is permission-based and scoped to specific data types — it isn't an all-or-nothing grant. With permission, Pokii can read body mass, lean body mass (used only as a read-only chart overlay — Pokii doesn't write lean body mass back to Health), dietary water, and nutrition values (calories, protein, carbohydrates, fat, fiber, sugar, sodium), along with date of birth and biological sex for chart context. Pokii writes back to Health in a similarly limited way: body mass, dietary water, and the nutrition macros generated by its meal-scanning feature. Health authorization is offered during onboarding alongside notification permissions, but it's presented as optional there, and you can revisit it later from Settings → Apple Health if you want to re-request authorization or check what's currently granted.

If you'd rather bring in history from elsewhere, Pokii supports importing a Pokii JSON backup, a Shotsy JSON export, or a header-based CSV file, each converted into Pokii's own data format with a duplicate-detection and cleanup pass afterward. Export out of Pokii is JSON through the share sheet rather than CSV, so whatever leaves the app leaves in a format you control and can inspect, not a silent sync to another company's servers.

Taken together, the pattern is consistent: your GLP-1 data lives on your device and in your personal iCloud, Health permissions are scoped and optional rather than blanket, and there's no ad business or public feed sitting behind any of it.