Permission-led connected data
Connected data is requested through the relevant permission flow rather than assumed.
Understand BestBody’s approach to consent, connected-data permissions, provenance and responsible AI.
Connected data is requested through the relevant permission flow rather than assumed.
Users control optional connections and sharing choices available to them.
Provenance and timing help distinguish a user entry, connected record or derived output.
Published boundaries explain where AI assistance and general fitness guidance stop.
BestBody explains why information is used, keeps connected health permissions granular and preserves source and timing context where relevant. Users can choose whether to connect supported health platforms and can continue with manual records. Privacy, security and responsible AI are documented separately so the boundaries are inspectable.
Apple Health and Android Health Connect use category-level permissions. Review each requested category and the purpose it serves before agreeing. A permission can be declined when the related feature is not wanted, while manual logging remains available for supported records.
Individual health information should not become visible merely because someone joins a coaching or team experience. BestBody describes permissioned client visibility and aggregate team insight as distinct from unrestricted access to a person’s private records.
Review why BestBody requests particular account, health, activity or nutrition information before enabling it.
Connect only the supported services and data categories you want to use.
Read the privacy and security information or contact BestBody about access, correction, deletion or a suspected issue.
Register your interest and we’ll let you know when wider UK access opens.
We don’t sell personal health data. You control what is shared.