DoseRing Privacy Policy
Last updated: 15 November 2026
DoseRing is a medicine reminder app. It is built to keep your health information private. Almost everything DoseRing knows about you stays on your own phone. This page explains, in plain language, what is collected, what leaves your device, and how to erase it.
DoseRing is not a medical device
DoseRing is a reminder and record-keeping tool only. It does not diagnose, treat, cure, or prevent any disease or medical condition, and it is not a substitute for professional medical advice. Always follow the instructions of your doctor or pharmacist. Do not change how you take a medicine based on anything in the app. If you think you have a medical emergency, contact your local emergency services.
What is stored on your device
When you use DoseRing as a patient, the app stores the following locally on your phone, in its private app storage:
- Medicine details — the names you enter, dosages, and any instructions or notes.
- Schedules — the times and intervals at which each medicine is due, and reminder settings such as sound and snooze.
- Dose events — a record of each reminder and whether you marked the dose as taken, skipped, or missed, with the date and time it happened.
This information is the heart of the app. It is kept on your device so that reminders, history, streaks, and adherence figures all work with no internet connection. It is never uploaded to our servers for advertising, analytics, or profiling. If no caregiver is linked (see below), none of it is sent to DoseRing's servers, and the app does not contact them at all. The only other way it can leave your phone is through Android's own phone backup, if you have backup turned on (see Android phone backup below).
What syncs to the server when a caregiver is linked
DoseRing lets a patient link a trusted caregiver so that the caregiver can see whether doses were taken, skipped, or missed. Linking is optional and is started by the patient, who must approve each caregiver.
Caregiver sync runs on Google Firebase (Firebase Authentication, Cloud Firestore and Cloud Functions). The data is stored in Mumbai, India. When, and only when, the patient has approved a caregiver, DoseRing sends adherence events to Firebase. An adherence event contains:
- the status of a dose — taken, skipped, or missed;
- the date and time the dose was due and when it was marked;
- a random code for each medicine, so doses of the same medicine can be grouped. It is not made from the medicine's name;
- identifiers that connect the event to your anonymous patient identity (see below).
When you approve a caregiver, your earlier dose history (the same status and times, nothing more) is sent too, so the caregiver sees the full picture and not only doses from that day on.
While an approved link is active, the patient's phone also sends a status record: the time of the last sync, the latest day with a dose, and the DoseRing app version. This lets the caregiver see when the phone last checked in.
When a caregiver enters a pairing code, the name they give their own phone (free text the caregiver types) is also stored with the link, so the patient can see who is asking to connect. Pairing codes are six digits, expire after 10 minutes, and are removed from the server within a day.
Medicine names, dosages, instructions, notes and your name are never sent to the server. The server's security rules reject any other field, so the caregiver sees that a dose was taken or missed and when — not what the medicine was. Sync is one-directional and additive: it reports events that already happened on the patient's device. A sync failure never deletes anything from your phone.
Either side can end the link at any time. When the patient no longer has an approved caregiver, nothing more is sent, and anything still waiting to be sent is discarded. Events that were already shared stay on the server until you delete your online data (see How to delete your data). If you approve a caregiver again later, doses recorded in the meantime are shared then, the same way as for a first link.
The caregiver's phone stores the adherence events it receives so the caregiver can see them offline. Like any app data, that copy is included in the caregiver phone's Android backup if backup is turned on there.
If you used caregiver sharing in version 1.0
Before version 1.1, caregiver sync ran on a different provider, Supabase. Nothing is sent to Supabase any more. If your phone still holds old data there, DoseRing deletes it automatically after you update: when you pair with a caregiver again, after 14 days, or straight away when you use “Delete my DoseRing online data”. We will close the old Supabase project, and delete everything left in it, once version 1.1 has reached everyone.
Android phone backup
If backup is turned on in your phone's settings, Android's built-in backup saves a copy of DoseRing's data to your Google account. This includes medicine names, dosages, schedules, and dose history. It exists so that nothing is lost if you replace, reset, or reinstall your phone.
This backup is created and stored by Google under your account, not by DoseRing. DoseRing cannot access it. On Android 9 or newer, if your phone has a screen lock (PIN, pattern or password), Google encrypts the backup end-to-end using that screen lock. On other devices the backup is protected by your Google Account. DoseRing cannot read these backups.
Your anonymous sign-in for caregiver sync, the subscription cache, and this phone's reminder setup are left out of the backup. Those belong to one specific phone. On a restored phone, DoseRing asks you to set up reminders again, and if a caregiver was linked, it prompts you to reconnect. Your “Send crash reports” choice is backed up, so it follows you to a new phone.
You can turn backup off, or delete an existing backup, in your phone's Settings → Google → Backup (the exact menu names vary by phone maker).
Authentication — no name, email, or phone number
DoseRing has no accounts to sign up for and never asks for an email address, phone number, or your name. To make caregiver sync possible, the app creates an anonymous Firebase user ID, but only when you start pairing with a caregiver (sharing or entering a code). It is a random identifier for your installation, not tied to your real-world identity.
If you never use the caregiver feature, no identity is created and DoseRing never contacts its caregiver-sync servers.
When caregiver sync runs, the app also asks Google Play to confirm that it is the genuine DoseRing app (Firebase App Check with Play Integrity). This protects the server from fake clients. DoseRing sends no personal data for this check.
Crash reporting (Firebase Crashlytics)
To find and fix bugs that would otherwise cause the app — and your reminders — to fail, DoseRing uses Firebase Crashlytics, a service provided by Google. When the app crashes or hits a serious error, a crash report is sent. A crash report typically contains:
- the type of error and the technical stack trace showing where in the code it occurred;
- the device model, operating-system version, and DoseRing app version;
- coarse device state at the time, such as available memory and whether the screen was on;
- the date and time of the crash and a random, app-generated installation identifier used to group reports from the same install.
DoseRing does not add your medicine names, schedules or dose history to crash reports. They are used only to diagnose stability problems. Crash data is processed by Google as described in the Firebase privacy documentation and the Google Privacy Policy, and is retained by that service on a rolling basis (Crashlytics keeps crash reports for up to 90 days).
Crash reporting is on by default. You can switch it off at any time in Settings → “Send crash reports”.
Subscriptions (DoseRing Plus)
DoseRing Plus is bought through Google Play. DoseRing uses RevenueCat to check whether your subscription is active. When the app starts, RevenueCat receives a random, anonymous app user ID, so it can tell whether this install has Plus. If you subscribe or restore a purchase, RevenueCat and Google Play also receive your purchase history for DoseRing. Payment is handled by Google Play; DoseRing never sees your card details. Purchases are restored through your Google Play account.
What DoseRing does not do
- No advertising, and no advertising identifiers.
- No selling or renting of your data to anyone.
- No third-party analytics or tracking SDKs. The only third-party SDKs are the crash reporting described above and RevenueCat for subscriptions, which checks entitlements and is not an analytics service.
- No access to your contacts, photos, location, or files.
DoseRing's service providers (Google Firebase for caregiver sync and crash reports, RevenueCat for subscriptions, and Google Play for purchases) process data only to run the app, and receive normal network metadata such as your IP address. We do not share your data with anyone else.
How to delete your data
Step-by-step instructions are on the Delete your DoseRing data page.
In the app, Settings → “Delete my DoseRing online data” deletes at once everything stored online for your phone, whether you are a patient or a caregiver:
- the dose history that was shared with caregivers;
- your status record;
- your caregiver links and any pairing codes;
- the anonymous Firebase account itself;
- old data from version 1.0 on Supabase, if your phone still has it.
It does not delete the medicines, schedules, or dose history on your phone. Those stay until you clear DoseRing's storage in your phone's settings or uninstall the app; either one removes all data DoseRing has stored on your device.
Uninstalling or clearing storage does not delete your online data. Afterwards, the app can no longer prove which online data is yours. If you shared doses with a caregiver, use “Delete my DoseRing online data” first. If it is too late for that, see Delete your DoseRing data.
Neither option deletes a copy already saved in your Android phone backup, because that backup is held by Google in your account. Delete it from your phone's backup settings as described in Android phone backup. Crash reports already sent to Firebase Crashlytics age out of that service on the rolling schedule noted above; to request earlier deletion of crash data, contact us at the address below.
Data retention
Data on your device is kept until you clear DoseRing's storage or uninstall the app. On the server, the dose history shared with caregivers and your status record are kept until you use “Delete my DoseRing online data”. Ending a caregiver link stops new sharing but does not delete what was already shared. The caregiver's phone name is stored with the link and is deleted when the link ends or when you delete your online data.
Anonymous accounts that have not been used for 90 days, and have no caregiver link and no shared dose history, are deleted automatically together with anything left over. Pairing codes expire after 10 minutes.
Crash reports follow Firebase Crashlytics' retention period. Purchase records are kept by RevenueCat and Google Play under their own policies. A copy in your Android phone backup, if you use it, is kept by Google according to your Google account's backup settings.
Children's privacy
DoseRing is intended for use by adults managing their own or a family member's medication. It is not directed to children, and we do not knowingly collect personal information from children.
Changes to this policy
If this policy changes, the updated version will be posted on this page with a new "last updated" date. Significant changes will also be communicated through the app where practical.
Contact
Questions about this policy or about your data can be sent to support@amginnovationhq.com.