Privacy

Last updated: 4 November 2026

Translations: Italiano · Français · Español · Deutsch. The English version prevails.

This policy describes how MedReminder handles personal data on Windows desktop, Android and iOS (iPhone). It applies to the versions and features made available for each platform; a feature may not yet be available in every release. The Windows desktop app is distributed as ZIP packages, MSI installers and through the Microsoft Store. Android is distributed through Google Play, including its testing tracks. iOS is distributed through the Apple App Store, including TestFlight.

1. Summary

• MedReminder stores your data on your device. The developer runs no server and receives none of your data.
• There is no account with the developer, no telemetry, no analytics, no advertising and no tracking.
• Data leaves your device only through features you use or turn on, such as email, export or sharing, cloud backup, sync and catalogue downloads. Each feature sends data only to the service or destination described below. Platform-specific services, such as Google Play and App Store updates, are described separately.

2. Who is responsible

MedReminder is free, open-source software (Apache License 2.0) developed by vger70. Because the developer does not collect or receive your data, you remain in control of it: the application processes it on your own device, on your behalf.

Contact: [email protected], or an issue at https://github.com/vger70/MedReminder/issues (do not post health data in a public issue).

3. Data stored on your device

Windows desktop

MedReminder keeps its data in %LOCALAPPDATA%\MedReminder\ under your Windows account. This includes:

• profiles: name, role, optional PIN (stored as a hash);
• medicines, doses, schedules, stock, intakes, prescriptions, administrative deadlines and notes, one database per profile;
• email settings: SMTP server, user name and password (the password is encrypted with Windows DPAPI), sender and recipient addresses, including an optional doctor or caregiver address;
• sign-in tokens for OneDrive or Google Drive, if you connect them;
• settings, backups you configure, and log files.

The profile databases are not encrypted on Windows: anyone who can use your Windows account can read them. The profile PIN prevents opening the wrong profile by mistake; it is not protection. To keep data apart from other people, give each person their own Windows account.

Windows log files never contain passwords, email bodies or medical notes. Uninstalling the Windows app does not delete its data folder; delete it separately to remove that data.

Android

MedReminder stores its databases, settings and log files in the app’s private storage on the phone. Android’s automatic app-data backup is disabled, so the operating system does not copy this health data to an Android backup account. The backup passphrase is kept using Android’s secure key storage. Google Drive access is managed by Google Play services, which keep the grant and give the app short-lived access tokens. OneDrive sign-in tokens are kept by the Microsoft sign-in library in the app’s private storage, which other apps cannot read and which is excluded from Android backup. Android log files do not contain passwords, email bodies or medical notes.

Clearing MedReminder’s app data or uninstalling it removes its local copy. Before doing so, use the app’s export or cloud-backup features if you want to keep a copy.

iOS (iPhone)

MedReminder stores its databases and settings in the app’s private storage on the iPhone, which other apps cannot read. This storage is excluded from iCloud and computer backups, so iOS does not copy this health data to an iCloud backup or to a computer, and a backup restored to another iPhone does not contain it. Local secrets, such as the backup passphrase, the email password and the OneDrive and Google Drive sign-in tokens, are encrypted with a key kept in the iOS Keychain. Only MedReminder on that iPhone can read this key, once the iPhone has been unlocked after it was turned on; the key is never synced to iCloud Keychain. You sign in to OneDrive or Google Drive on the provider’s own page, opened by iOS; MedReminder never sees your Microsoft or Google password. The iOS app writes no log files.

Deleting MedReminder from the iPhone removes its local copy. iOS may keep the app’s Keychain key after the app is deleted; only MedReminder can read it, and without the deleted data it opens nothing. Before deleting the app, use its export or cloud-backup features if you want to keep a copy.

Reminders are local notifications scheduled on the iPhone; no push notification service is used. Depending on your iOS notification settings, their text, such as a medicine name, may appear on the lock screen and on a paired Apple Watch.

4. Data that leaves your device

Only these features send or share data, and only when available and used or enabled:

When you connect OneDrive or Google Drive, MedReminder requests access for its app data and backup files, not general access to your other files. Turning cloud backup or sync off stops future uploads from that feature; you can revoke the app’s access in your Microsoft or Google account settings. Turning a feature off does not by itself delete copies already stored with the provider. The cloud and email providers process data under their own privacy policies.

