Connecticut AI Law: What Starts Oct 1 for Small Business

Connecticut's AI law starts October 1, and the headlines say it regulates AI chatbots. On that date, it doesn't. The chatbot rules in Public Act 26-15 start January 1, 2027, and they exclude the customer service bot on your website. What st

Connecticut's AI law starts October 1, and the headlines say it regulates AI chatbots. On that date, it doesn't.

The chatbot rules in Public Act 26-15 start January 1, 2027, and they exclude the customer service bot on your website. What starts October 1 is smaller and stranger: a subscription notice, a line about hiring tools, and a layoff disclosure.

Here's the sorted version for a Connecticut small business.

The Chatbot Rules Start January 1, Not October 1

A Connecticut outlet ran the headline "New Laws Go Into Effect Oct. 1 Regulating AI Chatbots, Protecting Whistleblowers" on September 17. The whistleblower half is right. The chatbot half needs a footnote.

The enrolled text of Public Act 26-15 gives every section its own effective date. Sections 4 to 6, the "artificial intelligence companion" rules, say January 1, 2027. The Future of Privacy Forum's explainer reads it the same way.

The act does have real October 1 provisions. They just aren't the chatbot ones.

October 1, 2026: the AI subscription notice (Section 1), the "AI is no defense" language in Connecticut's employment discrimination statutes (Sections 13 and 14), the layoff disclosure for employers that file federal WARN notices (Section 26), the provenance rule for very large image and video generators (Section 15), and whistleblower protection at frontier AI developers (Section 2).

January 1, 2027: the AI companion rules (Sections 4 to 6).

October 1, 2027: the hiring-tool duties in Sections 8 to 10. Sections 7 to 12 are technically effective October 1, 2026, but their duties attach to tools deployed on or after October 1, 2027.

Your AI Receptionist Sits Outside the Companion Rules

Start with the part most owners worry about.

The act defines an AI companion as AI with a natural-language interface that gives adaptive, human-like responses, including through anthropomorphic features, and can sustain a relationship across multiple interactions. That's a friendship app.

Then the definition lists what it excludes. A chatbot used only for a business's operational purposes, technical assistance, customer service or support is out, provided it isn't marketed to consumers as a companion. So are narrow task-specific tools. So is a company that supplies a model to others without solely deciding the use case, interface, or deployment.

That covers your website chat widget. It covers the AI phone receptionist that books a Tuesday slot. Colorado drew the same line in its own bill, which we walked through in our Colorado chatbot law breakdown.

If a bot did land inside the definition, the disclosure rule would apply whenever a reasonable person might think they were talking to a human. The notice is either a static one visible throughout, or a spoken or written one at the start of the first interaction in any 24 hours, then once every three hours for adults and hourly for minors.

The exclusion turns on the words "not marketed to consumers as a companion." So don't pitch your receptionist as a friend. Give it a job and a name that fits the job.

Our own receptionists open every call by saying they're an AI. That's a state-independent habit, and we explain why in our state-by-state disclosure guide. It costs one sentence.

The Subscription Rule Catches Small Software Sellers on October 1

This is the provision most likely to surprise a small software seller.

Section 1 applies to a "subscription-based provider": a person doing business in Connecticut who offers AI technology to a consumer for a fee. "Consumer" means an individual who lives in Connecticut. So it's a business-to-consumer rule. Sell only to other businesses and it doesn't reach you.

If you do sell an AI-powered product to Connecticut residents, from October 1 you can't start a subscription, renew one, or collect a fee unless two things happened first. You gave the customer written notice of the key terms, and the customer gave you written notice that they accept.

The notice has to include any limits you may impose, quantitative or qualitative, including limits you impose in response to the customer's own behavior. It also has to say whether you have discretion to cut their access or reduce the quantity or quality of any functionality. On renewal, you disclose what's new or changed.

Read that as a description of fair-use caps, throttling, and quiet model downgrades. If the discretion clause currently lives in paragraph fourteen of your terms page, Section 1 wants it in front of the buyer before the charge.

Whether a checkout checkbox plus a confirmation email counts as written notice and written acceptance is not answered in the text. That one is a question for your lawyer, and it's worth asking before October 1.

The Attorney General enforces it alone, as an unfair trade practice. The section says it creates no private right of action.

AI Is No Defense in a Hiring Complaint, Starting October 1

This is the provision that applies to every Connecticut employer using AI to hire or fire, whatever the tool costs.

