This policy explains how DoseMate handles information in the Android app and on this website. Your medicine photos, reminder details, schedules, and dose history are stored on your device for the app's reminder features. They are not sent to DoseMate's advertising providers. The app does use third-party advertising services, which process device, network, consent, and ad-interaction information as described below.
Who Is Responsible and How to Contact Us
DoseMate is provided by the developer identified on its Google Play listing. For privacy questions or requests, email Lovedesiree593@gmail.com.
Information We Handle
| Category | Examples and source | Purpose and processing |
|---|---|---|
| Reminder content | Medicine photos, dose labels, reminder times, repeat schedules, reminder status, and dose history that you enter or choose. | Stored and processed in the app's private storage to create reminders, display alerts, and generate reports. DoseMate does not upload this content to its advertising providers. |
| Device and network information | Advertising ID, app-set or similar identifiers, IP address, device type, operating system, language, network state, and general location inferred from IP address. | Processed by AppLovin and Google for ad delivery, mediation, measurement, personalization where permitted, security, and fraud prevention. |
| App and ad activity | App launches, screens viewed, onboarding progress, feature actions, permission choices, reminder and dose action results, report creation and sharing actions, ad requests, ad format and placement, impressions, clicks, video views, reward events, consent status, and related timestamps, session identifiers, or pseudonymous reminder/dose record identifiers. This does not include medicine photos, dose labels, or reminder times. | Used for product analytics, attribution, troubleshooting, and to operate, measure, limit, secure, and improve advertising. Recipients are described in the Advertising and Analytics sections below. |
| Diagnostics and ad revenue | SDK performance, errors, response information, mediated ad network, estimated impression revenue, currency, and revenue precision. | Used for troubleshooting, reporting, ad performance measurement, and fraud prevention. Development builds may also write diagnostic events to the device's system log. |
| Consent choices | Your advertising consent or privacy choices and region-dependent consent status. | Stored or processed by Google User Messaging Platform and made available to AppLovin MAX and supported mediated advertising partners so they can honor applicable choices. |
Medicine Photos and Local Processing
Medicine photos are used only to create the visual reminder and report features you request. Image processing takes place on your device. The app does not identify medicine, infer medical conditions, recommend a dosage, or make medical decisions from your photos.
Advertising, Mediation, and Personalization
DoseMate uses AppLovin MAX to mediate and display banner, native, interstitial, app-open, and optional rewarded ads. The advertising sources integrated in the version covered by this policy are AppLovin and Google AdMob. MAX selects and serves ads from the available source and provides impression-level reporting.
AppLovin and Google may process the information listed above to serve contextual, limited, non-personalized, or personalized ads, depending on your region, choices, device settings, and the providers' available controls. DoseMate does not send medicine photos, reminder details, or dose history to these advertising services for ad targeting.
Learn more about these providers and their controls:
- AppLovin Privacy Policy
- Google Privacy Policy
- How Google uses information from sites or apps that use its services
Consent and Your Advertising Choices
DoseMate uses Google's User Messaging Platform to request consent or present privacy choices where required. The app waits for the platform's consent result before requesting ads. When the app shows a Privacy choices option on its Info screen, you can use it to review or change available advertising choices. You can also reset or delete your Advertising ID, or adjust ad-privacy controls, in Android settings. Changing a choice may affect personalization but does not necessarily stop all ads or all processing needed for security, fraud prevention, measurement, or legal compliance.
Analytics and Attribution
DoseMate uses the following services in the production version covered by this policy:
- DataEye Analytics receives app lifecycle, screen, feature-action, permission-result, error, attribution, advertising lifecycle, and impression-revenue events, together with a session identifier and the event properties described above. DoseMate uses this information to understand product use, diagnose failures, and measure advertising performance.
- Firebase Analytics, provided by Google, receives app analytics events and impression-level advertising revenue events. DoseMate uses it to measure feature use, app performance, and advertising results.
- AppsFlyer receives device, install, campaign, media-source, channel, first-launch, deep-link, and advertising-revenue information. DoseMate uses it for install attribution, campaign measurement, and fraud prevention. AppsFlyer attribution fields are also associated with later DataEye analytics events.
- Google Play Install Referrer supplies install-referrer and campaign information to support AppsFlyer attribution. DoseMate does not upload the raw referrer URL to DataEye; only approved campaign and attribution fields are used.
The app does not send medicine photos, dose labels, reminder times, or generated PDF contents to DataEye, Firebase Analytics, or AppsFlyer. Analytics events can include pseudonymous internal reminder or dose-event identifiers so related action results can be correlated, but those identifiers are not user account IDs.
Provider information:
Permissions
- Camera: used when you take a medicine photo.
- Notifications: used to show reminder alerts.
- Alarms and boot completion: used to schedule reminders and restore them after the device restarts.
- Wake lock: used briefly so reminder delivery can complete reliably.
- Internet and network state: used to request ads, manage consent, and communicate with advertising services.
- Advertising ID: used by advertising services for ad delivery, measurement, and fraud prevention, subject to your device and consent choices.
Sharing and Third-Party Recipients
DoseMate makes advertising-related information available to AppLovin and Google, analytics information available to DataEye and Google Firebase, and attribution and ad-revenue information available to AppsFlyer for the purposes described in this policy. These providers process information under their own terms and privacy policies and may use service providers or process information in countries other than the one where you live. DoseMate does not operate an account server and does not sell or upload your medicine photos, dose labels, reminder times, or generated report contents.
Retention, Deletion, Backup, and Reports
- Reminder records, dose history, and their saved photos remain in app-private storage until you delete the reminder or uninstall the app.
- Deleting a reminder removes its database record, related dose events, and the original and processed photo files saved for that reminder.
- Weekly PDF reports are created in temporary app cache and shared only when you open the Android share sheet. Copies you save or send outside DoseMate are controlled by you and the receiving app.
- Android backup may include eligible app data when backup is enabled on your device. Backup and restored copies are controlled through Android or your Google account settings and may survive an uninstall.
- AppsFlyer attribution fields are also stored in app-private preferences until app data is cleared or the app is uninstalled, subject to Android backup and restore behavior.
- Advertising, consent, analytics, and attribution providers retain information under their own policies, service settings, and legal obligations. DoseMate cannot directly delete provider-held records that it cannot reliably connect to you.
Security
DoseMate stores reminder content in Android app-private storage and uses HTTPS/TLS connections provided by its advertising and consent SDKs for network transmission. No method of storage or transmission is completely secure, and this policy does not promise absolute security.
Your Rights and Choices
Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, or information about processing. DoseMate does not require an account and may be unable to identify provider records as belonging to you. You can delete individual reminders in the app, clear the app's storage in Android settings, uninstall the app, use available Privacy choices, or contact us at Lovedesiree593@gmail.com. The app currently does not provide a separate in-app analytics opt-out. Requests involving provider-held data may also need to be made through the controls or request channels in the providers' privacy policies.
Children
DoseMate is designed for adults and older adults and is not directed to children. The app's Google Play target-audience declaration and advertising configuration must remain consistent with this position. If you believe a child has provided information through the app, contact us.
This Website
This privacy page does not include advertising, analytics scripts, forms, or app-created cookies. The hosting provider may process standard server information such as IP address, browser or device type, requested page, and access time to deliver and secure the site.
Medical Disclaimer
DoseMate only helps you remember the schedule you selected. Always follow your doctor, pharmacist, prescription, or medicine label. If you are unsure whether to take a medicine, seek professional medical advice.
Changes
We may update this policy when app features, advertising partners, data practices, or legal requirements change. The effective date above shows when this version was last updated. Material changes will be reflected in the published policy before the related app release.