On Windows, cloud backup and sync can also use folders you select. Those folders may be synchronized by a cloud provider or shared with other people; their access and processing are governed by that provider and your folder settings. Android cloud backup and sync use the connected OneDrive or Google Drive account. Scheduled work on Android may be delayed by Android or device battery-management settings. On iPhone, cloud backup and sync use the connected OneDrive or Google Drive account, and iOS decides when background work runs: it may delay it or, for an app you rarely open, not run it.

The Microsoft Store, Google Play and the App Store may give the developer aggregate statistics, such as downloads, and crash reports, depending on your device’s diagnostic and sharing settings (on iPhone, “Share with App Developers”). These do not include the data stored in MedReminder.

How MedReminder uses Google user data

When you connect Google Drive, MedReminder requests two permissions: drive.file (only the files and folders the app creates) and drive.appdata (a hidden folder reserved for the app). It cannot see, read or change any other file in your Google Drive. It uses them only to create a visible MedReminder › backups folder and store encrypted backup files there, to store encrypted sync data in the hidden app folder, and to list, download and delete those files when you restore or sync, or when old backups exceed the number you chose to keep. It also reads the connected account’s email address and Drive account identifier and, on Android and iPhone, its display name, only to show you which account is connected and to tell accounts apart. Backup files are encrypted on your device with your backup passphrase, and sync data is end-to-end encrypted, before upload: neither Google nor the developer can read their content.

Storage, sharing and Limited Use

The details of the connected account and the sign-in tokens are kept only on your device; section 3 describes where on each platform, and on Windows they are encrypted with Windows DPAPI. Google user data is not sent to the developer or to any third party, is not sold, is not used for advertising, and is not used to develop, improve or train artificial intelligence or machine learning models. MedReminder’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Removing access and deleting data

You can revoke MedReminder’s access at any time in your Google Account, under Security › Your connections to third-party apps and services (https://myaccount.google.com/connections); the app can then no longer reach your Google Drive. To delete what the app stored in Google Drive, delete the MedReminder folder in My Drive and, in Google Drive Settings › Manage apps › MedReminder, choose Delete hidden app data. For OneDrive, delete the Apps › MedReminder26 folder and remove the app’s access in your Microsoft account privacy settings.

5. Camera and app lock

The barcode scanner can use the Windows webcam, or the Android or iPhone camera, when you choose to scan. Images are processed on your device and are not saved or sent by MedReminder. On Windows, the camera turns off when a code is read, when you close the scan window, or after 30 seconds. On Android and iPhone, the camera is used only with the permission you grant in the operating system, to read medicine barcodes or the QR code another device shows when you join a circle; the code is not saved. On Android, camera access also follows the app lifecycle, and the circle QR code is read only while the scan page is open. On iPhone, the camera is used only while a scan page is open.

On Android and iPhone, the optional app lock uses the phone’s own unlock: biometrics, such as a fingerprint or Face ID, or the screen lock PIN, pattern or passcode. The operating system performs the check; MedReminder receives only whether it succeeded, never biometric data.

6. Links that open your browser

Some commands open a web page in your browser, such as a medicine leaflet or information page, the user guide, or the project page. On Windows, a donation link may also open a Stripe or PayPal page if you choose it. MedReminder sends no data to these sites; your browser does, under the sites’ own policies. MedReminder never sees payment details.

7. Children

MedReminder is not directed to children. The developer does not collect personal data from children through the app.

8. Your rights

You can view, correct, export and delete data in MedReminder. On Windows, use Settings → Backup / Restore → Export all data; on Android and iPhone, use the app’s export and data-management controls. You can also remove local Android app data in Android settings, or delete the app from the iPhone. Copies in email, exported or shared files, OneDrive or Google Drive must be managed with the relevant recipients, apps or providers.

9. Changes

Changes to this policy are published here, with a new “Last updated” date. The history is visible in the repository: https://github.com/vger70/MedReminder/commits/main/PRIVACY.md

This website

Website analytics

This website uses Cloudflare Web Analytics to count page views and visits. Cloudflare adds its script automatically for visitors outside the European Union; for visitors in the EU no analytics script is loaded. No cookies are set.

Version check on this page

To show the latest version number and download links, this page asks the GitHub Releases API (api.github.com) for the current release. Your browser therefore contacts GitHub when the page loads.

Payments

Donations open the payment provider's own hosted page (Stripe or PayPal). This site never sees your card details, never stores anything about the transaction, and receives no confirmation from the provider.