Privacy Policy

• Your data lives on your phone. There is no account, no sign-in, and no server that holds your training log.
• The app has no analytics, no advertising, and no tracking of any kind. It contains no third-party analytics or advertising software.
• Three things can leave your phone. Two of them are off until you turn them on: a conversation with the trainer, and an online food search. The third is a subscription receipt, and only if you subscribe.
• Apple Health data is read on your phone, shown to you, and never stored by the app. It is never sent anywhere unless you separately allow the trainer to see it, and then only as summaries inside a conversation you started.

On your phone. Your workouts, programs, body weight, food log, water and creatine marks, progress photos, settings, and any trainer conversations are stored on your device. Photos are stored as files protected by your device passcode. Trainer conversations are stored in a separate store that is kept for 90 days, and any conversation can be deleted at once from the trainer's settings.

In your iCloud, if you turn sync on. The app can mirror your training, food, and body data through iCloud, using your own private iCloud database. That data is readable by your devices and by nobody else, including the developer, who has no access to your iCloud account. Sync is off by default. Trainer conversations and Apple Health data are never synced. Apple's own privacy policy governs iCloud.

1. Conversations with the trainer

The trainer is off until you read a disclosure in the app and turn it on. When you send a message, the app sends:

• your message, and
• summaries of your training log, programs, goals, and body weight.

If you separately allow it, one meal photo you attach is sent for analysis, and sleep, steps, and active energy from Apple Health may be sent as summaries. Each of those is its own switch and each is off until you turn it on. Nothing is sent until you tap send: there is no background transfer.

Where it goes. Your message goes first to a private server operated by the developer, and from there to the model provider that server is configured to use: OpenAI, and, when configured, Anthropic. Those providers process the request under their own API data policies and retention terms; the developer's server asks them not to retain it where their API offers that choice. The developer's server does not store your messages, your training data, or your photos. The public trainer service is live, and the server keeps a pseudonymous install identifier and usage counts against it so it can enforce a per-device budget; it does not keep the content of any conversation. That identifier is derived from a key your device generates and is also sent to the model provider, as an abuse-containment label, alongside the request.

The trainer is not Apple's Private Cloud Compute and is not a named vendor's app; it is a relay the developer runs. The app never holds a model provider's credential.

What the app records for you. Every trainer turn keeps a record on your phone of which categories of information entered the request. That record is yours, on your device, and is deleted with the conversation. It is stored rather than displayed today; the screen that reads it back shows the changes you confirmed and the replies you reported, and the per-turn rows are not on it yet.

2. Online food search

Searching for a food online is off until you turn it on. When it is on, the text you type into food search is sent over HTTPS to Open Food Facts. Nothing else is sent with it: no name, no account, no device identifier, no training log, no body weight, and no food you have already logged. There is no account and there are no cookies. Open Food Facts sees the request's IP address, as any web server does, and a user-agent line naming this app and a contact email, which Open Food Facts requires.

You can turn online search off in Settings → Food data sources, and it takes effect on the next keystroke. The app's bundled food list works with online search off and with no network at all.

3. A SulAI subscription

If you subscribe to SulAI, the App Store gives the app a signed receipt for that subscription, and the app sends it to the same private server named above so the server knows the subscription is real and can count the month's usage against it. The server keeps that receipt's identifier and those counts, and nothing else: not your name, not your email, not your Apple Account.

The app never sees a card. The purchase happens in Apple's own sheet, Apple takes the payment, and no payment details are ever passed to this app or to the developer's server. Nothing in this section happens unless you have a subscription: with no subscription there is no receipt, and nothing is sent.

With your permission, the app reads these types from Apple Health: steps, active energy, sleep, workouts, resting heart rate, and heart rate. They are read when a screen appears, shown to you beside your training, and held only while that screen is open. The app never writes to Apple Health, never stores what it reads, never uses it to set a load or a rep target, and never sends it through iCloud.

Health data leaves your phone in exactly one case: you have turned the trainer on and separately allowed health context, and you send a message. Then sleep, steps, and active energy may be sent as summaries inside that conversation, to the server and provider named above. Heart rate and workouts are never sent. You can revoke either permission at any time in the app, and revoke the app's Health access in Settings → Privacy & Security → Health. Health data is never used for advertising, marketing, or shared with any third party for any purpose other than answering the message you sent.

• No analytics or crash-reporting software from any third party.
• No advertising, no advertising identifiers, no tracking across apps or websites.
• No selling, renting, or sharing of your data with anyone for their own purposes.
• No account, and therefore no account data.

SKomp Forge is intended for adults. The trainer's conversation feature is for people aged 18 and over. The app does not knowingly collect personal information from children.

• On your phone: delete the app. Everything the app stored on the device is removed with it. A single trainer conversation can be deleted from the trainer's settings without deleting the app.
• In iCloud, if sync was on: on your iPhone, open Settings → [your name] → iCloud → Manage Account Storage, find SKomp Forge, and delete its data. Do this after deleting the app, or the app will sync it back.
• Trainer: the server holds no content of yours, so there is nothing of what you said to delete. What it does hold is the pseudonymous install identifier described in §1 and the usage counts kept against it, plus a subscription receipt identifier once you subscribe. Email admin@skomp.studio with nothing more than a request and we will revoke that identifier, which is what deleting it means. Data sent to a model provider or to Open Food Facts is handled under that provider's policy for the time they state.

If this policy changes, the effective date above changes with it, and the page at this address is the current version.

Questions about this policy or about your data: admin@skomp.studio.