Privacy Policy for MediAlert

Effective Date: [07/04/26]

MediAlert ("we", "our", or "us") operates the MediAlert mobile application, a medication reminder application designed to help users remember and manage their medication schedules.

This Privacy Policy explains how we collect, use, and protect user information when you use the MediAlert application.

1. Information We Collect

MediAlert is designed to function primarily offline on the user's device. The application does not collect, store, or share personal health data with external servers.

However, the following types of information may be processed locally on the device:

Medication Reminder Data

Users may enter information such as:

• Medication names

• Dosage schedules

• Reminder times

• Alarm settings

This information is stored locally on the user’s device and is not transmitted to external servers.

Device and Diagnostic Data

Some technical information may be accessed by third-party services such as crash reporting tools or system SDKs to improve application stability.

This may include:

• Device type

• Android OS version

• App crash logs

• Network connection state

This data does not include personal medical data.

2. Permissions Used by the Application

MediAlert requires several Android permissions to ensure that medication reminders work reliably, even when the device is sleeping or locked.

These permissions are strictly used to support the app’s core functionality.

Exact Alarm Scheduling

Permissions Used

• SCHEDULE_EXACT_ALARM

• USE_EXACT_ALARM

Purpose

Medication reminders must trigger at precise times. These permissions allow the application to schedule alarms that are not delayed by Android battery optimization systems.

Device Wake and Power Management

Permissions Used

• WAKE_LOCK

• REQUEST_IGNORE_BATTERY_OPTIMIZATIONS

Purpose

These permissions ensure that:

• The device wakes up when a medication alarm triggers

• The alarm is not delayed or blocked by battery optimization features

This ensures critical reminders are delivered on time.

Restart After Device Reboot

Permission Used

• RECEIVE_BOOT_COMPLETED

Purpose

Android removes scheduled alarms after a device restart.

This permission allows the app to:

• Detect when the device restarts

• Automatically restore all medication reminders

Without this permission, users would have to manually reopen the app after every reboot.

Foreground Service Execution

Permissions Used

• FOREGROUND_SERVICE

• FOREGROUND_SERVICE_MEDIA_PLAYBACK

Purpose

These permissions allow the alarm system to:

• Continue playing reminder sounds

• Vibrate until the user interacts with the alarm

This ensures the reminder cannot be silently stopped by the system.

Lock Screen and Overlay Notifications

Permissions Used

• SYSTEM_ALERT_WINDOW

• USE_FULL_SCREEN_INTENT

• DISABLE_KEYGUARD

Purpose

Medication reminders may need to display immediately and visibly, even if the device is locked or another app is open.

These permissions allow the alarm screen to:

• Appear over other applications

• Show on the lock screen

• Allow the user to respond quickly (Take / Snooze)

Notifications and Alerts

Permissions Used

• POST_NOTIFICATIONS

• VIBRATE

• ACCESS_NOTIFICATION_POLICY

Purpose

These permissions allow MediAlert to:

• Send reminder notifications

• Vibrate the device for alerts

• Bypass silent or Do Not Disturb modes for critical reminders

Audio Access for Custom Alarm Sounds

Permissions Used

• READ_EXTERNAL_STORAGE

• READ_MEDIA_AUDIO

Purpose

These permissions allow users to select custom ringtone or alarm sounds stored on their device.

The app only accesses audio files chosen by the user.

Network State Access

Permission Used

• ACCESS_NETWORK_STATE

Purpose

This permission allows the application or integrated services to detect whether an internet connection is available before attempting optional tasks such as crash reporting or updates.

3. Data Storage

All medication and reminder data is stored locally on the user’s device.

MediAlert does not store or transmit personal health data to external servers.

4. Data Sharing

We do not sell, rent, or share user data with third parties.

Some anonymous technical data may be processed by integrated Android services for:

• Crash reporting

• App stability improvements

5. Data Security

We take reasonable measures to protect user data. Since most information remains stored locally on the device, the user retains full control of their medication information.

6. User Control

Users have full control over their data and can:

• Modify reminder schedules

• Delete medications

• Uninstall the application to remove all stored data

7. Children's Privacy

MediAlert is not directed toward children under the age of 13. We do not knowingly collect personal information from children.

8. Changes to This Privacy Policy

We may update this Privacy Policy periodically. When changes occur, the updated policy will be published with a new effective date.

9. Contact Us

If you have any questions about this Privacy Policy, please contact us:

Email: [vaibhav.iboy@gmail.com]
Developer Name: [Vaibhav Vishal]
Application Name: MediAlert

✅ Important for Play Store submission

You will also need:

• Developer email vaibhav.iboy@gmail.com

• App name MediAlert

• Developer company name Peepaal.in