Privacy

Your data never lives on our servers.

That's not just a promise, it's an architecture. Your training data lives in your own iCloud database. The AI Connector that links your AI passes messages and keeps no workout data, ever.

This page explains our approach in plain English. The binding document is our privacy policy.

What each hop can see

Your AI

Sees what you ask it to read

Plans and history flow through your AI account, governed by that vendor's privacy terms.

AI Connector (ours)

Sees messages in transit. Keeps no workout data.

No workout database. One encrypted authorization token per account plus limited operational and diagnostic logs. This is the only piece we run.

Your iCloud

Holds everything

Your private database, keyed to your Apple ID. We have no credentials for it. We couldn't read your logs if we wanted to.

iPhone + Watch

Yours, physically

Execution and logging happen on-device. HealthKit stays under iOS permissions you control, and never leaves your device.

Six facts

No account

No sign-up, no email, no password. There is no user record to breach. The one sign-in you'll ever see happens on Apple's own page when you connect your AI. Parameter never sees your Apple ID or password.

Your iCloud

Every workout, plan, and note lives in your private iCloud database.

The Connector stores almost nothing

No workout data ever. One encrypted authorization token per account, deleted within hours of full revocation or data deletion, plus limited operational and diagnostic logs kept only to diagnose problems.

An AI can't touch your logs

Your AI can read your profile, equipment, and history, and write plans and workouts. It can never write your logs, your profile, or your equipment. Every new connection triggers a "Was this you?" alert, and a per-client revoke takes effect in about a minute.

Free export

All of it, as JSON/CSV, anytime, subscribed or not.

One-tap delete

Delete everything from your iCloud in one tap. There's no copy anywhere else.

What we don't collect

Any in-app analytics SDKs.

Any advertising identifiers.

Any third-party trackers. Parameter is written in pure SwiftUI, with no third-party SDKs phoning home.

Your GPS location. Parameter uses GPS to estimate speed and distance for outdoor workouts, but does not store a map of where you have been. GPS data never passes to the AI connector. Only the metrics derived from it (speed, distance) do.

App Store privacy label: Data Not Collected

These are claims about the shipped binary, and the App Store privacy label will say the same thing: zero third-party SDKs, nothing to declare.

A few answers

Does my AI provider see my data?

Your AI client processes what it reads under its own provider's terms, the same as any other conversation you have with it. Parameter's connector controls what's readable: profile, equipment, and history, never your raw health logs.

Diagnostics?

"Report a problem" opens a share sheet you send yourself. Nothing phones home automatically, ever.

What about a birthdate or age?

If your profile stores one, it lives in your iCloud database like everything else. It never reaches us. And your age isn't shared with your AI even when it reads your profile.

Notifications?

Notifications do four jobs: morning summary, workout reminders, rest timers, and check-ins. None of them is marketing, and none of them is a re-engagement nudge.

Ready for data protection law?

There's no workout database to subpoena and no Parameter account to breach. Export and delete are both one tap, built into the architecture rather than bolted on to satisfy a regulator.

Architecture beats policy.

But the policy exists too. The lawyer version

Coming soon to the App Store

The beta is open on TestFlight. Join the beta

Requires iPhone (iOS 17+). Apple Watch (watchOS 10+) recommended.