MenoHealth Health Data Disclosures

Effective Date: November 5, 2026 | Last Updated: October 30, 2026 | Version: 0.0.1

1. Purpose of This Document

This document explains how MenoHealth, Inc. (“MenoHealth,” “we,” “us”) collects, uses, protects, shares, and deletes health information. It supplements our Privacy Policy and Terms of Service. The Privacy Policy and Health Data Disclosures govern MenoHealth’s data practices. The Health Data Disclosures control for consumer health data if a specific provision conflicts, and applicable state-specific provisions control for the users and activities they cover.

This document also serves as our Consumer Health Data Privacy Policy for purposes of the Washington My Health My Data Act, the Nevada Consumer Health Data Privacy Law (SB 370), and similar state laws. A link to this document appears on our website homepage and within the app.

2. Who We Are — and What We Are Not

MenoHealth is a wellness application for women navigating perimenopause and menopause. It provides symptom tracking, pattern insights, educational content, coaching exercises, and access to independent telehealth providers.

MenoHealth is not a covered entity under HIPAA, the federal Health Insurance Portability and Accountability Act. We handle health information under this document, our Privacy Policy, applicable consumer privacy, health-data and medical-confidentiality laws, and applicable source agreements.

Exception — telehealth. If you choose to have a telehealth visit through the app, the clinician and clinical network you see are healthcare providers. Information you share with them in a clinical encounter is governed by their notice of privacy practices and, where applicable, HIPAA. Section 9 explains what moves between MenoHealth and the clinical side, and when.

MenoHealth is not a medical device and does not provide medical advice, diagnosis, or treatment. Insights are wellness information, not clinical conclusions. MenoAI, our coaching assistant, is artificial intelligence — its responses are computer-generated, not written by a human clinician.

3. The Health Data We Collect

We collect health data only as described here and with the applicable consent described in Section 4. Sources include information You provide, MenoAI interactions, connected devices and applications, and information we derive or infer from those sources. Categories:

a. Information you enter yourself. Symptoms you choose to track (such as hot flashes, night sweats, sleep disruption, mood changes, brain fog), severity, frequency, daily check-ins, free-text notes, menstrual cycle information you log, and your answers to onboarding questions about your menopause stage and health history.

b. Information captured from your conversations with MenoAI. Our AI coach can save health observations from your chats:

• Observations in categories you already track. If you tell MenoAI “I barely slept and had two hot flashes,” it can log those to your tracked symptoms. Every entry appears in your symptom log, where you can see, edit, or delete it at any time.
• Mentions of things you do not track — we ask first. MenoAI does not add a new symptom category to your symptom log quietly. If you mention a symptom you have not chosen to track, MenoAI asks in the conversation whether to log it before making that log entry. If you say no, no symptom-log entry is created; the conversation itself remains subject to Sections 6 and 7. Starting to track a symptom going forward is a separate choice.
• MenoAI memory. With your separate, explicit consent (its own separate choice, off until you turn it on), MenoAI can remember helpful things you tell it across conversations. Every memory is visible in the app, where you can erase any memory, or all of them, at any time. If you decline, MenoAI keeps context only within a single conversation. Memories do not affect your scores or insights.

c. Information from devices and apps you connect. If you connect a wearable or health platform (Apple Health, Google Health Connect, Oura, and other supported devices), we collect the biometric data needed for the service: heart rate variability (HRV), sleep stages and quality, skin/body temperature trends, activity, and — if you connect a glucose monitor — glucose readings. Connecting is optional and controlled by you; you can disconnect at any time in Settings, and disconnecting stops new collection. When you connect a source, we also record which app or device you connected and whether the connection is working, solely to keep your connection running (see Sections 4 and 8).

d. Meal and nutrition information. If you use meal logging, we process the photos and food descriptions you submit to estimate nutritional content and identify potential symptom triggers. Photos and descriptions are analyzed by our AI model providers under the same signed zero-retention agreements, and the uploaded file is deleted from the provider after analysis.

e. Lab results you provide. If you upload laboratory results (such as hormone panels), we collect the values needed to display and interpret them within the app.

f. Information we infer. The app computes wellness metrics from the data above — including your MenoHealth Score, pattern correlations (for example, a relationship between sleep quality and next-day symptoms), and personalized suggestions. Inferred health information is treated as consumer health data with the same protections as data you entered yourself.

