Your data is yours.

Dosely is a GLP-1 and peptide tracker made by Tiny Software, LLC ("Dosely", "we", "us"). This policy covers the iPhone app, your Dosely Account, the Account website, and getdosely.app. It explains the personal and health information we handle to provide tracking, progress displays, Account access, and optional Dosely Intelligence. Dosely is for adults, and does not provide medical advice.

You can sign in with email or Sign in with Apple through Logto, our identity provider. Sign-in and recovery involve your verified email, linked login identifiers, and verification information. Dosely associates an internal Account identifier with that identity and keeps your display name, setup-completion status, display preferences, revocable device Sessions, and access status. An Apple login and an App Store purchase are separate associations, not your Account identifier.

We use this information to authenticate you, protect Account access, recover access, and connect purchases or complimentary access to your Account. Account pages use session cookies; the iPhone app uses a device Session credential. These are separate from optional analytics and from your health records.

Dosely stores Account records in Dosely-hosted Postgres. This is the authoritative cloud copy, not iCloud or CloudKit. The iPhone app also keeps an on-device database, including an offline replica of supported Account records and pending changes that synchronize when connected. Records that have not been migrated or are not supported by that app version can remain local. The Account website is online-only; it does not provide the iPhone's offline replica.

Account records include Protocols (the medications or compounds, schedules, and amounts you record), logged Doses (amount, unit, date, route, injection site, notes, and pain rating), custom compounds and Blends, Inventory (including recorded vial volume, draw-device details, notes, and usage or adjustments), day notes, side effects and severity, and Health measurements. We store the record identifiers, dates, revisions, and sync information needed to show your records and reconcile changes. You choose what to record; Dosely does not verify your entries or recommend a dose.

The six cloud Health categories are weight (WEIGHT), body fat percentage (BODY_FAT), lean body mass (LEAN_MASS), waist circumference (WAIST), resting heart rate (RESTING_HEART_RATE), and blood pressure, including systolic and diastolic readings (BLOOD_PRESSURE). Health records include a measurement, unit, time, and provenance. Entries you create manually are marked MANUAL. Consented Apple Health copies are marked HEALTHKIT and retain their sample identifier and source name; they are read-only copies, not manual entries.

Existing local records and historical imports are not permission for a new upload. Native-to-cloud Account migration and Apple Health upload are separate paths. Unknown historical origins stay unknown; importing or displaying a value does not make it a manual entry or authorize cloud processing. User-facing file import and Protocol-link or paste import are not supported.

Onboarding interests also stay local and are not Intelligence inputs.

With your iPhone permission, Dosely reads weight, height, body fat, lean body mass, waist circumference, resting heart rate, and blood pressure from Apple Health. Dosely does not write to Apple Health. Height is not one of the six cloud Health categories and HealthKit-derived height is not uploaded.

Apple's permission to read on your iPhone is not consent to upload. Uploading HealthKit measurements to your Dosely Account requires a separate grant for each cloud Health category. These choices belong to your Account and can be recognized across Sessions. We keep category consent receipts with a status, timestamp, and increasing receipt version; that version records successive choices, not a blanket privacy-policy approval.

You can withdraw a category's cloud consent from the Health controls. Withdrawal stops new uploads and removes that category's HealthKit copies from active cloud records; manual records and your original Apple Health samples remain. Pausing uploads keeps existing copies. Purging copies without withdrawing leaves the grant in place, so later permitted sync may upload again. Removing an individual HealthKit reading suppresses its sample from re-upload until you explicitly reverse that removal, even if you re-grant the category.

Turning off a local metric or revoking Apple's read permission stops future reads; it does not by itself delete copies already in Dosely. Cloud changes need a connection and successful synchronization. Use the cloud withdrawal controls to remove uploaded copies, and Apple's Health settings to change device permissions. Cloud Health consent does not turn on Intelligence sharing.

Dosely Intelligence v1 is Protocol Review only: educational compound information and review of logged-protocol inconsistencies, never individualized dosing or treatment advice. If you use it, your messages and relevant context are processed by Dosely's API and Anthropic, our AI processor, to generate a response. AI responses may be wrong.

Account Intelligence requires a separate consent grant under Intelligence terms version 1. You choose the optional context categories: PROTOCOL (compound labels and schedules), DOSE_HISTORY (up to 14 recent logged Doses, with label, amount, unit, and date), and HEALTH_RECORDS (up to 8 recent cloud Health measurements, with metric, value, unit, and date). A category you do not grant is left out of newly assembled context. Completed messages in the conversation, including previous responses, are sent with your new request, together with educational catalog material and the selected context.

The context assembler does not send your onboarding interests, Inventory, journal entries, dose notes, injection sites, saved memories, email, login identifiers, or billing details to Anthropic. Anything you type into a message can still contain personal or health information, and earlier conversation messages may contain previously shared context. Avoid including information you do not want processed by the AI provider.

Account Intelligence stores conversations, messages, responses, saved memories, and source-record references in the Account cloud. Selected Health context is projected from source records rather than copied into a separate Intelligence health table. Earlier app versions may use the legacy relay, which does not persist chat text or request context in Dosely's chat service; that does not change Anthropic's processing or the storage of Account records.

