Oohvie Consumer Health Data Privacy Policy
Effective date: November 3, 2026
Last updated: November 3, 2026
Operator: HealthLynked Corp.
Website: https://oohvie.com
1. Scope and purpose
This Consumer Health Data Privacy Policy describes how Oohvie, a product of HealthLynked Corp. (“Oohvie,” “HealthLynked,” “we,” “us,” or “our”), collects, uses, processes, discloses, retains, and protects consumer health data through the Oohvie website, mobile application, and related functionality. It supplements the Oohvie general Privacy Policy and is intended to address applicable requirements, including the Washington My Health My Data Act and Nevada’s consumer health data privacy law. Rights and exceptions vary by jurisdiction and may also depend on whether information is governed by HIPAA or another specific law.
2. Consumer health data categories
Depending on features used and information supplied, we collect or generate information linked or reasonably linkable to an individual concerning: (a) menstrual health—first day of the last period, cycle start and end dates, cycle length, bleeding patterns, missed or irregular periods, cramps, and menstrual symptoms; (b) fertility and ovulation—estimated ovulation dates, fertile-window estimates, test or body-temperature observations entered by users, and reproductive planning goals; (c) contraception and medications—reported contraceptive methods, birth control pill names or types, schedules, reminder choices, logged use or missed doses when supported, hormonal treatments, and other voluntarily entered medication information; (d) pregnancy and reproductive health—pregnancy-related entries, testing, family planning, fertility treatment information, and reproductive symptoms; (e) symptoms and wellness—mood, pain, weight or other measurements voluntarily entered, health notes, and health-related experiences; (f) derived information—predictions, insights, or trends inferred from tracking data; (g) requested healthcare services—information associated with an appointment or telehealth request; and (h) health-related analytics and interaction data, including event names and attributes revealing period logging, symptom entries, birth-control or medication choices, app-screen views, timestamps, device or application identifiers, and website activity associated with reproductive-health content; and (i) other technical information that reveals or reasonably permits health inferences.
Not every category is collected from every user. Features may differ by version and availability. We do not collect categories or use data for additional undisclosed purposes where separate disclosure and affirmative consent are required by law.
3. Categories of sources
We obtain consumer health data from: information you enter or upload; your use of available health-tracking features; calculations generated by Oohvie from information you supply; optional HealthLynked connections or user-directed transfers; healthcare professionals or connected services involved in a service you request, where authorized; and health-feature analytics generated when you interact with Oohvie, as well as website measurement and session-interaction technologies that can reveal health interests or activities. We do not infer that every connected system automatically delivers its records to Oohvie.
4. Purposes of collection and processing
We collect and process consumer health data to provide user-requested period, symptom, contraception, and pregnancy-related tracking; produce estimated cycle and fertility information; provide available reminders; maintain accounts and their security; support an optional user-directed transfer of records to HealthLynked; carry out provider-specific sharing authorized through HealthLynked; respond to requests; and comply with law.
Product analytics and website measurement are additional processing purposes. Oohvie uses third-party technologies to measure app features used, engagement, navigation, performance, errors, and user interactions, and to inform product development. Those technologies receive some events relating to reproductive health, not merely general diagnostic data. Processing can include collection, generation, transmission to outside technology companies, association with device or account identifiers, storage, analysis, retrieval, correction, or deletion.
Processing for unrelated advertising, independent scientific research, or general-purpose AI-model training is not automatically authorized because a user participates in tracking or accepts Terms of Use; additional notices and separate consent may be required by law.
5. Automatic account creation is not automatic health-record transfer
Creating an Oohvie account also creates a corresponding HealthLynked account for account integration. Oohvie does not automatically transfer a user’s menstrual, fertility, contraception, symptom, pregnancy-related, or other reproductive health records into the user’s HealthLynked patient health record. A user must choose to make that health-record transfer.
This restriction on transfer to a HealthLynked patient record does not mean reproductive-health activity never reaches other companies. Some health-related app events and website interactions are sent to analytics providers, as described in Sections 7 and 10. Such disclosures are separate from a user-directed transfer of a health record and from healthcare provider access permissions.
6. User-directed transfer and separate provider permissions
You may choose to transfer selected Oohvie reproductive health records to your HealthLynked personal health record. An elective transfer is a distinct step from authorizing any particular provider to access information. Through HealthLynked, users can select the healthcare providers and the specific records or categories of information those providers may access, subject to the actual available sharing controls. Sharing records with one provider does not automatically authorize access by all providers. Changes to permissions generally govern future availability, not records already lawfully received and retained by a provider. Where consent to share is required, it is separate from consent to collect.
7. Categories of data shared and recipients
Provider-directed record sharing: When a user elects to transfer information into a HealthLynked patient health record, the categories may include menstrual histories, fertility and ovulation estimates, contraception details, pregnancy-related information, symptoms, and other selected health records. The user separately controls the providers and records authorized for access through available HealthLynked settings. An Oohvie account created during registration does not itself give providers access to Oohvie reproductive health records.
Third-party analytics disclosures: Some reproductive health activity events are sent to external vendors even when the user has not transferred records into a HealthLynked patient health record. Mixpanel receives events involving period logging, symptoms, and birth-control choices; associated information may include event names and attributes, identifiers, screens used, and timestamps. Firebase Analytics also receives app measurement information and supports advertising identifiers in the present configuration. Website providers Google Analytics 4 and Microsoft Clarity may receive navigation events, page URLs, interaction details, device/browser information, and session-interaction or session-replay data; health-related website activity may reveal sensitive interests or information.
Recipient categories: (1) app analytics and engagement measurement providers (Mixpanel and Google Firebase Analytics); (2) website analytics and interaction-recording providers (Google Analytics 4 and Microsoft Clarity); (3) crash reporting, technical diagnostics, support, and security service providers, where used; (4) push-notification and messaging delivery providers, where used; (5) hosting, infrastructure, and account authentication services; (6) healthcare professionals and healthcare service organizations involved in a service the user requests or authorizes; and (7) authorities or other recipients when lawfully required or permitted.
Affiliates: Oohvie is operated by HealthLynked Corp., rather than by a separate Oohvie legal entity. This notice does not identify any separate corporate affiliate as an additional recipient of Oohvie consumer health data. We will update the applicable recipient disclosures and obtain legally required consent before introducing additional categories of sharing or recipients.
The exact data received varies by recipient, technology, and feature. The inclusion of a recipient here does not establish that the recipient has no independent rights to use data or that any particular disclosure has already received legally required consent. We do not describe the data sent to analytics companies as limited to non-health technical information.
8. Separate consent, withdrawal, and no sale
Collection of consumer health data generally requires affirmative consent for a specified purpose unless it is necessary to provide a product or service requested by the consumer or another applicable exception exists. Sharing consumer health data generally requires separate and distinct affirmative consent, unless an exception applies. Where consent is required, the request must identify the relevant data categories, purposes, recipient categories, and available withdrawal mechanism.
This Policy and acceptance of the Terms of Use are not consent. Choosing to transfer a record into HealthLynked or authorize a healthcare provider is not authorization to disclose health activity to an analytics or advertising company. Analytics disclosures described here are occurring as part of the reported implementation; disclosure of those practices does not establish that the separate consent required by law has been obtained. You may request cessation of eligible future collection or sharing, withdraw applicable consent, or seek deletion using the procedures in Section 15.
Oohvie does not offer completed personal health records for direct purchase as a standalone commercial database. However, disclosures to analytics and measurement providers may qualify as statutory sharing or a “sale” depending on actual processing, applicable legal definitions, vendor rights, and any valuable consideration involved. Where a law requires a distinct written authorization for a sale, that authorization must be obtained before a covered sale unless a lawful exception applies.
9. Research, AI, and service improvement
Oohvie may use information to calculate the predictions, reminders, and trends expressly requested by a user. Routine operation of a prediction feature is not authorization to use identifiable reproductive health histories for unrelated scientific research, third-party advertising, or training a general-purpose AI model. We may analyze aggregated or lawfully de-identified information to improve performance, security, and features, subject to applicable safeguards. Any materially new purpose involving identifiable consumer health data for external research, general AI-model training, or other nonessential uses will require the additional notice and affirmative consent required by applicable law before it begins. The company may update its methods and vendors to provide disclosed functions without promising to retain any specific algorithm or vendor indefinitely.
10. Analytics and cross-site health data collection
Cross-site consumer health data collection: YES. Third-party providers may collect consumer health data or information revealing health interests over time and across different websites or online services when a person uses Oohvie. The presence of app analytics, website tags, and session-interaction technologies means health-related activity can leave Oohvie systems even without a user-directed transfer to a HealthLynked patient record.
App analytics — Mixpanel: Receives events concerning menstrual-period logging, symptom activity, and birth-control choices, together with information such as event metadata, time, device/app identifiers, and screen or feature context.
App analytics — Google Firebase Analytics: Is active in Oohvie and may collect app events, identifiers, and device information. The current SDK configuration has support for advertising identifiers. That support does not by itself prove any particular advertising identifier was sent or used for cross-app targeting.
Website analytics — Google Analytics 4: May collect pages and URLs visited, interaction and navigation events, device/browser information, and other measurement signals. Visits to reproductive-health pages may reveal health interests or activities.
Website interaction measurement — Microsoft Clarity: May collect clicks, scrolling, page interactions, browser/device details, and session-interaction or replay information. Session data can reveal health-related context depending on the content and fields captured.
Other recipient categories: Crash and diagnostics providers and push/message delivery vendors, when used, may receive error details, device or delivery identifiers, message metadata, and potentially health-related context depending on the information transmitted.
The extent to which an individual vendor correlates data across services depends on its configuration and legal rights; this Yes disclosure is not a statement that every vendor uses health data for targeted advertising. Where applicable law requires separate affirmative consent, authorization, or other controls, a published disclosure alone is insufficient and does not eliminate those obligations.
11. Children’s privacy and eligibility
Oohvie is intended for adults 21 years of age or older. Individuals younger than 21 should not register or use Oohvie. We may restrict or close an account that does not meet eligibility requirements, subject to applicable law. If an underage user provides personal information, we will address any applicable privacy and deletion obligations. The intended age requirement is not, by itself, a statement that every version of the app automatically verifies a user’s age.
12. Security, service providers, and location
We recognize that reproductive health data is highly sensitive. Oohvie relies on technology services for operation, measurement, support, communications, and security. We are responsible for adopting administrative, technical, and organizational protections appropriate to applicable law and for complying with legal requirements for processing arrangements, access restrictions, and service-provider use. No online system is completely immune to errors, misuse, or unauthorized access.
Information may be processed in the United States and other countries in which Oohvie’s technology providers operate. Applicable legal protections and contractual requirements apply to international processing. This Policy does not make an unconditional representation that every service provider is located exclusively within one country.
13. Retention, linked accounts, and deletion
We retain information for the disclosed purposes and for lawful operational needs, security, dispute resolution, and legal obligations, subject to data minimization and consumer health data retention limitations. You may request deletion of eligible Oohvie consumer health data. Your Oohvie account and automatically created HealthLynked account are distinct for account administration; deleting records in Oohvie does not by itself guarantee deletion of information you previously elected to transfer to HealthLynked or that a provider lawfully received. We will explain the appropriate request route and coordinate deletion obligations for information we control. We will not claim that a backup, clinical, or legally retained record was immediately erased when lawful exceptions or phased removal apply.
For authenticated Washington deletion requests, we will comply with the statutory response and deletion requirements, including notifying applicable recipients where required and addressing archived or backup information within permitted deadlines, generally no more than six months after authentication where the law permits delayed backup deletion. For Nevada, applicable active-record deletion must generally occur within 30 days after authentication, required recipients must be notified, and backup or archival deletion delays cannot exceed the period authorized by Nevada law (up to two years in specified circumstances). Applicable statutory exceptions may permit limited retention.
14. Consumer rights
Subject to law and valid exceptions, you may request confirmation of whether we collect, share, or sell consumer health data; access to eligible records; information about applicable recipients, including contact mechanisms where required; cessation of future collection or sharing; withdrawal of consent; deletion; review or correction through available account controls or applicable legal rights; and an appeal when we decline to act on an eligible request. We will not unlawfully discriminate against you for exercising these rights.
15. How to make a request
Send requests to [email protected] or use https://oohvie.com/contact/ or applicable account privacy controls. Describe the right being exercised without including unnecessary medical detail in unsecured email. We may request information reasonably necessary to authenticate your identity or authority. We will provide a reasonably secure process for requests. We will not require a Washington consumer to open a new account solely to exercise rights when prohibited by law.
Washington: For requests governed by Washington’s My Health My Data Act, we generally respond without undue delay and within 45 days after receiving the request, with one additional period of up to 45 days if legally justified and timely notice is provided. Other statutory deadlines and requirements for authentication, deletion, recipient notices, and fees apply.
Nevada: For requests governed by Nevada’s consumer health data law, we generally respond without undue delay and within 45 days after authentication, with a permitted extension of no more than 45 additional days upon timely notice when justified. The separate Nevada authenticated deletion deadline stated above also applies.
16. Appeals
You may appeal a qualifying refusal by writing to [email protected] with the subject line Consumer Health Data Privacy Appeal and identifying the original request. We will respond to appeals within the time required by applicable law, including 45 days for qualifying Washington and Nevada requests. If an appeal is denied, we will explain the decision and provide regulator contact information when required.
17. Government requests, geofencing, and breach notifications
We review requests by public authorities or other parties for reproductive health information under applicable law. We will not engage in geofencing practices prohibited by applicable consumer health privacy laws.
When a potential security incident or unauthorized disclosure is identified, we will assess the facts and determine whether notice or other action is required under applicable law, including, where relevant, the FTC Health Breach Notification Rule and state security-breach laws. A software vulnerability does not necessarily establish that a reportable breach has occurred, and notification obligations depend on the circumstances and applicable law. Where legally required, notices will be provided in the required time and manner.
18. Material changes and contact
We may update this Policy as permitted by law to address new functionality, vendors, security practices, and legal changes. We will notify affected users of material changes as required, and will obtain new affirmative consent before collecting or sharing additional categories of health data, introducing additional recipient categories or separate affiliates, or using data for additional purposes when applicable law requires it. The current effective date will appear above. Contact: Oohvie — HealthLynked Corp.; website: https://oohvie.com; secure request/contact page: https://oohvie.com/contact/; privacy email: [email protected].