Oura Integration Disclosure
Last updated: 2026-06-22
The short version. If you connect Oura, SOMA accesses only the sleep, readiness, activity, and related metrics you authorize through Oura's official API and your OAuth consent — to power your recovery read and training decisions. SOMA never sells your Oura data, never uses it for advertising, and lets you disconnect or delete it at any time.
1. Overview
SOMA is provided by SOMA ("SOMA", "we", "us") — [Registered company name and address — fill before launch]. SOMA is a Training Intelligence platform: it turns recovery, sleep, activity, and training data into personalized training recommendations and adaptive training decisions — how much volume to do, how hard to push, when to add load, and when to deload.
This page explains exactly how SOMA works with Oura. Connecting Oura is entirely optional. If you choose to connect, SOMA accesses your Oura data only through Oura's official API and only after you grant explicit OAuth authorization. You decide what to share, and you can withdraw that access at any time (see §6).
SOMA is not a medical device and does not provide medical advice, diagnosis, or treatment. For how we handle all data, see our Privacy Policy and Data Usage & Privacy pages.
2. What Oura data SOMA accesses
When you connect Oura, SOMA requests read access — via Oura's API and your OAuth consent — to the metrics it needs to model your recovery and inform your training. Depending on the scopes you approve, this includes:
- Daily readiness — your Oura readiness score and contributing signals.
- Sleep — sleep duration and stages, and related sleep metrics.
- Activity — daily activity and movement metrics.
- Heart rate & HRV — heart rate, heart-rate variability, and resting heart rate.
- Related physiological metrics — such as respiratory rate and body temperature, where you authorize them.
SOMA reads only the data types you authorize during the OAuth flow. It does not request access to data it does not use, and it cannot read anything you have not approved.
3. Why SOMA accesses it
SOMA uses your authorized Oura data for one purpose: to power your recovery and readiness model and turn that into your daily training decision. Specifically, SOMA uses these signals to:
- compute a daily recovery and readiness read;
- estimate your fatigue and training load;
- learn your adaptation patterns over time; and
- generate personalized training recommendations — how much volume, how hard to push, when to add load, and when to deload.
Your Oura data is used to provide these health and fitness features to you, and for nothing else.
4. How SOMA uses & stores it
SOMA processes your Oura data on your device wherever possible. It stores only what it needs to deliver your recovery read and training decisions, and no more. Any data that must go off-device (such as account data) is handled by vetted infrastructure providers under confidentiality and data-protection obligations, encrypted in transit and at rest where supported.
What we never do. SOMA never sells your Oura data, never uses it for advertising or marketing, and never shares it with advertising networks or data brokers.
5. How Oura data is and isn't combined
To produce an accurate daily training decision, SOMA may combine your authorized Oura data with other inputs you have connected — for example Apple Health (including Apple Watch) and your own training data (workouts, sets, reps, loads, and effort). Combining sources lets SOMA weigh the best available signal for your recovery read and recommendations.
This combination happens only to operate SOMA for you. Your Oura data is not cross-sold, not bundled into a profile for advertising, and not shared with third parties for their own purposes.
6. Your control — disconnecting
You can revoke SOMA's access to Oura at any time, in either of two ways:
- In SOMA: go to Settings → Integrations → Oura and tap Disconnect. This revokes SOMA's access token, so SOMA stops accessing your Oura data.
- In your Oura account: sign in at cloud.ouraring.com and remove SOMA under your account's connections. This revokes the authorization from Oura's side.
Disconnecting stops further data access immediately. It does not by itself delete data SOMA has already stored — to remove that, see §7.
7. Deleting Oura-derived data
To remove the Oura-derived data SOMA holds, delete your SOMA account and associated data:
- In-app: Settings → Account → Delete Account; or
- By email: message us at hello@somaintelligence.app from your account email.
On deletion, your SOMA account and associated server-side data are deleted, and integration access tokens (including Oura) are revoked. On-device data is removed when you delete the app or via the in-app delete. Verified requests are actioned promptly — within 30 days, and sooner where required by law. We may retain a minimal amount of data where required by law (for example, a record of your deletion request). Full details live on our Account Deletion page.
8. Compliance with Oura's terms
We access Oura data in line with Oura's API terms and developer policies. We request the minimum scopes needed, store only what is necessary, and use the data solely to provide SOMA's recovery and training features to you.
SOMA is an independent product and is not endorsed by, sponsored by, or affiliated with Oura. We do not use the Oura name or marks to imply any partnership or endorsement; we reference Oura only to describe this integration.
9. Contact
Questions about how SOMA handles your Oura data? Email us at hello@somaintelligence.app. You can also read our Privacy Policy and Data Usage & Privacy pages for the full picture.