You can change Intelligence categories or withdraw Intelligence consent in its privacy controls. Withdrawal blocks new generation; it does not erase existing conversations or recall requests already sent to Anthropic. You can delete conversations and saved memories separately. Anthropic handles API inputs and outputs under its API data-retention terms, including safety and legal exceptions, and does not train on API data by default. We do not promise zero retention or immediate deletion at Anthropic.

Apple processes App Store purchases and Stripe processes website checkout. Dosely keeps purchase and subscription identifiers, status, paid-through dates, and transaction or event records needed to verify access, reconcile payments, and handle restore requests. We do not store your full card number. No health logs are sent as payment metadata.

Complimentary Access is an expiring administrative exception for an existing Account, separate from a purchase, subscription, public free plan, or trial. We keep its issue, expiry, revocation, and administrative audit information to determine access. It does not cancel an existing paid subscription or its renewal.

The iPhone app sends usage events to self-hosted OpenPanel analytics: app launches, tab views, dose and weight logging, Health sync completion; onboarding start, Protocol configuration, and completion; compound-chart views; Intelligence chat starts and completed responses; paywall views and subscriptions; schedule creation; and doses logged through reminders.

Schedule-created events include the catalog compound identifier. Dose-logged events for catalog compounds include the compound identifier, amount, unit, and route when known. Custom-compound dose events send only the event name; edits do not send a new dose event. Dosely's backend also stores accepted catalog-dose events in a separate analytics table, with the compound, amount, unit, route, source event identifier, event time, and ingestion time. These event payloads do not include weight values, notes, injection sites, or Account identifiers; other usage events carry only their event name.

Usage analytics and crash reporting have separate switches under Account → Usage & crash reports. Turning off usage sharing stops future usage events, including compound and dose payloads; it does not erase events already sent or disable Account sync, Intelligence, or service operational logs. Crash-report sharing is separate and takes effect when the app restarts. Crash and error reports include technical information such as stack traces and device model, not the contents of your health logs. These app services are self-hosted.

Our services also process technical request and session information for security and operations. Account sync and Intelligence require your Account and are separate from usage analytics. Provider error details may appear in operational logs and can include message or health information echoed by the provider. If you email support, we receive your email address and whatever you include. Please avoid sending health records or payment credentials unless needed to resolve your request.

getdosely.app uses self-hosted analytics and Google Analytics to understand visits, traffic sources, and useful pages. These services may process your IP address, browser and device details, referring page, pages viewed, interactions, and analytics identifiers or cookies. We do not send your Dosely health logs to website analytics. Hosting services may keep standard server logs for security and operations.

We do not sell your data, show ads, or share health information with advertisers, data brokers, insurers, or employers. We do not use your health logs to train AI models, build marketing profiles, or commercialize cross-user health patterns. This policy does not authorize future aggregate-data products. Identity, hosting, payment, and optional AI services process the information needed for their stated functions.

We retain active Account records to provide the service until you remove them or delete your Account. Deleting an entry removes the active record; sync change history, deletion markers, retry records, and consent history can remain to reconcile devices and prevent stale data from returning. Account Intelligence history remains until you delete the conversation or Account; withdrawing consent alone is not deletion.

Request Account deletion in Account settings after verifying your recovery email. The request revokes all Sessions and blocks private reads and sync immediately. The requesting iPhone clears its Account-owned data; other devices clear theirs when they next contact Dosely and learn of deletion. An offline device cannot be remotely erased immediately. Ordinary sign-in does not recover a deleted Account. Within seven days, verify your email and explicitly choose Keep my Account to recover it.

After that seven-day window, the deletion process purges the working Account and associated records, including health records, journal, Inventory, Intelligence, and sync records. A deletion-status record and purchase or payment records can remain for deletion enforcement and billing reconciliation or purchase recovery. Account purge is not a promise to erase records independently held by Logto, Apple, Stripe, or Anthropic.

Backups are separate from the active database. Removed data may remain in backups until those backups expire; deletion is not an immediate erase of every backup copy. We do not promise a fixed backup or provider retention period here. Support correspondence and operational records may also remain separately from your Account. Contact us about a specific retention or deletion request.

Uninstalling removes the app's local data, not your cloud Account or subscription. Signing out is not Account deletion. Account deletion does not cancel App Store or website billing, and does not alter your Apple Health samples. Cancel renewal through the service where you purchased before deleting your Account. Manage any Apple device backups separately in your Apple settings.

On iPhone, Settings → Export Data offers JSON, CSV, and PDF copies of the records available to that app. The Account website offers a JSON download of supported live Account records, assembled from pages read while the export runs, not a single immutable snapshot. The current web export does not include Intelligence transcripts; CSV and PDF are iPhone formats, not web formats. Export is a records copy, not a full backup, restore, or supported re-import. Keep exported health information secure.

Depending on where you live, you may have rights to access, correct, delete, or obtain a copy of personal and health data, or withdraw consent. Those requests can cover Account and cloud health records, not just support and analytics. Email [email protected] to make a privacy request or ask about a missing export record. We may need to verify your identity and will respond as required by applicable law, explaining any lawful limits. Please do not send passwords or verification codes.

Dosely is intended for adults 18 and older, not children. We do not knowingly collect children's personal information. Contact us if you believe a child has provided information so we can address it.

If this policy changes, we will update this page and its effective date. Material changes will be called out in the app or on this site. Agreeing to terms or reading this policy does not grant optional HealthKit cloud or Intelligence consent.