Last updated: October 10, 2026
Scope and eligibility
DoseBuilt LLC provides the DoseBuilt TestFlight beta to invited adults age 18 and older in the United States. This notice covers beta accounts, fitness tracking, optional backups, enabled AI features and Sandbox membership testing. Some features may be unavailable while testing is configured. Beta data processing is real even when a test purchase is free.
Create account uses an unchecked “I’m 18 or older” declaration. We keep the declaration, eligibility category, source, policy version and access state. The checkbox is not identity verification and does not override an existing restriction. Supported Apple age and permission signals may require additional checks. No birth date is collected by that checkbox.
Accounts and fitness data
Supabase processes your email, authentication information, account identifiers and sessions. Resend delivers configured account messages. Your workouts, food, water, weight, saved foods, goals and training/nutrition settings are saved on your device first. Nutrition-profile inputs can include age, height, energy-equation sex and activity level. Signing in creates a separate local workspace for your DoseBuilt account and does not automatically copy or upload guest logs.
Cloud upload is optional. Automatic upload is off until you explicitly agree for the signed-in account on that device. If enabled, the app sends that account’s existing manually logged fitness records and later saved changes to DoseBuilt’s Supabase-hosted database while the app is open and connected. Uploads include routines, unfinished workouts, custom exercises, saved meals, nutrition targets and any nutrition-planning profile you entered. Food entries you review and explicitly add to your diary may be included even when an AI estimate helped you prepare them. You can also upload a backup manually.
Coach conversations, raw AI requests and responses, meal photos, sign-in credentials and payment information are excluded from fitness uploads. Appearance, workout sounds and local rest-alert preferences stay on that device. Optional product push preferences and device registrations are stored separately with your DoseBuilt account as described below. Workout photo files are not included in cloud backups.
The service keeps up to five cloud backup versions under your account’s access controls. Cloud backups are not end-to-end encrypted. Uploads do not automatically merge or restore records from different devices. When another device has changed the cloud data, uploads pause for review. A full backup restore replaces the current workspace’s fitness records after review and turns automatic upload off until you enable it again. Import data pauses automatic upload during replacement, then follows your existing setting. If automatic upload was already enabled, imported records can be included in later uploads.
You can turn automatic upload off in Account → Data → Account & cloud. This stops future automatic uploads; a request already sent cannot be recalled. Turning it off does not remove existing cloud versions. If a connection fails, locally saved changes remain on your device and uploads can resume while the app is open and connected. Uploads are not guaranteed while the app is closed or suspended. Before uninstalling or changing devices, confirm an upload or export a backup. Exported files contain unencrypted fitness information, so choose their destination carefully.
Optional product push notifications
You can optionally choose to receive DoseBuilt product launches and offers at signup or in Account → Sounds & notifications. The signup checkbox starts unchecked, and your choice is saved after account verification. Membership is not required. This choice is separate from email preferences, device notification permission and local rest alerts. DoseBuilt stores your preference and consent history with your account in its Supabase-hosted database, including the consent wording version, signup or settings source and timestamps. Registering a device also stores its Expo push token, installation identifier, platform, registration version and account-session association. These records support your notification choices and delivery; fitness logs are not used for these messages. Campaign sending is currently disabled. If enabled later, delivery will use Expo and Apple or Google push services. You can withdraw consent in Account → Sounds & notifications. Once the server confirms withdrawal, DoseBuilt disables your account’s device registrations and clears their push tokens. If withdrawal is pending, reconnect and retry; you can also block notifications in device Settings. A message already handed to a delivery provider cannot be recalled.
Optional AI sharing
AI Coach, Scan meal and Describe food send information you choose to submit through DoseBuilt to OpenAI to provide personalized AI coaching or meal estimates. AI sharing is optional and separate from buying or restoring a subscription. Payment, membership, reading this notice and choosing a photo do not grant AI sharing permission.
In app versions with the “AI sharing agreement” in Membership, one unchecked agreement covers Coach messages and optional fitness context, plus food photos and descriptions you choose to submit. Until you explicitly agree, these AI tools remain locked; manual logging, barcode lookup, charts and local log insights remain available. For a new purchase or restore, a checked agreement is saved only after active membership is verified. Existing active members can review and save it in Membership without purchasing again. An earlier Coach-only or per-meal choice is not converted into this broader permission. Earlier app versions may continue to ask for their narrower Coach or individual meal permission.
After you agree, Coach sends the message you choose to submit. Up to three recent complete question-and-answer pairs and derived fitness summaries start on unless you previously turned either context option off. Previous explicit opt-outs are kept. In weight-trend builds, automatic summaries use your manually logged workouts and weight and may include weight-change trends, weigh-in coverage, the age of the latest weigh-in, whether the starting weight boundary was recorded, weight-trend review status, and workout performance. Your selected weight goal and requested weekly weight-change rate may be sent to DoseBuilt to validate the summary, but are excluded from automatic context sent to OpenAI. Automatic summaries in weight-trend builds exclude calorie targets, recorded intake and food-log coverage. Earlier installed builds may still send goals, calorie targets, intake and log coverage to DoseBuilt; some earlier versions also include these in context sent to OpenAI under their existing sharing controls. Your message and included conversation can still contain information you choose to share. You can turn either context option off in Coach. Earlier conversation may contain details you previously shared; turning off new summaries does not remove those details from included conversation.
Scan meal and Describe food send the description and any food photo you explicitly submit for that estimate. They do not send your Coach conversation or fitness history. Photos are prepared as resized JPEGs; selecting a photo alone does not submit it. Meal photos are not added to the diary or fitness backups. Temporary device copies are not promised immediate erasure. You review and confirm the estimated foods before they are saved to your diary, where they follow your fitness-backup choices.
The saved agreement and explicit context choices apply to this DoseBuilt account on this device or browser, not automatically to your other devices. Review or remove permission in Account → DoseBuilt membership → Manage Your Membership → AI privacy. Removing the unified agreement blocks new Coach and food AI requests on that device and cancels pending work in the app. A request already dispatched may still be processed; information already sent cannot be recalled. Removing permission does not delete existing diary entries or data already held by a provider. To withdraw on another device, remove permission there too. If the app cannot save the removal, it blocks AI in the current session and asks you to retry before closing.
Relevant changes to eligibility, recipients, purpose or the scope of sharing can require a new explicit agreement. Consent is stored on the device separately from fitness backups. The AI handlers do not create stored server conversations or save meal photos. Coach conversations remain temporary, are excluded from fitness backups and are cleared on a full app restart or relevant account or context changes. Switching tabs or briefly backgrounding the app does not necessarily clear a conversation. Automatic Coach context excludes meal photos, raw workout notes, receipts and account credentials. Coach cannot change your logs or targets. Provider retention and deletion limits are described under “Retention deletion and choices” below.
Do not submit credentials, identity documents, photos of other people or unnecessary identifying information to AI. AI estimates and replies can be inaccurate; review the result and use your judgment.
Food references
Live food searches and barcode lookups send the search text or barcode to Open Food Facts. Barcode camera frames stay on-device. Remote food images contact their hosts; network providers receive connection information such as IP addresses.
Apple receipts membership and diagnostics
When you explicitly connect Apple app or Sandbox purchase eligibility, signed receipt information is sent to DoseBuilt for verification and account/environment binding. A receipt does not prove your age. Apple and RevenueCat process subscription and transaction information; RevenueCat receives your DoseBuilt account identifier to verify and restore access. DoseBuilt’s app integration does not receive full payment-card details.
Apple automatically collects TestFlight crash and usage information and shares it with DoseBuilt; it may include device, build, session and tester information. Feedback you submit may include screenshots and identifying details. We use this information to investigate problems and improve the beta. Apple describes these practices at https://www.apple.com/legal/privacy/data/en/test-flight/.
Retention deletion and choices
OpenAI requests disable saved response storage, but the project uses Global residency and Standard Retention, not Zero Data Retention. OpenAI documents default abuse-monitoring retention of up to 30 days, with legal and protection-from-harm exceptions and endpoint-specific controls. US-only beta availability does not mean US-only processing. See https://developers.openai.com/api/docs/guides/your-data.
Account information and live cloud fitness versions remain until account deletion, subject to the service’s limit of up to five backup versions. Account deletion requires confirmation; after successful server deletion, live account backups are removed. You can separately choose to remove that account’s device copy. Guest logs, exported files and separate Shopify accounts, carts and orders need their own handling. Turning off cloud upload does not delete existing cloud versions. Deleting your DoseBuilt account or the app does not cancel a separate real Apple subscription or request a refund; manage or cancel any such subscription through Apple. The provider-retention limitations below still apply.
Turning off product push notifications does not erase the consent history or all registration metadata. These records are retained to record your choice and prevent delayed requests from restoring a revoked registration. Successful account deletion removes account-linked push preferences, consent history, device registrations and any delivery records from DoseBuilt’s live database. No fixed automatic deletion period is currently configured for consent history or delivery records. Infrastructure backups and provider-held records remain subject to the separate retention limitations described below.
Usage records hold transformed billing/account references, request IDs, counts, periods, outcomes and timestamps, not prompts, photos or fitness records. They can remain linked and survive account deletion. New-version records become eligible for cleanup 48 hours after their original UTC month ends, but cleanup is not scheduled or automatic; legacy records remain protected. This is not a deletion deadline. Apple revocation references, infrastructure logs/backups, support correspondence and provider-held records have separate handling; deleting a live account does not erase every copy.
You can decline AI or cloud backups, control optional context and device permissions, export local records, and request access, correction or deletion at support@dosebuilt.co. Depending on applicable law, you may have additional privacy rights, including an appeal of a request decision. We may verify your identity and apply lawful exceptions. Contact us to request review or ask about retained records. No transmission or storage system can be guaranteed completely secure.
Other DoseBuilt services and contact
Website cookies, shopping and store support are covered by https://dosebuilt.co/policies/privacy-policy. The closed guardian-verification Test has its separate historical notice at https://dosebuilt.co/pages/guardian-verification-test-privacy; this adult beta does not reopen it. Material changes to this notice will be identified by an updated date and any additional notice or consent required by law.
Contact DoseBuilt LLC at support@dosebuilt.co or 8735 Dunwoody Place #10328, Atlanta, GA 30350, United States.