Privacy Policy — Android

1. About this policy

Menolora is a personal symptom and treatment diary for perimenopause, menopause and the years after. This policy explains local health records, optional sharing, and technical information processed when the app checks for updates.

This policy covers Menolora for Android and its sharing website. Version 1.0, effective 2026-09-25. The iOS privacy policy is published separately.

2. What Menolora records

The following records are entered by you and stored locally.

• The menopause stage, optional age range and focus areas you choose
• Symptoms you log, each with an intensity from 1 to 10 and a date and time
• Optional notes, care records, and cycle observations such as flow and pain
• Treatment names, forms, optional active ingredients, manufacturer, doses and schedules, start/end dates and notes
• Local reminder settings and visit reports you generate
• Your language and appearance preferences

3. Information the app does not request

Menolora does not require a user account and does not upload your health database to a Menolora server. It does not request the information or permissions listed below for tracking. If you contact support by email, we receive the address and information you choose to send. Technical update-service information is described in section 6.

• Name, email or phone number for app registration
• Device location permission
• Payment or billing details inside the app
• Advertising identifiers such as IDFA or Android advertising ID
• Contacts, photo-library, microphone or camera access

4. Where your data is kept

Your health entries are stored in a private local database. Android backup and device-transfer exclusions are configured for the app. Menolora provides no cloud sync or recovery service for these records.

Health records are not automatically uploaded to Menolora or Expo. Exporting a report or sharing selected products sends a copy through the destination you choose. Generated images and PDFs may also remain in local app cache until it is cleared; deleting database records does not recall these files or copies already shared.

5. Health integrations

The current Android version has no Apple Health or Health Connect integration. Tracking is manual.

6. Connections the app makes

The app can contact software-update services. These requests are separate from your local health database and do not intentionally include symptom entries, treatment notes or report contents. Service operators also receive ordinary connection information such as an IP address.

On release builds, app code checks for a compatible Expo EAS Update shortly after startup and again when foregrounded, at most once every six hours. Disabling Expo’s native automatic launch check does not disable these app-initiated checks. The app asks before downloading and applying an available update; there is no in-app switch to opt out of the checks themselves.

Expo receives a random installation identifier, platform/runtime information and update identifiers to deliver compatible updates. If a previous native launch failure is recorded, a limited error description may accompany a later request. This is technical data processing, not an upload of your health diary. Requests use HTTPS. Provider retention and deletion are governed by the applicable service arrangements and provider policies; deleting local diary entries does not delete provider logs.

Opening a support, legal or source link also connects to that website. Its operator may process connection information under its own policy.

• Expo EAS Update: software delivery and update recovery. https://expo.dev/privacy-explained — https://expo.dev/privacy

7. Your controls

You control the records you enter and the exports you create. Deletion is permanent; sharing cannot be undone by deleting the original record.

A product share link contains the selected snapshot in its URL fragment. The fragment is decoded in the recipient’s browser and is not sent as part of the HTTP request to the website host. It is encoded, not encrypted. Anyone with the complete link can view or forward it; links have no access password, revocation or automatic expiry.

Images, PDFs and links go through the app you select in the system share sheet. The receiving app and recipient control their copies. The card excludes private treatment notes; optional ingredients, doses and dates appear only if you select them.

• Settings → “Delete all local data” clears the app’s local record database and preferences and cancels its scheduled treatment reminders. It does not erase shared copies, generated export caches or update-provider logs.
• Uninstalling removes local app records; Menolora has no cloud backup to restore them from.
• You can withdraw notification permission in your device settings.
• For questions about service-provider technical data or privacy requests, contact support@menolora.com. Do not send health records unless you want support to receive them.

8. Your rights

You can view, edit, export supported reports and delete your local records in the app. We do not hold a server copy of your health database to recover for you. For requests concerning information received through support or technical service providers, contact support@menolora.com.

Where the GDPR applies you have rights of access, erasure, portability and objection, and you may complain to your supervisory authority. Under Türkiye’s KVKK, health data is special-category data and is treated as such here. If you are a California resident, the CCPA gives you the right to know, to delete, and to opt out of the sale of personal information; Menolora sells no data of any kind.

Applicable rights depend on your location and the processing involved. Deleting local records does not automatically exercise rights against a service provider or remove a recipient’s copy.

9. Children

Menolora is intended for adults and must not be used by anyone under 18. We do not knowingly collect information from children. If you believe a child has used the app, contact us at support@menolora.com.

10. Not medical care

Menolora is a personal record, not a medical device. It does not diagnose, treat, monitor or predict, and it is not a substitute for professional care.

Educational articles name their source — The Menopause Society and ACOG — and open that source’s own website. They are general information, not advice about you.

If you are worried about a symptom, contact a qualified health professional. In an emergency, contact emergency services.

11. Cookies and the website

The app does not use advertising cookies or cross-app advertising tracking. Its software-update installation identifier is described in section 6.

menolora.com does not use advertising cookies. On pages offering optional analytics, Google Analytics 4 loads only after you choose “Allow analytics.” Declining keeps those pages usable without loading Google Analytics. Your consent choice is stored in your browser. Google’s analytics processing follows its own privacy documentation.

The product share page decodes its snapshot in the recipient’s browser and has no analytics integration. Do not put health details into support messages or other website fields unless you intend to send them. Website hosting providers may process ordinary request information such as IP addresses; this is separate from the app’s local health database.

12. Changes and contact

If we change how health data is handled, this page will carry a new version number and a new effective date. The summary at the top always describes the version you are reading.

For any privacy question, write to support@menolora.com.