Medeazy privacy policy

Contact

Medeazy's contact is Garv Narsinghani. For app or privacy questions, email medeazy.care@gmail.com. Do not email passwords, sign-in codes or medical records.

Your account

Medeazy uses your email, account name and sign-in identifiers to create your account, verify access and keep your records separate from other accounts. Supabase Auth handles email and password authentication. Brevo delivers email-verification and password-reset codes. Your Medeazy password is not your Google password.

Where Google sign-in is offered, Google and Supabase process the basic identity needed to sign you in, including your email, provider identifier and profile information made available by Google. This basic sign-in does not ask to read Gmail messages or Google Calendar. Optional Calendar access is requested separately as described below. Google and email/password identities with the same verified email may be linked to the same new Medeazy account.

New accounts start with an empty record. Records from older, separate Medeazy accounts are not automatically imported or matched by email.

Optional Google Calendar connection

Calendar connection is separate from Google sign-in and is optional. If you choose to connect, Medeazy requests access only to secondary calendars it creates and events on those calendars. It does not request Gmail access or access to your primary calendar. Medeazy verifies that the permission belongs to the same linked Google identity as your signed-in Medeazy account.

The account service stores an encrypted Calendar refresh credential in the Mumbai database. Its encryption key is kept separately in the Singapore account service. This credential is used only for the Calendar connection you authorize. A saved connection status does not prove that Google permission has not been revoked since it was saved. Medeazy checks the credential and linked Google identity again when using the connection.

Permission alone does not create a calendar, send medicine names to Google, create events or enable alerts. Where the checked Calendar feature is offered, you separately choose whether to create an empty calendar named Medeazy reminders, then review an exact event plan before any changes are applied. The plan names the calendar, dates, times, timezone, creations, updates and removals. Changing the saved schedules or review choices invalidates that plan. A review expires after five minutes and cannot be silently replayed.

Calendar events use the generic title Medeazy reminder and the description Open Medeazy to review your saved reminder. They do not include medicine names, doses, report text, family notes, attendees or attachments. Google receives event dates, times, timezone and opaque event-ownership markers. These can still reveal a reminder schedule to Google and anyone with access to that calendar. Only saved app-owned events on the separate Medeazy calendar may be changed; other Google calendars and events are not imported or changed by this feature.

Mumbai storage keeps the selected calendar identifier, event identifiers and ownership mappings, a limited snapshot of saved medicine-schedule identifiers, dates, expiry/archive state, days, reminder times, before/after offsets and saved time-entry status, and review/change records needed to avoid repeating an uncertain write. The limited snapshot does not include medicine names, doses, report text or family notes. This bookkeeping is separate from the medicine records you already choose to save in Medeazy.

A plan can separately request a Google popup at event time. No Google email reminder or attendee invitation is sent. Google Calendar popups are not Android medicine alarms and are not proof that an alert reached your phone. Keep an independent reminder method. Free-service limits, connection failures and Google settings can delay or prevent Calendar changes or alerts.

If a Calendar creation or change cannot be confirmed, Medeazy stops further automatic attempts rather than risking duplicates. A calendar or event may already exist in Google. Disconnecting Calendar or deleting the Medeazy account can pause while an operation is in progress or awaiting review. Support must stop the relevant worker and review the exact operation before that change can continue. This review does not itself repeat or reverse a Google change, and an uncertain plan cannot be resumed merely because support reviewed it.

Disconnecting Calendar removes Medeazy's stored Calendar credential and associated Calendar setup, mappings and review records once any in-progress operation has finished or been safely reviewed. Existing Google calendars and events remain, and Google's permission is not revoked by this step. To revoke it too, remove Medeazy in your Google Account permissions; doing so can also affect Google sign-in. Deleting your Medeazy account removes its stored Calendar credential and associated Calendar bookkeeping after the same operation checks, but does not delete your Google account or existing Google calendars or events.

Records you choose to save

Medeazy stores medicine details and schedules, refill notes, recorded doses, profile information, preferences and family-history notes that you choose to enter. These records can reveal health information. Enter only information you have the right to provide. Check the accuracy of medicine names, amounts and instructions.

The app uses saved records to display, update and summarize your information. A recorded dose describes what was entered, not proof that a medicine was taken. A saved schedule does not prove that a reminder was delivered.

