Ad Tech Compliance
Connecticut consumer health data rules for advertisers: the CTDPA, the 2025 and 2026 amendments, and geofencing
Published · Last updated
Next scheduled review:
Connecticut regulates consumer health data inside its Data Privacy Act. Since 1 October 2023, anyone doing business there needs consent to sell health data and may not geofence within 1,750 feet of mental, reproductive or sexual health facilities. Since 1 July 2026, processing health data needs both consent and reasonable necessity (Conn. Gen. Stat. 42-526).
Connecticut's rules come in two layers. One section binds every person, with no size threshold. The other layer is the general privacy act, which treats health data as sensitive data. Three Public Acts since 2023 have changed both. The state health privacy law tracker places Connecticut next to the other states; this page reads the current text.
Contents
Key facts
- Health rules started on 1 October 2023. Public Act 23-56 was approved on 26 June 2023 (Public Act 23-56). Public Act 23-204 moved its health sections from 1 July to 1 October 2023 (statute history notes, chapter 743jj).
- The definition widened on 1 July 2026. Consumer health data now covers data used to identify a health "condition, diagnosis or status", not only a condition or diagnosis (Public Act 25-113, section 5).
- Size thresholds no longer shield sensitive data. From 1 July 2026, any business that processes sensitive data is in scope, and the volume floor fell to 35,000 consumers (Public Act 25-113, section 6).
- Precise location data cannot be sold. From 1 October 2026, no controller and no third party may sell any consumer's precise geolocation data (Public Act 26-64, sections 14 and 15).
- Only the Attorney General enforces. A violation is an unfair trade practice enforced solely by the AG, with no private right of action (Conn. Gen. Stat. 42-525). Wilful violations carry up to $5,000 each (Conn. Gen. Stat. 42-110o).
Definition
Consumer health data, from 1 July 2026, means "any personal data that a controller uses to identify a consumer's physical or mental health condition, diagnosis or status", including gender-affirming health data and reproductive or sexual health data (Conn. Gen. Stat. 42-515(9), as amended by Public Act 25-113). Before that date the words "or status" were absent. The glossary compares the term across states.
A consumer health data controller is any controller that decides the purpose and means of processing consumer health data (42-515(10)). That label matters because the health data section and the cure rules use it.
Two layers of rules
The first layer is section 42-526. It applies to "persons that conduct business in this state" or target residents, regardless of the act's usual thresholds (42-526(a)(2)). The second layer is the general CTDPA, which treats consumer health data as sensitive data (42-515, sensitive data).
7 of 7 rows
No sale or offer to sell consumer health data without consent | 42-526 | Any person in scope of 42-526(a)(2) | |
No geofence within 1,750 feet of a mental health or reproductive or sexual health facility for the listed purposes | 42-526 | Same | |
Staff and contractors with access must owe confidentiality; processors need a 42-521 contract | 42-526 | Same | |
No processing of sensitive data without consent; from 1 July 2026 also only where reasonably necessary | CTDPA | Controllers meeting 42-516 | |
Opt-out of targeted advertising and sale, including by preference signal | CTDPA | Same | |
Data protection assessment for targeted ads, sales and sensitive data | CTDPA | Same | |
No sale of precise geolocation data, from 1 October 2026 | CTDPA | Controllers and third parties |
No sale or offer to sell consumer health data without consent
- Layer
42-526
- Who it binds
Any person in scope of 42-526(a)(2)
- Citation
No geofence within 1,750 feet of a mental health or reproductive or sexual health facility for the listed purposes
- Layer
42-526
- Who it binds
Same
- Citation
Staff and contractors with access must owe confidentiality; processors need a 42-521 contract
- Layer
42-526
- Who it binds
Same
- Citation
No processing of sensitive data without consent; from 1 July 2026 also only where reasonably necessary
- Layer
CTDPA
- Who it binds
Controllers meeting 42-516
- Citation
Opt-out of targeted advertising and sale, including by preference signal
- Layer
CTDPA
- Who it binds
Same
- Citation
Data protection assessment for targeted ads, sales and sensitive data
- Layer
CTDPA
- Who it binds
Same
- Citation
No sale of precise geolocation data, from 1 October 2026
- Layer
CTDPA
- Who it binds
Controllers and third parties
- Citation
Table by AdSovereign, CC BY 4.0.
Exemptions. Section 42-526 does not apply to HIPAA covered entities and business associates, financial institutions or data subject to GLBA, colleges, state bodies and some others (42-526(b)). Unlike the general act, the list in 42-526(b) does not name nonprofit organizations. Hospitals and plans therefore fall under HIPAA rather than this section; the HIPAA marketing rule covers their communications.
Consent and necessity for health data in ad flows
What the statute says. Before 1 July 2026, a controller could not process sensitive data "without obtaining the consumer's consent" (42-520(a)(4)). Public Act 25-113 rewrote the duty. A controller may not process sensitive data "unless such processing is reasonably necessary in relation to the purposes for which such sensitive data are processed and without obtaining the consumer's consent" (42-520(a)(1)(D), as amended). We read that as requiring both conditions; the point is listed for counsel.
Consent must be a "clear affirmative act". Accepting broad terms, hovering over or closing content, and agreement obtained through dark patterns do not count (42-515(7)). Consumers must be able to revoke it as easily as they gave it.
Targeted advertising has a defined scope. It means ads chosen from data about a person's activity across nonaffiliated sites or apps. Ads based on activity on the controller's own sites, on the current page or search, and processing solely to measure frequency, performance or reach are excluded (42-515, targeted advertising). Consumers may opt out of targeted advertising and sales, including through an opt-out preference signal (Public Act 25-113, section 9).
An example. A fertility app user in Hartford logs cycle data. The app wants to show that user ads on other sites for its premium tier. The cycle data is consumer health data and so sensitive data. Using it to pick ads on other sites is targeted advertising, which needs consent and, since July 2026, reasonable necessity for a disclosed purpose (42-520, as amended). Showing the same upgrade offer inside the app is excluded from "targeted advertising".
What practitioners do (practice, not law). Many Connecticut flows pass consent and opt-out status in the Global Privacy Platform (GPP) string so that a supply-side platform (SSP) and its buyers can read it. The GPP and TCF implementation guide shows the fields.
The geofence ban and the new location sale ban
What the statute says. No person may "use a geofence to establish a virtual boundary that is within one thousand seven hundred fifty feet of any mental health facility or reproductive or sexual health facility". The ban applies to identifying, tracking, collecting data from or notifying a consumer about the consumer's health data (42-526(a)(1)(C)). A covered facility is one where at least 70% of services are mental health, or reproductive or sexual health, care (42-515(23) and (36)). General hospitals and pharmacies are not named.
From 1 October 2026 a second rule applies. "No controller shall sell any consumer's precise geolocation data", and the same words bind third parties (Public Act 26-64, sections 14 and 15). Precise means within a radius of 1,750 feet. The ban has no consent exception in its text and is not limited to health locations.
Data brokers. Public Act 26-64 also bars data brokers from selling or licensing brokered personal data on or after 1 January 2027 unless registered with the Department of Consumer Protection (section 2).
Who must comply after July 2026
Before. The general act applied to businesses that handled data of at least 100,000 consumers, or 25,000 with more than a quarter of revenue from data sales (42-516).
After. From 1 July 2026 it applies to businesses that handled data of at least 35,000 consumers, that "control or process consumers' sensitive data", or that offer personal data for sale (Public Act 25-113, section 6). A small telehealth start-up or a niche health publisher with a few hundred Connecticut users can now be a controller under the full act. Section 42-526 already reached them.
Enforcement and what the Attorney General has said
The statute. The Attorney General has "exclusive authority" to enforce. From October 2023 to the end of 2024, the AG had to offer health data controllers a 60-day cure where a cure was possible. Since 1 January 2025 a cure is discretionary, and "the sensitivity of the data" is one factor (42-525(b)-(c)). Nothing in these sections creates a private right of action, and the private CUTPA action in 42-110g does not apply (42-525(d)-(e)). Under CUTPA, the AG may recover up to $5,000 per wilful violation and up to $25,000 per violation of an injunction (42-110o).
The AG's reports. The third annual CTDPA enforcement report, covering 2025, was released in February 2026 (Troutman Pepper Locke, 10 February 2026). It describes an investigation of a hormonal fertility tracking app whose privacy notice did not account for the health data rules. It also takes the position that processing sensitive data without telling consumers about heightened risks is unlawful, even when they volunteer it.
The report urges the legislature to remove entity-level exemptions, including the one for HIPAA covered entities. Kelley Drye's summary adds an investigation of a data broker offering advertising SDKs, cookie-banner sweeps and testing of opt-out signals (Kelley Drye, 2 March 2026).
We found no published settlement under 42-526 as of 9 November 2026.
Dates that matter
8 of 8 rows
26 Jun 2023 | Public Act 23-56 (SB 3) approved | |
1 Oct 2023 | 42-526 and health definitions take effect (date set by Public Act 23-204) | |
31 Dec 2024 | Mandatory 60-day cure ends | |
1 Jul 2026 | Public Act 25-113: "status" added, 35,000 threshold, sensitive data trigger, necessity plus consent | |
24 Jun 2025 | Public Act 25-113 (SB 1295) approved | |
27 May 2026 | Public Act 26-64 (SB 4) approved | |
1 Oct 2026 | Sale of precise geolocation data banned | |
1 Jan 2027 | Data brokers must be registered to sell or license brokered data |
26 Jun 2023
- Event
Public Act 23-56 (SB 3) approved
- Source
1 Oct 2023
- Event
42-526 and health definitions take effect (date set by Public Act 23-204)
31 Dec 2024
- Event
Mandatory 60-day cure ends
- Source
1 Jul 2026
- Event
Public Act 25-113: "status" added, 35,000 threshold, sensitive data trigger, necessity plus consent
- Source
24 Jun 2025
- Event
Public Act 25-113 (SB 1295) approved
- Source
27 May 2026
- Event
Public Act 26-64 (SB 4) approved
- Source
1 Oct 2026
- Event
Sale of precise geolocation data banned
- Source
1 Jan 2027
- Event
Data brokers must be registered to sell or license brokered data
- Source
Table by AdSovereign, CC BY 4.0.
What the text means for each part of an ad stack
7 of 7 rows
Health segments on third-party media | 42-520 as amended | Consent and reasonable necessity for a disclosed purpose |
Audience or data sales | 42-526(a)(1)(D) | Consent before any sale of consumer health data |
Location data products | PA 26-64 | No sale of precise geolocation data from 1 October 2026, health-related or not |
Location campaigns | 42-526(a)(1)(C) | No geofence within 1,750 feet of covered facilities for the listed purposes |
Opt-out handling | 42-518; 42-520 | Honour opt-out preference signals for targeted ads and sales |
Vendor contracts | 42-521; 42-526(a)(1)(B) | Processor contract before a processor touches health data |
Assessments | 42-522 | Documented assessment for targeted advertising, sales and sensitive data |
Health segments on third-party media
- Section
42-520 as amended
- What changes under the text
Consent and reasonable necessity for a disclosed purpose
Audience or data sales
- Section
42-526(a)(1)(D)
- What changes under the text
Consent before any sale of consumer health data
Location data products
- Section
PA 26-64
- What changes under the text
No sale of precise geolocation data from 1 October 2026, health-related or not
Location campaigns
- Section
42-526(a)(1)(C)
- What changes under the text
No geofence within 1,750 feet of covered facilities for the listed purposes
Opt-out handling
- Section
42-518; 42-520
- What changes under the text
Honour opt-out preference signals for targeted ads and sales
Vendor contracts
- Section
42-521; 42-526(a)(1)(B)
- What changes under the text
Processor contract before a processor touches health data
Assessments
- Section
42-522
- What changes under the text
Documented assessment for targeted advertising, sales and sensitive data
Table by AdSovereign, CC BY 4.0.
Maryland takes the stricter route of banning sensitive data sales outright; see Maryland's MODPA sensitive data rules. New York's pending bill would add a separate authorization regime; see New York's Health Information Privacy Act. The planned US state privacy laws tracker and the ad tech compliance hub cover the rest.
FAQ
When did Connecticut's consumer health data rules take effect?
What counts as consumer health data under the CTDPA?
Do Connecticut's health data rules apply to HIPAA covered entities?
Can an advertiser geofence a clinic in Connecticut?
Can consumers sue under the CTDPA?
How this works on owned infrastructure
Connecticut now asks two questions of every health-based campaign: did the person consent, and is the processing reasonably necessary for a disclosed purpose. From October 2026 it adds a hard stop on selling precise location. On a rented stack those checks live in a vendor's settings, and an advertiser often cannot see whether a location feed was bought or sold. AdSovereign is designed so that location ingestion, audience rules and outbound data feeds run on infrastructure the operator controls, with each feed tagged by purpose. A Connecticut rule can then block a precise-location export at the connector, and the block is logged. The integrations page lists the connectors, and security describes the logs.
Sources
- Connecticut General Assembly, General Statutes chapter 743jj, Data Privacy and Security, sections 42-515 to 42-526 with history notes (2025 revision), checked 9 November 2026. https://www.cga.ct.gov/current/pub/chap_743jj.htm
- Connecticut General Assembly, 2026 Supplement to the General Statutes, chapter 743jj (amendments from the 2025 session). https://www.cga.ct.gov/2026/sup/chap_743jj.htm
- Connecticut General Assembly, Public Act 25-113 (SB 1295, 2025, approved 24 June 2025), sections 5 to 18 effective 1 July 2026. https://www.cga.ct.gov/2025/ACT/PA/PDF/2025PA-00113-R00SB-01295-PA.PDF
- Connecticut General Assembly, Public Act 26-64 (SB 4, 2026), "An Act Concerning Consumer Privacy and Protection" (approved 27 May 2026). https://www.cga.ct.gov/2026/ACT/PA/PDF/2026PA-00064-R00SB-00004-PA.PDF
- Connecticut General Assembly, Public Act 23-56 (SB 3, 2023), "An Act Concerning Online Privacy, Data and Safety Protections" (approved 26 June 2023). https://www.cga.ct.gov/2023/ACT/PA/PDF/2023PA-00056-R00SB-00003-PA.PDF
- Connecticut General Assembly, General Statutes chapter 735a, Unfair Trade Practices, section 42-110o. https://www.cga.ct.gov/current/pub/chap_735a.htm
- Troutman Pepper Locke, "2025 CTDPA Enforcement Report Issued" (10 February 2026). https://www.troutmanprivacy.com/2026/02/2025-ctdpa-enforcement-report-issued/
- Kelley Drye, "Connecticut's Privacy Report Highlights Rising Expectations for Businesses" (2 March 2026). https://www.kelleydrye.com/viewpoints/blogs/ad-law-access/connecticuts-privacy-report-highlights-rising-expectations-for-businesses
Changelog
- 9 November 2026: page created from the state tracker's Connecticut entry; effective date resolved from the statute history notes; Public Acts 25-113 and 26-64 read in full.