Guide · Published November 14, 2026 · Reviewed November 14, 2026 · Ingenious AI team · Not legal advice
Connecticut Data Privacy Act Thresholds: Who the Profiling Duties Actually Reach
The short answer: Connecticut's profiling duties reach businesses through three triggers, stated in the kit's checker data: processing the personal data of 35,000 or more Connecticut consumers a year (excluding payment-only data), processing sensitive data, or offering personal data for sale. A controller meeting any trigger owes the profiling set for covered decisions: the opt-out (since July 1, 2023, expanded July 1, 2026), outcome answers, and the data-protection assessment before heightened-risk profiling. The thresholds count Connecticut consumers — a business elsewhere with a Connecticut base can be in scope for that processing while a larger business with no Connecticut footprint is not.
Check your duties and dates — free Build your first notice — free
What is a controller, here? It is the CTDPA's term for the business that determines how personal data is processed — the deployer-side actor for profiling purposes. This guide covers the Act's thresholds and the profiling duties they switch on, as the kit's data states them; the Act's wider content (privacy notices, other consumer rights) is noted in the checker as existing beyond the automated-decision duties the kit covers.
Trigger one: 35,000 Connecticut consumers, payment-only excluded
The volume trigger is geographically specific: Connecticut consumers, counted per year, at 35,000 or more — with data processed solely for completing a payment transaction excluded from the count. Both qualifiers do work. A national business counts its Connecticut slice, not its national book; a payment processor's transaction-only data does not inflate the count toward coverage.
Measure the slice from the systems that hold it — accounts, orders, applications with Connecticut residency or service location as your data defines it — and record the method with the number. Residency definitions are a place where the count can be honestly arguable; the file should show which definition was used, so the finding can be re-derived and revisited.
Triggers two and three: sensitive data, and data for sale
The second trigger has no volume floor in the checker's statement: processing sensitive data brings the Act in. Businesses handling health-adjacent, biometric, or similarly sensitive categories should treat this trigger as a classification exercise over their actual data inventory — the same inventory the ADMT programme maintains — rather than a size question.
The third, offering personal data for sale, is a business-model trigger in the same family as California's revenue-share threshold but stated without a share: offering data for sale is the act that counts. Between them, the three triggers ensure that scale, sensitivity, and data-trading each independently ground coverage — a small, sensitive-data business and a large, ordinary-data business can both be in, for different reasons, owing the same profiling set.
Worked example: Constitution State Outfitters
Example — fictional business, real duty structure. Constitution State Outfitters is a fictional retailer with stores in Connecticut and a national web shop. Its thresholds working:
- Volume measured: Connecticut consumers whose data it processed in the year: 41,300 (store accounts, web orders with Connecticut delivery or account residency, applications) — over the 35,000 line, with payment-only transaction data excluded from the count as the checker specifies.
- Sensitive data: none processed beyond payment data handled by its processor — recorded as a not-met trigger on current facts, with the data inventory cited.
- Data for sale: the business does not offer personal data for sale — recorded as not met.
- Consequence: covered via the volume trigger. Its profiling-based product-recommendation-to-credit-offer workflow is assessed: the credit-offer decision is a covered effect, so opt-out intake (45-day standard), outcome answering, and a data-protection assessment are stood up.
- Employment track filed separately: its Connecticut hiring tool is analysed on the PA 26-15 track — no-defence rule noted as in force; notice pair diarised against the tool's replacement deployment date.
What the triggers switch on: the profiling set, already live
Coverage switches on duties that are already in force — the feature of Connecticut that most distinguishes it in planning. The opt-out has applied since July 1, 2023; since July 1, 2026 it reaches decisions where a person is nominally involved, and carries the outcome-question rights (question the result, learn the reasoning, review the data used) and, for housing, correct-and-re-run. Answers run on the 45-day standard with one extension and an appeal on denial. The assessment precedes heightened-risk profiling.
A business discovering its coverage late should therefore sequence honestly: stand up opt-out intake and outcome answering first (the live duties), complete assessments for ongoing profiling, and file the coverage finding with its measurement date — the date the position was established is itself a record fact. The full profiling walkthrough is at Connecticut Profiling Opt-Out Rights.
The employment track is separate from the thresholds analysis
Connecticut employers should keep two analyses distinct. The CTDPA thresholds govern the profiling track (consumer decisions). The employment track — the discrimination no-defence rule in force since October 1, 2026 and the AEDT notices for tools deployed on or after October 1, 2027 — arises under Public Act 26-15 and is presented in the checker as its own result for employment, not as a consequence of the 35,000 count. A small Connecticut employer under the CTDPA volume line can still carry the employment-track position for its hiring tools.
Keeping the tracks separate in the coverage file prevents the two classic errors: assuming a low consumer count answers the employment question, and assuming an employment-tool analysis answers the consumer profiling question. The employment track is covered in Connecticut AEDT Notices and the discrimination rule guide.
Enforcement context, as the checker states it
The checker data records the Act's enforcement frame: the Attorney General enforces the Act, penalties run up to the figure stated under the Connecticut Unfair Trade Practices Act for wilful violations, and there is no private right of action. This guide repeats the frame without extending it: the practical relevance for a covered controller is that the duties are public-enforcement duties, answered for with records — which returns the analysis to the standing theme: opt-outs logged with dates, answers filed, assessments dated, all in the one record.
Run your facts through the free checker selecting Connecticut and your decision type: its result states the duties for covered controllers in their operational form, and its notes state the threshold test alongside — the two halves of this guide in one screen.
- Count Connecticut consumers specifically — 35,000 or more a year, payment-only data excluded — and record the residency method used
- Classify your data inventory for the sensitive-data trigger independently of volume
- Answer the data-for-sale trigger from the business model, and file all three findings with measurements and dates
- If covered, stand up the live duties first: opt-out intake on the 45-day standard, outcome answers, assessments before heightened-risk profiling
- Keep the PA 26-15 employment track as a separate analysis — the consumer thresholds do not answer the hiring-tool question
Sources, as carried in the kit's own data: the duty summaries in app/rules.py and the checker data in app/checker_data.py, verified against primary or authoritative sources on October 28, 2026. Run the free duties checker for your jurisdiction, decision type, and the tool's role, and compare the kit's plans for the record, builder, and review queue. More from Ingenious AI is on the hub.
Related guides
- Connecticut Profiling Opt-Out Rights: What the CTDPA Gives Consumers and What Businesses Must Do
- Connecticut Automated Employment Decision Tool Notices: What Employers Must Send and When
- Connecticut's Discrimination Rule for Automated Employment Tools: No Defence, No Safe Harbour
- Colorado AI Act Automated Decision Notices: What to Send
See all ADMT guides for the full set.
Frequently asked questions
What are the CTDPA thresholds in the kit's data?
Processing the personal data of 35,000 or more Connecticut consumers a year (excluding payment-only data), processing sensitive data, or offering personal data for sale.
Do non-Connecticut businesses need to count?
Yes, if they process Connecticut consumers' data — the trigger counts Connecticut consumers specifically, so a business elsewhere with a Connecticut customer base can be in scope for that processing.
What duties switch on when a threshold is met?
The profiling set for covered decisions: the opt-out (since July 1, 2023; expanded July 1, 2026), outcome answers (question the result, reasoning, data review; housing adds correct-and-re-run), and a data-protection assessment before heightened-risk profiling.
Are the Connecticut employment-tool rules part of the thresholds analysis?
No. The discrimination no-defence rule and the AEDT notices arise under Public Act 26-15 as a separate track, presented separately in the checker.
Who enforces the CTDPA?
The Attorney General, per the kit's checker data; there is no private right of action.