Creates provisions relating to the use of reproductive or sexual health application information

2026 Regular Session Introduced by Eric Woods

HB 2735 would regulate how reproductive/sexual health app data can be collected, stored, shared, and disclosed, strengthening user consent and data protections.

Referred: Emerging Issues(H)

#healthcare #lawenforcementofficersandagencies #statedepartments

Summary of HB 2735 (Missouri, 2026)

Purpose and intent

HB 2735 creates provisions relating to the use of reproductive or sexual health application information. The bill appears aimed at regulating how data gathered by reproductive or sexual health apps can be accessed, used, or disclosed, with a focus on consumer protections and privacy related to sensitive health information.

Key provisions and changes

Privacy framework for health app data: The bill establishes rules governing the collection, storage, sharing, and use of information generated by reproductive or sexual health applications. It addresses how this data may be utilized by third parties, including service providers, advertisers, researchers, and potentially employers or insurers.

Restrictions on disclosure: The bill sets parameters around when and how such data can be disclosed without consumer consent. This may include prohibitions or require specific consent for certain purposes (e.g., targeting advertising, data brokers, or employment/insurance decisions).

Consumer consent and control: Likely provisions require explicit consent for sensitive data processing, and may grant individuals rights to access, correct, or delete their data held by apps or data processors.

Data security requirements: The bill may impose minimum security standards for the storage and transmission of reproductive or sexual health data to reduce risk of breaches or unauthorized access.

Definitions: The measure defines terms related to reproductive or sexual health information, applications, data, and possibly terms like "sensitive personal data" or "health data" to ensure clear scope.

Enforceability and penalties: Provisions could specify enforcement mechanisms, violations, and penalties for noncompliance, potentially including civil penalties or injunctive relief.

Who would be affected

Users of reproductive or sexual health apps: Individuals whose data are collected, stored, or processed by such apps would gain strengthened privacy protections and certain rights regarding their data.

app developers and data processors: Companies and contractors handling sensitive health information would be subject to the new consent, disclosure, security, and reporting requirements.

third-party partners: Advertisers, analytics providers, researchers, or affiliates that access or receive app data may face new restrictions or need to obtain consent.

insurers and employers (potentially): If the bill restricts use of health app data, entities that historically used health data for underwriting or employment decisions could be affected.

Procedural and timeline aspects

Prefiled: The bill was prefiled on January 6, 2026.

First reading: January 7, 2026.

Second reading: January 8, 2026.

Referred to committee: Emerging Issues (H) on May 15, 2026.

Next steps: If advanced, the bill would typically proceed to further committee hearings, potential amendments, and floor votes in the House, followed by consideration by the Senate and potential reconciliation. Specific deadlines would depend on the legislative calendar and session rules.

Additional notes

Co-sponsor: Eric Woods.

The summary reflects the bill’s stated focus on reproductive or sexual health app information; exact statutory text would specify precise definitions, permissible uses, consent mechanisms, data security standards, and enforcement details.