MedTick: Medication Reminder Privacy Policy

# MedTick Privacy Policy Last updated: October 1, 2026 Canonical public policy URL: https://consultant.quinnfavo.com/privacy/medtick-medication-reminder MedTick is a Wear OS and Android phone medication reminder app. Each can run local reminders; the phone requires explicit opt-in. A watch does not require a phone. This policy covers the MedTick Android and Wear OS applications. Visits to the website hosting this policy are covered separately by the website privacy notice at https://consultant.quinnfavo.com/legal/privacy. Website analytics are not part of the MedTick apps. ## Important local-data notice Medication names, supplement names, dose schedules, reminder notes, and adherence history can be sensitive. MedTick keeps this information on the device where you use it. If you pair a phone and watch, medication and schedule setup is copied between them as described below. Dose history is stored locally on each device and is not synchronized. MedTick does not automatically send your medication content to the developer or a MedTick-operated server. If you choose to export or share a report, or include medication information in a support request, the recipient receives what you choose to send. ## Data stored locally MedTick may store: - Medication or supplement names you enter. - Dose schedules, reminder times, recurrence rules, and notes. - Taken, skipped, snoozed, refill, and adherence/history state. - Notification preferences and alarm scheduling state. - Local tile and complication state for upcoming-dose display. - Local file/export state if an in-app export or share flow is used. ## Permissions The watch app requests VIBRATE, POST_NOTIFICATIONS, RECEIVE_BOOT_COMPLETED, USE_EXACT_ALARM, SCHEDULE_EXACT_ALARM (for Android API 31-32), and FOREGROUND_SERVICE for reminder notification, scheduling, recovery, haptics and brief Alarm-mode ringing. It includes a local FileProvider for user-initiated export/share flows where available. For phone reminders, the Android app declares POST_NOTIFICATIONS, SCHEDULE_EXACT_ALARM, RECEIVE_BOOT_COMPLETED, FOREGROUND_SERVICE, and VIBRATE. It asks for notification permission and exact-alarm access from the phone reminder setup, and can use less precise timing if exact access is unavailable. Phone-to-watch sync itself requires no runtime permission. Google Play Billing can add the non-runtime com.android.vending.BILLING permission for optional Pro purchase and restore. The current manifest does not declare location, camera, contacts, calendar, health/body-sensor, or advertising ID permissions. ## In-app purchases MedTick offers an optional one-time "Pro" upgrade through Google Play Billing. Google Play handles checkout and payment credentials; MedTick verifies and locally caches Pro entitlement separately on each form factor. The developer does not receive your payment-card credentials through MedTick, but Google Play may make limited transaction/order information available to the developer for purchase support and refunds. ## Optional voice input When you choose to add a note or text by voice, MedTick launches your device's built-in speech-recognition service. The audio is handled by that system service (for example, Google's speech recognizer) under its own privacy policy, not by MedTick. MedTick does not record audio itself and does not request the microphone permission; it only receives the recognized text you confirm. ## What MedTick does not do MedTick does not automatically transmit medication content to a developer-operated service, and the current app code has no advertising SDK, developer-operated analytics service, MedTick account, or medication backend. Optional phone/watch synchronization is not a MedTick-hosted cloud account or backup: Google Play services carries the transfer between your devices and may route it through Google-managed infrastructure. Google Play processes purchases and may provide limited order information for purchase support. User-initiated exports and information you send to support are handled by the destination you choose. ## Optional phone companion The Android phone app can remind you without a watch, storing medication setup and dose actions on the phone. Pairing is optional; your watch reminds you with or without it. **Medication content is not synchronized before you confirm pairing.** You choose a watch on the phone, review the proposed data sharing and then confirm on the watch. Google Play services may exchange technical discovery and pairing messages during setup; declining on the watch prevents medication configuration from being sent. **Shared:** medication names, dosage text, instructions, reminder schedules, and active/paused state — between your watch and the one phone you paired. **Not shared:** dose history, dose-history notes, snooze state, purchase information, and app settings. Medication instructions are part of the shared configuration; notes attached to dose history are not. **Changes travel both ways.** A change you make on the phone is saved there first and then sent to your watch, which applies it and rebuilds its own reminders. If you enabled phone reminders, the phone also schedules its own local alarms until you choose to hand off to watch reminders. Until the watch has applied a configuration change, the phone says so. Dose actions remain on the device where you recorded them. **Carried by:** Google Play services, between your own two devices, over its Wear Data Layer. It prefers a direct connection to your paired phone; when the two cannot reach each other directly it may route through Google-managed infrastructure, which Google documents as end-to-end encrypted. There is no MedTick account and no MedTick server. **You can stop it:** disconnect from the phone at any time. Disconnecting deletes nothing and your watch keeps working. A separate action erases the phone's copy without touching the watch. The phone companion's data is excluded from Android cloud backup and device-to-device transfer. ## Help and support MedTick exposes an explicit **Report a bug** action. On Android, it opens the MedTick support page in the browser. On Wear OS, it asks the paired phone to open that same page so the user does not need to type a report on the watch. The support URL contains only the flow type, source platform, and a bounded app version when available. The Android app can also copy a locally generated, allowlisted technical summary after the user taps **Copy technical details**. That summary contains only app/version, Android release/API, and device manufacturer/model. It does not include medication or supplement names, dosage text, instructions, schedules, reminder times, dose history or notes, snooze state, pairing/installation IDs, Data Layer payloads, purchase data, or logs. Nothing is automatically attached or uploaded by MedTick. If you choose to enter medication information or other content in the external support form, that submission is your explicit action. ## Data deletion You can delete local MedTick data by deleting medications or reminders where available, clearing app storage in Android/Wear OS settings, or uninstalling the relevant app. Disconnecting phone and watch stops synchronization but does not erase existing local copies. To erase the paired phone's copy without changing the watch, use the phone companion's separate removal action or clear its app storage. Clearing watch storage does not automatically erase a disconnected phone's copy. Google Play purchase records are managed through Google Play. ## Safety disclaimer MedTick is a reminder utility. It is not a medical device and does not provide medical advice, diagnosis, treatment, or emergency medication guidance. ## Contact For privacy questions, contact Quazmoz@vivaldi.net.