By adding a host of new protections for health data, Connecticut has continued to play an outsized role in privacy regulation. Learn more at TrueVault.
The momentum of states passing their own privacy laws is showing no signs of slowing down. The Connecticut legislature recently passed the Connecticut Data Privacy Act (CTDPA), which was then signed into law by Governor Ned Lamont. A trend that began with Europe’s Virginia’s Consumer Data Protection Act (CDPA), offering a similar set of rights to consumers and applying to businesses in much the same manner. With an effective data of July 1, 2023, it's a good idea to start getting familiar with its requirements. Here’s a quick rundown on the new law.
Borrowing terminology from the GDPR, most of the CDPA’s rules apply to “controllers.” A controller is a person or legal entity that determines the purpose and means of processing consumers’ personal data. Contrast this with a “processor,” which is an entity that processes personal data on a controller’s behalf. For example, consider an online retail business that uses a marketing email vendor to send promotions to its customers. The retail business is a controller because it collects consumers’ email addresses and determines when and how to send emails to them; the email vendor is a processor because it is only using those email addresses on the retailer’s orders.
However, not all controllers are required to comply with the CDPA. First they must meet these minimum criteria:
The first requirement applies pretty widely. Having a physical location in Connecticut clearly meets this condition, but so does merely selling goods online to people in Connecticut. For most businesses it is the second requirement, specifically the 100,000-consumer threshold, that is the critical test.
Many businesses assume the 100,000-consumer threshold doesn’t apply to them, but don’t be so quick to dismiss it. If your business has a website, it almost certainly processes personal data (e.g., IP addresses, cookies, etc.) from each one of its visitors. If you are getting just 8,400 unique visitors from Connecticut per month, that puts you over the 100,000 mark.
The CTDPA also contains a number of entity-level and data-level exemptions. For example, governmental agencies, nonprofit organizations, financial institutions, and institutions of higher education are completely exempted from having to comply. Similarly, data that is already regulated by the Health Insurance Portability and Accountability Act (HIPAA) and the Fair Credit Reporting Act (FCRA) is also exempted.
The CTDPA is designed to protect “consumers,” which means individuals who are Connecticut residents. The statute specifically states that “consumer” does not include an individual acting in a commercial or employment context, so employees and B2B contacts are permanently exempted from the CTDPA. For consumers acting in their personal capacity, the CTDPA grants them a series of data privacy rights. These rights are:
As with other state privacy laws, a major part of complying with the CTDPA involves posting privacy disclosures on a business’s website (and anywhere else it collects personal data). These disclosures must include the following information:
Disclaimer: This content is provided for general informational purposes only and does not constitute legal or other professional advice. Without limiting the foregoing, the content may not reflect recent developments in the law, may not be complete, and may not be accurate or relevant in an applicable jurisdiction. This content is not a substitute for obtaining legal advice from a qualified licensed attorney in the applicable jurisdiction. The content is general in nature and may not pertain to specific circumstances, so it should not be used to act or refrain from acting based on it without first obtaining advice from professional counsel qualified in the applicable subject matter and jurisdictions.
Get monthly updates on the latest updates on policy & the shifting privacy landscape.
Dive into a world of knowledge, trends, and industry updates on the TrueVault blog.