Data Usage & Privacy

SOMA is provided by SOMA ("SOMA", "we", "us") — [Registered company name and address — fill before launch]. This page is a plain-English companion to our full Privacy Policy. It answers three questions directly: exactly what wearable and training data SOMA uses, what it produces from that data, and what it is never used for.

SOMA is a Training Intelligence platform. It reads recovery, sleep, activity and training data to generate personalized training recommendations and adaptive training decisions — how much volume, how hard to push, when to add load, and when to deload. SOMA is not a medical device and does not provide medical advice, diagnosis, or treatment.

1. What we read, and why

SOMA reads only the specific data types you authorize. Each category has one job: to feed your recovery read and the day's training decision. Here is what we use, why we read it, and what it produces.

• Sleep (duration & stages) → a restorative-sleep and recovery read → today's training decision.
• Heart-rate variability (HRV) → your core readiness signal → how hard to push today.
• Resting heart rate → confirms recovery state and trend → readiness confidence.
• Respiratory rate, blood oxygen (SpO2), body temperature → context that sharpens the recovery read → a more reliable daily decision.
• Readiness / recovery scores (e.g. from Oura) → a direct recovery input → your daily readiness.
• Workouts & activity → measured strain and training load → fatigue tracking and when to deload.
• Training data you log — sets, reps, loads, effort (RIR), programs → derived volume, fatigue and training load → load progression and adaptation.
• Account & profile data you provide (e.g. name, training preferences) → tailors recommendations to you.
• Waitlist email, if you join the waitlist → lets us tell you about early access.
• Limited technical & usage data → privacy-respecting, minimized diagnostics → reliability and improvement, never advertising profiles.

2. What we create from it

SOMA turns those inputs into a small set of derived signals, and then into one clear decision:

• Recovery / readiness — a daily read of how recovered you are, computed on your device wherever possible.
• Fatigue & training load — an estimate of accumulated stress from your training and activity.
• Adaptation — patterns SOMA learns over time about how your body responds to load.
• The training decision — the day's recommendation: how much volume, how hard to push, when to add load, and when to deload.

These outputs exist to run the Service for you. They are not sold, and they are never shared for advertising.

3. What we never do

• We never sell your data — not your health data, not your training data, not your email.
• We never use health or wearable data for advertising, and we never share it with advertising networks or data brokers.
• We never make medical decisions. SOMA does not diagnose, treat, or give medical advice — it gives training recommendations.
• We never access data types you didn't authorize. SOMA reads only the specific types you approve, and stores only what it needs.

4. Where your data lives

SOMA is on-device first. Your recovery read, fatigue and load estimates, and the training decision are computed on your device wherever possible. On Apple devices, Apple Health data is read on-device via HealthKit — only the types you authorize in the iOS permission prompt. Per Apple's rules, HealthKit data is never used for advertising or marketing, is never sold, and is used only to provide SOMA's health and fitness features.

If you connect Oura, SOMA accesses the sleep, readiness, activity and related metrics you approve through Oura's official API and your explicit OAuth authorization, then uses them to feed your recovery model and training decisions. SOMA stores only what it needs, never sells Oura data, and never shares it for advertising. See the Oura Integration Disclosure for details.

The little data that must go off-device — such as your waitlist email or any account data — is handled by vetted infrastructure providers under confidentiality and data-protection obligations, encrypted in transit and at rest where supported.

5. Staying in control

You can disconnect any source or delete everything at any time.

Disconnect Apple Health

Go to iOS Settings → Privacy & Security → Health → SOMA and toggle off the data types (or all of them). SOMA immediately stops reading new HealthKit data.

Disconnect Oura

Open SOMA → Settings → Integrations → Oura (Disconnect). This revokes SOMA's access token, so SOMA stops accessing Oura data. You can also revoke access in your Oura account at cloud.ouraring.com (account / connections).

Delete your data

Delete your account and data either in-app at Settings → Account → Delete Account, or by emailing hello@somaintelligence.app from your account email. On deletion, your SOMA account and associated server-side data are deleted, integration access tokens (e.g. Oura) are revoked, and on-device data is removed when you delete the app or use the in-app delete. Verified requests are actioned promptly — within 30 days, and sooner where required by law. Full details are on the Account Deletion page.

6. How this relates to the Privacy Policy

This page is a focused, plain-English summary. Our full Privacy Policy is the complete and governing statement of how we handle your data, including your legal rights, retention, sharing, and contact details. For the deeper data breakdown see Data Usage & Privacy, for the integration specifics see the Oura Integration Disclosure, and for the terms of using SOMA see our Terms of Service. If anything here is unclear, email us at hello@somaintelligence.app — we read every message.

Effective 2026-06-22. Governed by [Governing-law jurisdiction, e.g. England & Wales — fill before launch].