We do not collect: precise geolocation; biometric identifiers used for identification (your face, voiceprint, or fingerprints); genetic data; or data from your device’s contacts, photos (other than images you deliberately submit), or your microphone — if you use voice input, it is transcribed on your device and we receive only the resulting text, not the audio.

4. Consent — When We Ask, and What Each Consent Covers

We use a layered consent model. Each consent is separate, plainly worded, and recorded with a timestamp:

• Account acceptance and health-data consent. At sign-up you accept the Terms, Privacy Policy, and these Disclosures. A separate, plainly worded health-data consent screen appears during onboarding before health-data collection. Where affirmative consent is required, we identify the relevant categories and purposes and obtain the required choice separately from general terms. We obtain any additional purpose-specific consent or authorization required by applicable law.
• MenoAI memory consent (optional, separate). A separate, affirmative choice — presented before memory is enabled and changeable in the app at any time — governs whether MenoAI may remember information across conversations. Memory is off until you turn it on. Declining does not reduce any other functionality.
• Device and platform connections (optional, per source). Each wearable, health platform, or app connection is initiated by you and authorized through that platform’s own permission screen plus ours. Our connection screen also tells you, in plain words, that our analytics service sees how you use the app (to find bugs) and which app you chose (to keep the connection working) — and your tap to connect is your consent for that app and that purpose. Disconnecting in Settings ends it.
• Historical backfill (optional). Importing past health data, such as prior Apple Health history, is disclosed in the connection consent for that source. Recent and historical data remain subject to that permission and the source’s terms.
• Research participation (optional, separate). Enrollment in a separately offered research study is governed by a study-specific Informed Consent and is not bundled with product consents. Work with Qualifying De-identified Data is governed by Section 5.

You can withdraw consent in Settings at any time. Withdrawal immediately stops new collection covered by that consent and also stops consent-dependent processing when and as applicable law or the governing consent requires. For MenoAI memory, you may erase everything already remembered. We do not make you call, email, or contact support to withdraw a consent you gave with a tap. Section 7 explains retention, including continued use of Qualifying De-identified Data.

We do not collect health data before the applicable consent exists. Consent screens are not pre-checked, and consent is not inferred from continued use.

5. How We Use Your Health Data

We process health data for the following purposes, subject to applicable law, the relevant consent and source permissions, and the conditions below:

• Providing and personalizing the service you signed up for: tracking, scores, insights, pattern detection, coaching content, and reminders;
• Making non-clinical suggestions inside the app, including asking whether to log a new symptom category mentioned in conversation. Observations in symptom categories you already track can be logged as described in Section 3; a new category requires your affirmative choice;
• Facilitating a telehealth visit, if and only if you request one (Section 9);
• Safety features, such as surfacing crisis resources when the app detects certain content in your messages;
• Quality and safety review — a short, named list of our clinicians and engineers reviews flagged MenoAI conversations and small random samples so the AI stays accurate and safe;
• A separately offered research study in which you choose to enroll through its specific Informed Consent, subject to that consent, the applicable protocol, and other legal or source requirements;
• Product analytics using non-health usage data, such as screens, taps, and errors. Our analytics events exclude health information except the connection details you approve for maintaining an app or device connection (Sections 4 and 8). Our analytics provider acts on our instructions, and support messages are access-restricted and are not used for product analytics. Quality and safety review is described above. We may also analyze Qualifying De-identified Data for the Permitted De-identified Uses below.

Permitted De-identified Uses. We may create, use, combine, retain, disclose, publish, license, sell, and otherwise commercialize Qualifying De-identified Data, including aggregate statistics and record-level de-identified datasets, for analytics; product and service development, improvement, and evaluation; research; development, training, testing, and evaluation of artificial intelligence and machine-learning systems; and commercial insights and data products. We may receive compensation for these activities.

Qualifying De-identified Data means information de-identified so that it no longer constitutes personal health information or consumer health data under applicable law.

We take reasonable measures to maintain Qualifying De-identified Data in de-identified form. We publicly commit to maintaining and using it in that form without attempting to re-identify individuals. We impose the recipient safeguards and contractual obligations required by applicable law.

These uses are subject to applicable law and binding source, study, and other commitments governing the information. No separate research-participation or commercial-use opt-in is required for these uses unless applicable law or those commitments require it.

