Who operates Natively
Natively is operated by Samuel Stout, a sole proprietor. Questions about this policy can be sent to sam@natively.co.
Information handled by the app
Natively account
Natively requires Sign in with Apple before you create a durable weigh-in. Apple and Natively’s authentication provider, Supabase, process the account identifier, authentication tokens, and identity claims Apple supplies to create and maintain your account. Natively does not request your Apple name or email address as separate sign-in scopes.
Weight and related app data
Natively stores weight measurements you deliberately create in the app, their dates and times, whether a measurement is included in the trend, goal or intent history, coaching history, and information needed to calculate and display your recent trend. This Natively-owned information is stored in your Natively account using Supabase and in a local-first copy on your iPhone so the app can continue to work during temporary network interruptions.
The app also stores preferences such as your display unit and daily reminder setting. Some approved preferences sync with your Natively account. Device-specific information—including Apple Health permissions, Health synchronization cursors, local Apple Health links, and records used to prevent a removed external Health measurement from being imported again—remains on that device.
Apple Health
Apple Health integration is optional. If you choose to connect it, Natively requests permission to read and write body-mass measurements only. Natively reads the body-mass history that Apple Health makes available to the app. When write permission is granted, Natively saves measurements you enter in the app to Apple Health.
Body-mass measurements created by other apps and read from Apple Health remain device-local in this version of Natively and are not automatically copied into your Natively account. Natively-created measurements are durable Natively account data even when a corresponding copy is also written to Apple Health.
Natively does not edit or delete body-mass measurements created by another app. Removing one of those measurements from Natively hides it locally and does not remove it from Apple Health. When you edit or delete a measurement that Natively created in Apple Health, Natively may update or delete its own corresponding Apple Health sample.
Apple controls Apple Health permissions and any synchronization of Health data through its services. You can review or change Natively’s Health access in iOS settings. Apple’s handling of Health information is governed by Apple’s policies and your device settings.
Notifications
If you enable the daily weigh-in reminder, Natively asks for notification permission and schedules the reminder locally on your iPhone. The reminder preference may sync with your Natively account, but notification authorization and delivery are controlled on each device. Notifications are optional and can be disabled in Natively or iOS settings.
AI coaching
AI-written coaching is a standard part of Natively. Before coaching begins, Natively asks you to acknowledge a concise disclosure about this processing. Natively first calculates supported trends, variability, persistence, goal context, confidence, and candidate insights deterministically. A bounded snapshot of that evidence, your current goal context, and summaries of up to three recent coaching responses is then processed through a Supabase Edge Function and sent to OpenAI to write the response. Natively does not send your full Apple Health history, Health source-app identity, email address, or authentication tokens to OpenAI.
The model is not permitted to invent calculations, causal explanations, or unsupported claims. Natively validates the response before storing it in your coaching history. If remote generation is unavailable or validation fails, Natively uses deterministic coaching created on your iPhone.
Subscriptions
Natively uses Apple StoreKit to offer monthly and annual subscriptions. Apple processes purchases and payment information. Natively receives StoreKit information needed to determine access, such as the product identifier, verification status, expiration date, and revocation status. Natively does not receive your full payment card details. Apple’s handling of purchase information is governed by Apple’s Privacy Policy.
Where app information goes
Supabase provides Natively’s authentication, database, synchronization, and server-function infrastructure. It stores Natively-owned account data and processes requests needed to provide those features. Supabase is not used to store body-mass measurements imported from other Health apps.
For daily coaching, OpenAI processes the bounded coaching context described above. Natively requests generation with response storage disabled. OpenAI states that API data is not used to train its models by default; under OpenAI’s standard data controls, content may be retained in abuse-monitoring logs for up to 30 days.
Information may also leave the device when you write a measurement to Apple Health, use Apple’s Health synchronization or device backup services, make an App Store purchase, or share a data export with a destination you choose.
The app contains no advertising, behavioral tracking, general analytics, or session replay. Natively does not sell personal information or use wellness information for advertising.
Exporting and deleting app data
You can create a versioned JSON export from Natively’s settings. Natively first attempts to synchronize the account and then prepares the export from the freshest local account projection available. If the device is offline, the export can still be created from its local-first copy. Any device-local Apple Health projections included in the export are identified separately from Natively-owned account data. The export is created in temporary app storage and presented through the iOS share sheet. A copy sent to another app or service is then controlled by you and that recipient.
“Erase Local Data” removes Natively’s local app data from that iPhone. It does not delete your Natively account, cloud data, or measurements stored in Apple Health. Deleting the app similarly does not delete your Natively account, Apple Health data, or cancel an Apple subscription.
“Delete Natively Account” permanently deletes your Natively account and its active Natively-owned cloud data, then removes that account’s local app data from the iPhone after the remote deletion succeeds. Account deletion does not delete Apple Health samples. Natively provides a separate, explicitly confirmed action that deletes only body-mass measurements written to Apple Health by Natively; it never deletes samples owned by other apps.
You can also review or revoke Natively’s Sign in with Apple connection in your Apple Account settings and manage or cancel subscriptions through Apple.
Website information
Natively.co does not include contact forms, user accounts, advertising, analytics scripts, tracking pixels, or browser storage. The site does not set its own cookies.
The website is delivered through Cloudflare’s ordinary hosting, caching, DNS, and security services. When you visit, Cloudflare processes technical information needed to deliver and protect the site. This may include your IP address, request details, browser and device information, timestamps, security signals, and network error reports. This technical information is handled by Cloudflare under its Privacy Policy. Natively does not use Cloudflare Web Analytics or a separate visitor analytics product.
Retention and security
Active Natively account data is retained until you delete individual information or your account. Coaching generation request metadata is retained for up to seven days and does not contain the coaching context. Superseded coaching artifact revisions are marked for deletion after 30 days and permanently removed after an additional 30-day synchronization window. Synchronization tombstones are retained for 30 days so devices that were temporarily offline can observe deletions.
Rejected model output and raw model responses are not kept as coaching history. Provider security, abuse-prevention, operational log, and backup copies may remain for their applicable retention periods after active data is deleted. OpenAI’s standard abuse-monitoring retention is described above. Supabase backup and platform-log retention varies by the service plan and recovery needs.
Natively uses access controls, row-level database security, encrypted network connections, iOS app isolation, Apple’s data-protection features, protected temporary export storage, and server-managed secrets. No method of storage or transmission is completely secure.
Changes to this policy
This policy may be updated if Natively’s features or information practices change. The effective date at the top will be revised when an update is published.
Contact
For privacy questions, contact Samuel Stout at sam@natively.co.