Clinical AI, prescription reading and automated medical analysis are unavailable in this version. Those unavailable features do not send prescriptions or health records to an AI service. Basic Google sign-in does not authorize broader Google access.

Services and processing locations

Supabase provides authentication and the primary app database in Mumbai, India. The account service uses Render hosting in Singapore. Brevo handles authentication-email delivery; Google handles its sign-in service. These services process the connection, account, security and delivery information needed for their part of the service.

Mumbai is the primary database location, not a promise that all processing stays in India. Provider support, security and other service records may be handled elsewhere. The public development website is hosted on Cloudflare Pages and has a separate website privacy notice.

Information on your device

The app uses sign-in tokens to maintain your session and device storage for account and interface state. It also keeps opaque request markers to avoid silently repeating an uncertain medicine-save request. A marker is not a copy of the medicine's text. Logging out does not erase records stored in your account or copies you have saved elsewhere.

Retention and deletion

Saved app records remain until you remove supported entries or delete the account. Archiving a medicine hides it from the active list; it does not erase its stored history. There is no automatic medical-record expiry in this version.

Account deletion requires explicit confirmation and fresh verification of the same account. Use your Medeazy password, or the same linked Google identity where that verification method is available. The process blocks account access, erases active app records and removes the authentication identity. Minimal non-content deletion bookkeeping can remain to prevent replay or accidental account resurrection.

If completion cannot be confirmed, the account stays locked for review rather than being reported as successfully deleted. Contact support with the account email, never your password or code. Do not recreate the account while uncertain deletion is being checked.

Account deletion cannot recall exported or forwarded copies, erase copies on other devices, change existing phone alarms or delete records in older separate systems. Providers may retain independent security, delivery or backup records under their own settings and policies. No immediate removal from every provider system or fixed expiry for every provider record is promised.

An in-progress or unresolved email or Calendar operation can temporarily pause account deletion. Support must stop the relevant sender or worker and reconcile or review the exact operation before deletion continues. Do not repeat the request to try to clear the pause. Contact medeazy.care@gmail.com from your account email without passwords, sign-in codes or medical records. This does not recall an accepted email, remove Google calendars or events, or promise a fixed completion time.

Security, backups and free-service limits

Account controls are intended to restrict each account to its own records. No system can promise complete security. Keep your password and codes private and protect access to your device and email.

The free database plan does not include automatic daily database backups. No separate automatic backup or guaranteed restoration service is provided. Free hosting and database limits can interrupt access or cause loss of records. Keep another usable copy of information needed for medical care; Medeazy must not be your only copy or reminder method.

Changes and questions

Changes to available features, providers or processing must be reflected in this policy. New clinical processing or Google permissions beyond those described here require an updated policy and the relevant consent. Contact medeazy.care@gmail.com with questions about access or deletion.

Optional email review reminders

If you choose to enable email review reminders, Medeazy saves your chosen weekly or monthly schedule, time zone, consent version and delivery status. Reminders go only to the current verified email of your Medeazy account. You cannot choose another recipient in the reminder controls.

Each reminder uses this fixed subject and message. It contains no medicine names, record counts, report results, medical records or attachments. The link asks you to sign in before viewing app records. The in-app preview covers the last 30 days, not a completed calendar-month report.

Brevo processes your email address, the fixed message and delivery information to deliver these reminders. Brevo and anyone with access to the destination inbox can see that the address receives Medeazy reminders. Delivery records may be retained by the email service under its policies. Brevo may also use open pixels and tracked links to collect opening and click information under its account settings. These reminders are not guaranteed to be tracking-free.

Email reminders are off by default and need a separate choice from consent to view health details inside the app. You can turn reminders off in the app. Changing the schedule requires reviewing the separate email consent again. An email already accepted by the email service cannot be recalled. A send already in progress may finish before a change takes effect.

A delivery problem with an uncertain outcome stops further automatic reminders for that account rather than risking duplicate messages. Changing reminder choices or deleting the account may pause while a send finishes. If a send cannot be confirmed, support must stop the sender and reconcile the delivery status before completing the change or deletion. Contact medeazy.care@gmail.com from your account email without passwords, codes or medical records. Support does not need your medical records for this check.

Medeazy deletes its saved reminder preferences and delivery jobs when the account is locked for deletion after an in-progress send has finished or been safely reconciled. This does not recall sent messages or erase copies already held by inboxes or the email service.