We may provide Qualifying De-identified Data to academic and scientific researchers, life-sciences and healthcare organizations, technology and AI developers, analytics providers, and other commercial partners, and may publish qualifying insights. The no-sale and advertising restrictions below apply to personal information and consumer health data; the Permitted De-identified Uses are governed by this Section 5.

We do not:

• Sell personal information or consumer health data. Licensing or selling Qualifying De-identified Data is governed by the Permitted De-identified Uses above;
• Use your health data for third-party advertising, ad targeting, or ad measurement, or share it with advertising networks or data brokers;
• Include third-party advertising SDKs in the app;
• Use consumer health data to train general-purpose AI models. Qualifying De-identified Data may be used for the model-development purposes described above;
• Use geofencing around healthcare facilities — or anywhere else.

6. Your Rights Over Your Health Data

The in-app controls described here are available to every user; privacy rights provided by state law are honored as the law of your state requires:

• See it. Your tracked data, connected-device data, and everything MenoAI has noticed are visible inside the app.
• Delete it. You can delete individual symptom-log entries, individual MenoAI memories or all memories, or your entire account in the app. You may request deletion of individual MenoAI conversations at privacy@menohealth.ai; an in-app control is planned for a later update. Account deletion removes health data from live systems, including MenoAI conversations and Langfuse traces, within the time applicable law requires. Automated database backups age out on a fixed short cycle without restoration to live systems, and archived or backup copies are deleted as applicable law requires, including within six months under Washington’s applicable archive/backup rule. Legally required records are kept only as long as required. Deleting in the app and emailing privacy@menohealth.ai trigger the same process. Retention and use of Qualifying De-identified Data are described in Sections 5 and 7.
• Export it. You can request a portable copy of your health data by emailing privacy@menohealth.ai; we respond within the time applicable law requires.
• Withdraw consent. Per Section 4, immediately, in Settings.
• Ask who has it. You may request a list of the third parties with whom we have shared your consumer health data (Section 8 lists the categories; the list of specific recipients is available on request where state law requires).
• No retaliation. As state privacy laws require, we will not deny you the service, charge you more, or degrade your experience because you exercised a privacy right. Features that require certain data (for example, sleep insights require sleep data) simply don’t activate without it — that is a functional dependency, not a penalty.
• Appeal. If we decline a request, we will tell you why. Where your state’s law provides an appeal right, you may appeal by replying to our decision or emailing privacy@menohealth.ai. We respond to appeals within the time required by your state’s law — in Washington, within 45 days of receiving your appeal. If your appeal is denied, we will provide a way to contact your state Attorney General where the law so requires.

To exercise any right: in-app controls first (fastest), or email privacy@menohealth.ai. We will verify the request is really from you before acting on it. Authorized agents may act for you where state law provides.

7. Retention — How Long We Keep Things

• Tracked health data: for as long as you keep your account.
• MenoAI memories: kept until you erase them in the app, or until you delete your account.
• Chat transcripts with MenoAI: kept for as long as you keep your account, so your conversation history stays available to you (you can request deletion of individual conversations at privacy@menohealth.ai). The behind-the-scenes quality-and-safety records of these conversations held by our AI monitoring provider (Langfuse) are kept as long as your account is active and are erased when you delete your account, except where the law requires us to keep them.
• Connected-device data: disconnecting stops new collection and the connection-specific consent described in Section 4. Previously collected information is subject to any withdrawal, deletion, use, and retention requirements imposed by applicable law, the consent, or source terms; disconnection does not itself delete all previously collected records. You may separately request deletion.
• Telehealth visit and medication order records: booking references, visit status, provider identifiers, records of your plan, consultation and visit fees, and medication order history (medication, quantity, price, medication payments, and fill, shipment, and refill status) are kept for seven (7) years after the visit or order, or six (6) months for users located in Washington State.
• After account deletion: health data is removed from live systems within the time required by law. Automated backups age out on a fixed short cycle, and archived or backup copies are deleted as applicable law requires, including within six months under Washington’s applicable rule. We may retain Qualifying De-identified Data after account deletion or consent withdrawal and continue the Permitted De-identified Uses as permitted by applicable law and binding commitments governing the information.

We keep health data no longer than reasonably necessary for the purposes above.

