Privacy Policy
Cexi uses account-linked data to personalize training, recovery, and coaching. Sign in with Apple is the production authentication method. We do not sell your data or use it for advertising. This page explains what stays on your device, what syncs to Supabase, and what is sent to AI or support services when you choose those features.
Contents
The short version
- Training, profile, body, workout, recovery, and selected wearable data may be linked to your account for sync and personalization
- Coach, plan generation, and selected image features send the relevant prompt, context, or image to Cexi's AI service and, when configured, an AI fallback provider
- Apple Health access is optional, read-only, and permission-based; Cexi does not write workouts or other data to HealthKit
- Progress photos stay encrypted on your device unless you deliberately attach an image to an AI request or an opted-in bug report
- You can manage permissions and delete your account and cloud data
- We never sell your data or use it for advertising
What we collect
- Account data: the Apple-provided account identifier, name, and email or private relay address that Apple shares, plus provider metadata needed to maintain your account. The production login surface uses Sign in with Apple only (see Storage & security).
- Profile & goals: name, age, experience level, training goals, split, equipment, and preferences.
- Workout and recovery data: exercises, sets, reps, weight, reps-in-reserve, notes, progression, readiness, recovery, and recommendation outcomes.
- Body metrics: height, weight, body-composition entries, and other measurements you enter.
- Health and wearable data: optional read-only Apple Health summaries and optional summaries from an Open Wearables connection, such as sleep, HRV, resting heart rate, activity, and body metrics.
- Photos and other user content: encrypted local progress photos, profile images, coach messages, plan-import images, food/body-scan images, and any text or image you choose to submit. Progress photos are not cloud-synced by default.
- Diagnostics and support data: app/device/OS version, locale, performance and crash signals, sync errors, notification interactions, and the description, app state, and optional screenshot in an opt-in bug report.
How we use it
- Generate and adapt your personalized training plans
- Estimate readiness and per-muscle recovery
- Power coach conversations and workout design with relevant context
- Produce daily briefings and trend insights
- Sync your history across your devices
- Diagnose technical issues and improve reliability
Most cloud-synced account, profile, workout, recovery, and submitted support data is linked to your Supabase account identifier so we can provide the requested service. We do not sell personal data, use it for advertising, or share it with data brokers.
On device vs. transmitted
Stays on your device by default: the training-intelligence models and their computations, your cached coach conversation history, and encrypted progress-photo files. These local records are removed when you delete them in the app or remove the app, subject to iOS storage behavior.
Transmitted when needed for a feature you use: signed-in account, profile, workout, and recovery records sync to Supabase for backup and cross-device access. Coach, plan builder, food/body scanning, and screenshot import send only the relevant prompt, context, or image for AI processing. Optional Apple Health and Open Wearables summaries may be included in synced records or AI context according to the permissions and sync choices you enable. Bug reports send their selected description, diagnostics, app state, and optional screenshot to Supabase.
Coach & workout design
- These features require network connectivity and are not processed on-device.
- When you send a message or request a plan, your prompt plus relevant recent profile, workout, recovery, health, or image context is transmitted over an encrypted connection to Cexi's first-party AI service.
- If that server is unavailable or the build is configured for it, requests may be routed to a third-party AI provider, which may include OpenAI.
- These requests are processed to provide the feature and are not used to build advertising profiles.
- Coach conversation history is cached locally; daily briefings generated from account data may be stored in your Supabase account for display in the app.
Apple Health
Access to Apple Health is optional and permission-based. This build requests read-only access to selected categories, such as sleep, heart rate, HRV, activity, body metrics, and other categories you select in the Health permission flow. Cexi reads HealthKit data to improve recovery-aware recommendations; it does not write workouts or other data back to HealthKit. You can revoke access anytime in iOS Settings → Health. Without Health, Cexi still works using your logged training and manual inputs.
Storage & security
- Core training data and models are stored locally on your device.
- Cloud sync uses Supabase, with row-level security so you can only access your own data.
- Data is encrypted in transit (TLS) between your device and our services.
- Authentication: Supabase Auth receives and validates the Sign in with Apple identity token and manages the resulting session. Cexi does not store an Apple password or raw identity-token credential. Sign in with Apple may provide a private relay address when you choose Hide My Email.
No system is perfectly secure, so use a strong device passcode and keep iOS updated.
Processors we use
We share data only with services essential to operating Cexi:
- Supabase: account authentication, cloud database, storage, sync, and bug-report storage.
- Apple: HealthKit, Sign in with Apple, and local notification services.
- Cexi AI: first-party inference for coach, workout design, and selected image features.
- Configured third-party AI provider: optional fallback inference when enabled for the build or used by the routing policy; this may include OpenAI.
- Sentry: crash, performance, and diagnostic telemetry. Cexi configures Sentry without screenshots, view hierarchy, email, or name; an account identifier may be used to group reliability events.
- Open Wearables provider: only when you connect a supported wearable service; Cexi requests the summaries needed for recovery and training features.
We do not share personal data with advertisers or data brokers for marketing.
Data retention
- Cloud data is retained while your account is active.
- You can delete your account in the app. After the authenticated
delete_account()operation succeeds, Cexi clears account-scoped cloud records and owned storage covered by the deployed deletion function, then clears local account data. - Backup and operational-retention timing depends on the deployed infrastructure configuration and is being verified. We will update this section before the Terms are finalized rather than promise an unverified period.
Your rights
Depending on your jurisdiction, you may have rights to access, correct, export, or delete your data; control notifications; and manage Health permissions in iOS Settings. You can export or delete your data in-app (Settings → Privacy Settings → Privacy & Data), or contact privacy@cexi.app. See Privacy choices for direct controls.
Children's privacy
Cexi does not use an in-app age-verification gate. We still apply age-aware safety rules to training and coaching when age information is available. If you believe a child has provided personal data, contact us and we will review and delete it as required.
Changes
We may update this policy. When we make material changes, we will update the effective date above and may notify you in the app.
Contact
Privacy: privacy@cexi.app
Support: support@cexi.app
Legal: legal@cexi.app
Security: security@cexi.app
Home · Methodology · Privacy choices · Terms · Support