Sections 13 and 14 amend the state's discrimination statutes. Using an automated employment-related decision technology is not a defense to a discrimination complaint. The commission or a court may also consider evidence of anti-bias testing: its quality, efficacy, recency, and scope, the results, and what you did in response.

Connecticut didn't ban AI hiring tools. It made you explain them, in writing, before the decision lands, and it made "the software did it" worthless.

— Arthur, Bunny Honey Club

The testing sentence tells you what to keep. A dated test, a clear scope, the results, and a record of the fix. The statute lists recency as a factor, so a bias check you ran once and filed is worth less than one you run on a schedule.

What counts as the technology? Any tool that processes personal data and produces a score, ranking, recommendation, or classification that is a "substantial factor" in a decision to hire, promote, discipline, discharge, or renew someone. The same definition covers selection for training and decisions about tenure or terms.

It excludes word processors, spreadsheets, and similar software that doesn't materially influence the decision. It excludes tools used only incidentally. It also excludes decisions about workplace health and safety, scheduling and planning, and productivity monitoring.

A résumé-ranking feature inside your applicant tracking system is in. The calendar tool that books interviews is out. If you want the neighboring rules, we covered California's AI-at-work law and the EU's high-risk treatment of AI candidate screening.

The Hiring Notice Rules Arrive a Year Later

Sections 8 to 12 are enrolled with an October 1, 2026 date, but the deployer duties attach to tools deployed on or after October 1, 2027. A "deployer" is any person doing business in Connecticut who puts such a tool into use. These sections set no headcount or revenue floor.

There are two duties. Under Section 9, if the tool is meant to interact with applicants or employees, you tell them in plain language that they're interacting with it. No disclosure is needed when a reasonable person would find it obvious.

Under Section 10, before the decision is made, you send a written notice. It lists six things:

1. That you've deployed an automated employment-related decision tool.
2. The tool's purpose and the nature of the decision.
3. The tool's trade name.
4. The categories of personal data it analyzes and how they'll be assessed.
5. The sources of that data.
6. Your contact information.

Item four is where small teams get stuck. If your vendor can't tell you what data the tool actually looks at, you can't write that line.

Two more details matter if you're buying software. Under Section 8, developers must hand deployers the information they need, and a developer may contract to take over the deployer's notice duties, provided the contract says clearly which duties it assumed. Check your vendor agreement for that clause. And under Section 11, you may withhold trade secrets, but you have to say you're withholding and why.

Enforcement sits with the Attorney General alone. For violations on or before December 31, 2027, the AG can send a notice of violation first and give you 60 days to cure it if a cure is possible. The act creates no private right of action.

Provenance and Layoff Rules Mostly Skip You

Section 15 is a provenance rule. It covers a provider whose generative AI system has more than one million monthly users and is publicly available to consumers for personal use, and it excludes business-to-business use. That describes the big image, audio, and video generators. Nothing in the section tells a business how to handle the images it generates.

Section 26 requires an employer that files a federal WARN layoff notice to tell the Labor Department whether the layoffs relate to its use of AI or another technological change. If you're too small to file WARN notices, ignore it.

Section 2 covers whistleblower protection and safety reporting at frontier model developers. Also not you.

What We Build for the October 2027 Notice

We build automations and AI receptionists, so weigh this as vendor talk.

When a client with real hiring volume asks for AI to screen applicants, our default is boring on purpose. The AI drafts and sorts. A named human decides. A log records both.

The Section 10 notice becomes an automated step. It fires the moment an application arrives, before any scoring step runs. The six items load from a config record kept per tool, so a vendor change updates the notice instead of leaving a stale PDF. A timestamp records when it went out. The decision record captures who decided and what the tool saw.

This is workflow automation of the dullest kind, and we build it in n8n. The automations we build are exactly this: the tedious, documented plumbing nobody wants to hand-maintain.

Why do it now instead of in 2027? Because the October 1, 2026 anti-bias-testing clause already rewards dated records. And retrofitting a notice into a live hiring funnel is far more annoying than starting with one.

Your homework before October 1 is short:

1. List every tool that touches a hiring, promotion, or discipline decision.
2. Ask each vendor what data the tool analyzes and who carries the notice duty under your contract.
3. Run a bias check, date it, and keep the results and the fix.
4. If you sell AI subscriptions to Connecticut consumers, fix the checkout notice.
5. Keep your receptionist in its customer service lane.