Trust center
Plain statements about data, sharing, security, and limits. Nothing here claims more than the shipped system does.
Data collected and why
- Account email and a display name, to sign you in and label your records.
- Protocols, events, inventory, symptoms, and measurements you enter, to show them back to you.
- Device facts needed for reminder health: platform, app version, notification permission, exact-alarm state, time zone.
- Household membership and the sharing scopes you grant.
Not sold, no advertising SDKs
Your data is not sold. The apps contain no advertising SDKs. Diagnostic reports exclude substance or product names, doses, notes, symptoms, and a partner's identity.
Optional Vercel website analytics is off until you allow it. It counts public marketing page visits and reports device/browser type, approximate location and safe traffic sources. Account, sign-in and health-content pages are excluded, and page URLs are stripped of queries and fragments. You can turn it off using the controls below.
Notification limitations
Reminders are scheduled on your device. Operating systems can delay or drop notifications, iOS keeps a limited number pending, and Android may deliver late when exact alarms are not allowed. The app shows what it can verify and never says reminders are guaranteed.
Ownership, export, deletion
Each adult owns their records. Export (CSV and PDF) is available on every tier and is built on your device. Account deletion revokes sharing and sessions immediately and removes your records after a 24-hour window in which you can cancel.
Couple permissions
Two adults, two accounts. Every scope is a separate, explicit grant with its consequence explained, revocable at once. Nothing is shared because two people share a household.
Security practices actually implemented
- TLS in transit and provider encryption at rest.
- The on-device cache is an encrypted SQLCipher database keyed by a random secret held in the platform secure store; sign-out destroys both.
- Row-level security on every table and server-side authorization on every write; a generated test matrix checks each owner-scoped table.
- Administrator roles are held in a server-controlled table, never in user-editable metadata; MFA is required for administrator access.
- Pinned dependencies, secret scanning, and code review on every change.
DoseTide does not claim end-to-end encryption, HIPAA compliance, medical-device status, or clinical validation.
Incidents
Security incidents are assessed for notification obligations under a documented decision process, and affected people are told through the app and by email when required.
Content review
Educational entries are reviewed by a designated reviewer before publication and can be withdrawn immediately. See the evidence methodology page.
Limits
The app records and organizes what you enter. It does not prescribe, recommend doses, or evaluate whether a therapy is working.