Product documentation · Connections & data
Nutrinaut Connections & Data Guide
Connect the right source, check what actually arrived, and understand the difference between a recorded observation and an app-generated insight.
Start with the route, not the watch brand
Nutrinaut brings available health signals, food and training logs, and optional lifestyle tags into one place. The source determines which observations can reach the app. Owning a watch does not mean every measurement it produces is shared with Nutrinaut.
- RecordYour device or source app records an observation.
- ShareApple Health, Health Connect or a Garmin connection makes permitted data available.
- Read & interpretNutrinaut reads available records and builds its own summaries.
Availability can vary by app version, operating system, device and permissions. This guide describes connection routes, not certification of every device or independent validation of its measurements. Use the current App Store listing or Google Play listing for installation requirements.
Choose your connection
Apple Health is the bridge
Use Nutrinaut’s Apple Health connection to request access to relevant categories. The implementation reads available sleep, activity and heart-related records; additional categories depend on what your sources provide and what you allow.
Check first: does the relevant record already appear in Apple Health, with the expected date and source?
Not a promise: connecting Apple Health does not create missing sleep stages, HRV or other measurements.
Share through Health Connect
Your source app must write the relevant category to Health Connect, and Nutrinaut must have permission to read it. Requested categories include sleep, steps, energy, heart rate, resting heart rate, HRV, oxygen saturation, VO₂ max and weight.
Check first: is the record present in Health Connect, and is access enabled for that category?
Not a promise: a watch or app supporting Health Connect does not necessarily share every category.
A separate account connection
Where your version offers Connect Garmin, sign in to Nutrinaut and complete the Garmin authorization flow. This is separate from granting Apple Health or Health Connect access. Available Garmin updates can contribute activity, heart-related and sleep fields.
Check first: has the device synced to Garmin, and did authorization finish in Nutrinaut?
Not a promise: an authorized account is not proof that new records or every metric have arrived.
Check the source app’s sharing
Use the manufacturer’s current sharing settings to see whether it supplies the required records to Apple Health or Health Connect. Check a real record in the bridge before assuming it will appear in Nutrinaut.
Check first: which categories are shared by this exact device, app version and platform?
Not a promise: a brand name alone is not a compatibility guarantee, and a phone connection is not a direct watch integration.
Apple explains how to inspect Health data sources and app access. Google describes Health Connect’s record types and permission-based sharing. Those platform capabilities do not establish which records your particular device exports.
Make the first sync understandable
- Confirm the original record. Open the watch’s source app. Check the observation you expect, not just the device’s connection icon.
- Confirm the bridge. For Apple Health or Health Connect, inspect the same category and date there. If it is missing, investigate the source app’s sharing before refreshing Nutrinaut.
- Grant the relevant access. Use Nutrinaut’s connection control and review the system permission request. On Android, background access is a separate permission where supported. Declining a category limits what can be read.
- Return and refresh. Let the source app finish syncing, then return to Nutrinaut. For Garmin, check the account connection rather than assuming Health-platform permission also connected Garmin.
- Verify one known observation. Compare a specific night, walk or recorded heart-rate value. A populated dashboard alone does not establish that every field is current.
You can use food and training logging without connecting a health source. Health-based insights then have less information. Do not repeatedly reconnect, erase records or reinstall as the first troubleshooting step; first find which stage is missing the expected observation.
Three times that should not be confused
| Time | Question it answers |
|---|---|
| Observation time | When did the sleep session, activity or measurement happen? |
| Import or sync time | When did that record arrive or get transferred? A record can arrive late. |
| Screen refresh time | When was the screen updated? This does not make the underlying observation new. |
These are checks to make across your source app, health platform and Nutrinaut; not every screen exposes every timestamp. If only an earlier sleep value is available, it is not evidence of last night’s sleep. The implementation includes optional last-known sleep handling and manual sleep records, so check the source and date instead of treating all displayed values as equivalent.
Companion-watch summaries can also be transferred from the phone. A recently transferred summary is not necessarily a newly measured health record. Read the wearable source checklist for missing-night and changed-source examples.
Why two numbers can still differ
Check the time window, units, source and definition before comparing. Daily activity totals are not the same as a single workout’s energy estimate. A manually entered sleep duration does not supply recorded sleep stages.
Even labels such as HRV can hide different definitions: the Apple Health reader requests SDNN, while the Android Health Connect reader requests RMSSD. Do not treat these as interchangeable measurements just because both are displayed in milliseconds. Likewise, a Nutrinaut summary is not necessarily the same formula as a watch manufacturer’s score.
Food, tags and insights: what to verify
- Food estimates: a photo or text analysis is a proposed entry, not a weighed meal. Check the food, portion, units, ingredients and final saved calories/macros. Entries can be edited. Use the meal-estimate review checklist.
- Tags: a tag records an event and its context. Record the event time and relevant details consistently. No tag is not proof that the event did not happen. See tags without confusing correlation and cause.
- Insights: separate imported observations, app calculations and generated advice. Check the inputs, period and missing information before following a suggestion. A confidence label or a precise-looking score is not a validated probability. Use the AI evidence checklist.
Nutrinaut does not diagnose illness, confirm recovery, clear an injury or establish whether training is medically safe. Do not use a favourable score to dismiss concerning symptoms. Seek an appropriately qualified professional for individual health decisions.
Permissions, privacy and support
You can change health-data access in Apple Health or Health Connect. For Garmin, use the connection controls offered in your app version and review the linked account’s permissions. Changing access is distinct from deleting records already held by a service. Consult the Privacy Policy for processing and data-rights information.
The public Nutrinaut Tools calculators are separate from the app’s health connections. They calculate from the values you enter in your browser; they do not connect to your wearable account or certify an app insight.
If a connection still fails, contact Nutrinaut with your phone model, operating-system version, Nutrinaut version, watch/source app, connection route and the missing category/date. Say where the record is visible and where it stops appearing. Start without an entire health export; crop or redact names, account details and unrelated health information from screenshots.
Documentation scope
This guide was checked against Nutrinaut’s iOS and Android connection and data-handling implementation, and the public store listings, on 10 October 2026. Source-code support is not a physical-device test or proof that every feature is present in every installed build. Menu labels and availability can change between releases.
Found a mismatch in your version? Send the version and affected step so the documentation can be corrected.