8. Who We Share Health Data With — and Who We Don’t

We disclose health data to service providers acting on our instructions under contracts restricting their use, to an independent telehealth provider for a visit you request and information you approve (Section 9), to research partners for a separately offered study under its specific consent and required authorizations, and for the legal-process or business-transfer purposes stated below, in each case only as permitted by applicable law and any required consent. The service-provider categories and purposes are:

Cloud hosting & database

• Purpose: Storing and running the service
• Examples: Amazon Web Services (RDS database, S3 storage)

AI model providers

• Purpose: Powering MenoAI responses under signed agreements with Zero Data Retention — conversation content is not stored on the providers’ servers and is not used to train models
• Examples: OpenAI OpCo, LLC (OpenAI for Healthcare); Anthropic, PBC

AI conversation monitoring

• Purpose: Reviewing MenoAI conversations for quality, accuracy, and safety — direct identifiers (emails, phone numbers, addresses, account IDs) and other people’s names are removed before storage, your own first name may remain, medication names appear only as general categories, and internal IDs are salted hashes; records are kept while your account is active and erased on account deletion, except where the law requires retention
• Examples: Langfuse

Wearable data integration

• Purpose: Connecting your devices
• Examples: Terra

Payments & subscriptions

• Purpose: Managing your subscription and processing purchases on our web checkout (no health data — receipt and entitlement data only)
• Examples: RevenueCat, Apple, Google; Stripe, Inc. (web checkout)

Communications

• Purpose: Sending emails you’ve enabled (no health details in any email)
• Examples: SendGrid

Analytics

• Purpose: Product usage analytics — events designed and automatically checked to exclude health data, apart from the connection details you approve when linking an app (see below); as our contracted processor, PostHog may use what it receives only on our instructions. PostHog also hosts our customer-support inbox: if you write to our support team, your message — including anything health-related you choose to include — is held by the same provider under our signed agreement, is access-restricted to the team members who help you, and is not used for product analytics
• Examples: PostHog

Video delivery

• Purpose: Streaming library videos — Mux receives viewing and playback-quality information tied to a pseudonymous identifier and your network address, not your name, contact details, or health records
• Examples: Mux

Push notifications: OneSignal receives push tokens and notification delivery metadata, using Apple Push Notification service and Firebase Cloud Messaging as transports; it receives no health information. Tokens are no longer used when push is disabled and are deleted within thirty days after account deletion, as described in the Privacy Policy.

We do not share your health data with: advertisers or ad networks, data brokers, social media platforms, insurers, or employers. We do not use third-party tracking pixels on pages or screens where health data is present, and we do not use session-replay tools that record your screen. Which health apps and devices you choose to connect is itself treated as health information. The only connection details our analytics provider receives are the ones you agree to on the connection screen — which app you connected and whether the connection is working — used solely to keep it running.

Qualifying De-identified Data may be disclosed or commercialized for the recipients and purposes described in Section 5.

Legal process. If we receive a subpoena, warrant, or other legal demand for your data, we will disclose only what we are legally required to disclose.

Business transfer. If MenoHealth is acquired or merges, your health data remains subject to these Disclosures, and any material change requires the notice-and-consent process in Section 12.

Affiliates: MenoHealth currently has no affiliates, so no consumer health data is shared with affiliated entities.

9. Telehealth — Where the Wellness App Ends and Healthcare Begins

We do not provide professional healthcare service. If you request a telehealth visit through the app:

• What we send: when you book a visit, we send the clinical network (MDI Medical Group PC and its affiliated professional entities) a booking reference and, only if you separately choose, a summary of your tracked data. You enter your intake information, including your identity, contact details, medical answers, and identification photo, directly with the clinical network in its own intake inside our app. We do not collect or store it.
• What they hold: the clinical record of your visit — including prescriptions — is held by the clinicians under their own legal obligations (including HIPAA, where applicable).
• What comes back: the visit status, the clinical network’s identifiers for you, and a notice when your clinician sends you a message. Your messages with your clinician take place on the clinical network’s page inside our app, and we do not receive their content. If you order a prescribed medication through the app, the clinical network also sends us the status of the order and shipment and the details for your medication tracker and refill reminders (medication name, strength, quantity, price, fill and shipment status, and refill dates), which it receives from the pharmacy. We do not receive your clinical records from the telehealth provider.
• Where prescriptions go: if a clinician prescribes a medication that you choose to fill through the app, your clinician sends the prescription and the details needed to fill and ship it (such as your name, date of birth, shipping address, and contact information) to Honeybee Health, Inc., an independent licensed pharmacy that handles them under its own privacy notice and applicable pharmacy law. We do not send your information to the pharmacy, and the pharmacy does not send your information to us. When you order through the app, the ordering screen shows two separately stated amounts, the pharmacy’s price for the medication, which Honeybee sells to you and we collect as its limited payment agent and forward to it, and our flat care coordination fee, which is the same for every medication. We approve the order through the clinical network’s platform, and the clinical network sends us the order details needed to manage refills and delivery (medication, quantity, price, and fill, shipment, and refill status), which it receives from the pharmacy. If you fill your prescription at another pharmacy, we receive none of that information.
• Who pays the clinician: you pay us for your plan. At each visit you pay the clinical network’s consultation fee, which we collect on its behalf as an administrative service and forward to it in full, and our flat visit fee, which a plan credit may waive. The consultation fee is the same whether or not anything is prescribed, and our fees never change based on what is prescribed. Neither the clinicians nor the pharmacy bill you separately, because we collect their fees for them and pass them along.
• What we don’t do: we do not use clinical-visit content for app analytics, and clinicians do not get browsing access to your app data beyond what you approved at booking.

10. Security

Health data is encrypted in transit and at rest. Access inside MenoHealth is role-restricted and logged, and access to MenoAI conversation records is limited to a named list of team members with two-factor sign-in, reviewed quarterly. Our team is trained on these data-handling rules — including the rule that user health data must not be entered into consumer chatbot tools outside our protected pipeline. Consent state is enforced on our servers — the app cannot save MenoAI memories for a user who hasn’t turned memory on, because the server refuses the write. No method of storage or transmission is completely secure, but these safeguards are designed to protect your information. If a security incident affects your health data, we will notify you and applicable regulators as required by law, without unreasonable delay.

11. Children

MenoHealth is for adults. It is not directed to anyone under 18, and we do not knowingly collect health data from anyone under 18. If we learn we have, we will delete it.

12. Changes to These Disclosures

We may update this document from time to time. We will communicate material changes in the app and, where appropriate, by email. We will provide any notice and obtain any consent or authorization required by applicable law or binding commitments governing the information before applying the relevant change. Prior versions are archived.

13. State-Specific Notices

Washington and Nevada. This document is our consumer health data privacy policy. Covered consumers have rights to confirm collection, sharing, or sale; access data and required recipient information; withdraw consent; and request deletion, subject to applicable law. We do not sell consumer health data. Qualifying De-identified Data is addressed in Section 5. These laws may cover in-state collection as well as residents. We do not use geofencing.

California. Where the CCPA/CPRA applies, health information is sensitive personal information, and we honor applicable rights to limit its covered uses and disclosures, together with access, deletion, correction, portability, sale/sharing opt-out, and non-discrimination rights. We do not sell personal information or share it for cross-context behavioral advertising. Qualifying De-identified Data is addressed in Section 5.

Other states with comprehensive privacy laws. Where applicable law requires consent to process sensitive or consumer health data, we obtain the required choice before that processing begins. We honor the access, correction, deletion, portability, opt-out, and appeal rights each applicable law provides.

Maryland. We comply with the Maryland Online Data Privacy Act’s requirements for sensitive data where applicable. Qualifying De-identified Data is addressed in Section 5.

Connecticut. We comply with applicable consumer health and sensitive-data requirements and honor the consent and privacy rights those laws provide. Qualifying De-identified Data is addressed in Section 5.

Texas. We comply with applicable sensitive-data and medical-information requirements, including Chapters 541 and 181 where they apply, and obtain consent or authorization when required. Qualifying De-identified Data is addressed in Section 5.

14. Contact

MenoHealth, Inc. Privacy requests: privacy@menohealth.ai General: support@menohealth.ai Mail: MenoHealth, Inc., Attn: Privacy, 11555 Heron Bay Blvd., Suite 200, Parkland, FL 33076

If you are unsatisfied with our response, you may contact your state Attorney General’s office. Washington residents: www.atg.wa.gov.