One more US state has entered the data privacy map.
The New Hampshire Data Privacy Act (NHDPA), codified under RSA 507-H, came into effect on January 1, 2025. It guarantees rights for consumers in the state and creates clear obligations for businesses that process the personal data of those individuals.
If your website serves users from New Hampshire, this guide is for you.
The New Hampshire Data Privacy Act (RSA 507-H) is New Hampshire's state-level personal data protection law. It follows the same logic as the major modern privacy regulations: giving people back control over the data companies collect about them.
If you are already familiar with the LGPD, the GDPR, or the CCPA, the NHDPA framework will feel familiar. The differences are in the details, and some of those details matter quite a bit.
Enforcement falls under the Data Privacy Unit within the Consumer Protection and Antitrust Bureau of the New Hampshire Department of Justice. The state's Attorney General holds exclusive authority to enforce the law.
On January 1, 2025.
There is no grace period. There are no friendly warnings from regulators. Any business that meets the criteria should already be in compliance.
Under RSA 507-H:2, the law applies to persons that conduct business in New Hampshire or produce products or services targeted to state residents and that, during a calendar year:
Control or process personal data of at least 35,000 unique consumers, excluding data processed solely to complete a payment transaction, or
Control or process personal data of at least 10,000 unique consumers and derive more than 25% of gross revenue from the sale of personal data.
The law does not focus on where the business is headquartered. It focuses on who the users are. If you have traffic from New Hampshire and process data from those people at scale, the law may reach you.
Understanding the difference between controller and processor is the first step in defining which role your business plays and what your responsibilities are.
Under RSA 507-H:3, the following are exempt:
State and local government bodies and their subdivisions.
Nonprofit organizations.
Higher education institutions.
Financial institutions regulated by the Gramm-Leach-Bliley Act.
Entities regulated by HIPAA.
National securities associations registered with the SEC.
Under RSA 507-H:1, XIX, personal data is any information linked or reasonably linkable to an identified or identifiable individual. This includes name, email, IP address, browsing history, location data, device identifiers, and any information that allows a person to be tracked.
De-identified data and publicly available information are excluded.
A well-executed data mapping exercise reveals where this data is being generated and processed in your digital environment.
Under RSA 507-H:1, XXVIII, sensitive data includes:
Data revealing racial or ethnic origin, religious beliefs, mental or physical health condition or diagnosis, sex life, sexual orientation, citizenship or immigration status.
Genetic or biometric data processed to identify an individual.
Personal data collected from known children (under 13 as defined by COPPA).
Precise geolocation data (within a radius of 1,750 feet).
Sensitive data cannot be processed without the consumer's explicit prior consent, as required by RSA 507-H:6, I, d.
The NHDPA goes beyond protections for children under 13. RSA 507-H:6, I, g expressly prohibits controllers from processing data of consumers for targeted advertising or data sale purposes without consent when the controller has actual knowledge and deliberately ignores that the consumer is between 13 and 15 years old.
This additional protection for teenagers is a distinguishing feature of the NHDPA compared to other US state laws.
Under RSA 507-H:4, the law guarantees residents of New Hampshire the following rights:
Right to access and confirmation: knowing whether the business processes their data and obtaining a readable copy.
Right to correction: correcting inaccuracies in personal data.
Right to deletion: requesting the deletion of data they provided or that was collected about them.
Right to portability: obtaining data in a portable, usable format, when processing is carried out by automated means.
Right to opt-out: refusing processing for targeted advertising, personal data sale, and profiling with legal or similarly significant effects.
Right to appeal: challenging any request denied by the controller.
The controller has 45 days to respond. The deadline can be extended by another 45 days in complex cases, as long as the consumer is notified within the initial timeframe (RSA 507-H:4, III, a).
Service is free once per year per consumer. For requests that are manifestly unfounded, excessive, or repetitive, the business may charge a reasonable fee or refuse, but the burden of proving the excessive nature of the request lies with the business (RSA 507-H:4, III, c).
Under RSA 507-H:1, VII, consent is a clear affirmative act signifying a consumer's freely given, specific, informed, and unambiguous agreement.
What is not valid consent: accepting general terms of use that contain data processing descriptions alongside unrelated information, hovering over or closing a piece of content, and any agreement obtained through dark patterns.
Dark patterns, defined in RSA 507-H:1, XII, are interfaces designed with the substantial effect of subverting or impairing the autonomy, decision-making, or choice of the user.
A specific and important point of the NHDPA is in RSA 507-H:6, I, f: after a consumer revokes consent, the business must cease processing the data as soon as practicable, but no later than 15 days after receiving the request.
This is a shorter deadline than the DSAR response period and directly impacts how marketing and tracking systems are configured.
Under RSA 507-H:6, the controller must:
Limit data collection to what is adequate, relevant, and reasonably necessary for the stated purposes.
Not process data for purposes incompatible with those disclosed, except with consent.
Implement reasonable technical, administrative, and physical security practices proportionate to the volume and nature of the data.
Not process sensitive data without prior consent.
Not discriminate against consumers who exercise their rights.
Offer a consent revocation mechanism that is as easy to use as the consent mechanism itself.
Provide a clear and meaningful privacy notice covering all elements required by law.
Conduct Data Protection Assessments for high-risk activities.
A Records of Processing Activities (ROPA) document that is kept up to date records all of these activities and serves as evidence of compliance in the event of an investigation.
Cookies that collect personal data or allow user identification fall directly within the scope of the NHDPA.
Before firing any non-essential cookie, the website must display a clear cookie notice, obtain affirmative consent, block trackers until acceptance, and offer real opt-out options without dark patterns.
Correct tag categorization is what makes it possible to identify which cookies are necessary and which require consent.
The law also requires respect for the opt-out preference signal, such as the Global Privacy Control (GPC), under RSA 507-H:6, V, a, 1, B. But with an important nuance: the signal is only valid when the consumer configured it in an affirmative and voluntary manner, not as an automatic device default.
Under RSA 507-H:11, the Attorney General holds exclusive authority to enforce the NHDPA. There is no private right of action.
In 2025 (RSA 507-H:11, II): the Attorney General was required to issue a notice of violation and give the controller 60 days to cure before filing a lawsuit.
From 2026 onward (RSA 507-H:11, III): the cure period became discretionary. The Attorney General may or may not grant the cure period, considering factors such as the number of violations, the size and complexity of the business, the nature of the processing, the risk to the population, and whether the violation was caused by human or technical error. There is no longer an automatic right to an opportunity to correct.
Violations are treated as unfair trade practices under RSA 358-A:2 (New Hampshire Consumer Protection Act), which provides for significant civil penalties. The market reference value is up to US$ 10,000 per violation.
Understand what you collect, where it lives, how it is used, and with whom it is shared. Data mapping is the foundation of everything.
The document must cover all requirements of RSA 507-H:6, III, with the date of the last update clearly visible.
A cookie banner that blocks, records, respects the GPC as an affirmative choice, and offers real control options.
At least one secure and reliable mechanism to receive requests. No requirement for the consumer to create a new account.
Ensure your systems can cease processing within 15 days of a consent revocation.
ROPA, data protection assessments, processor agreements. This documentation is your defense.
Applying privacy by design from the conception of products is what makes compliance sustainable.
AdOpt records every consent interaction, blocks trackers before acceptance, automatically respects the GPC when configured by the user, and generates the auditable log you would need to present in an investigation.
The automatic scan identifies all active trackers on the site, feeding the data inventory. And when the law changes, the platform updates automatically.
Over 60,000 websites already run with AdOpt.
Privacy is not a banner. It is a position.
Ready to bring your website into compliance with the NHDPA? Talk to our team.
| Law | State | Consumer Volume | Penalty | Effective Date |
|---|---|---|---|---|
| NHDPA | New Hampshire | 35K or 10K + 25% revenue | Up to US$ 10K/violation | Jan 2025 |
| TIPA | Tennessee | 175K or 25K + 50% revenue | US$ 7,500/violation | Jul 2025 |
| TDPSA | Texas | 25K residents | US$ 7,500/violation | Jul 2024 |
| MTCDPA | Montana | 25K residents | US$ 7,500/violation | Oct 2025 |
| CPA | Colorado | 100K residents | US$ 20,000/violation | Jul 2023 |
To understand how these privacy laws compare in terms of structure, our comparative guide goes deeper on the subject.
Compliance with the NHDPA rests on three documents that have to agree with each other: the cookies policy, which declares every tracker and its purpose; the privacy policy, which explains what you do with the data; and the privacy portal, where the consumer exercises their rights and you keep the record of it.
1. What is the NHDPA and when did it come into effect?
The New Hampshire Data Privacy Act (RSA 507-H) is New Hampshire's state-level data protection law. It came into effect on January 1, 2025. It guarantees rights to consumers in the state and imposes compliance obligations on businesses that process the personal data of those individuals.
2. Who needs to comply with the NHDPA?
Businesses that conduct operations in New Hampshire or target products and services to its residents, and that process data from at least 35,000 unique consumers per year, or from at least 10,000 consumers while deriving more than 25% of revenue from the sale of personal data (RSA 507-H:2).
3. What is the penalty for non-compliance?
Violations are treated as unfair trade practices under RSA 358-A:2. The reference value is up to US$ 10,000 per violation. In 2025, there was a guaranteed 60-day cure period. From 2026 onward, the cure period is discretionary and may not be granted (RSA 507-H:11).
4. How long does a business have to respond to a consumer request?
45 days from the receipt of an authenticated request. The deadline can be extended by another 45 days in complex cases, with notification within the initial period. For appeals, 60 days. Free once per year per consumer (RSA 507-H:4, III).
5. What is the deadline to cease processing after consent is revoked?
15 days from the receipt of the revocation request, under RSA 507-H:6, I, f. This deadline is separate from the DSAR response period and must be factored into the configuration of marketing and tracking systems.
Want to bring your website into compliance with the NHDPA? Talk to our team.
Discover the 5 common **cookie consent mistakes** that risk your **compliance** and learn how to avoid heavy **fines**. Simplify your **data privacy** strategy using a reliable **[Cookie notice/banner](https://goadopt.io/en/blog/why-the-cookie-banner/)**.
What the Connecticut CTDPA requires from your Cookies Policy: opt-out link, opt-out preference signal from January 2025, 15-day consent revocation, teen protections, and targeted advertising definition.
Learn the essential steps for creating GDPR-compliant cookie banners in 2025, ensuring user consent and privacy protection.
How does your website handle LGPD? What strategies does it use to comply with the General Data Protection Law? Have you thought about using a cookie notice but don't know if your site has cookies or if it's enough? If you can't answer these questions, be cautious! Your page may be exposed to fines and other sanctions.
How to handle DSARs under the California CCPA/CPRA: 7 consumer rights, 45-day deadline, toll-free number required, 12-month lookback, private right of action for breaches, and CPPA enforcement.
Have you ever thought that your marketing agency could find a great business opportunity in LGPD? Well, unlike what many think, it brings changes that can accelerate the demand for the services of these companies.
Learn what your Privacy Policy must contain under the NHDPA. We break down the 8 mandatory elements and how to comply with New Hampshire's data privacy law.
Having a cookie banner on your brand's website has become indispensable for many. However, for e-commerce websites, it has practically become an obligation to have one. This is because this type of website has a technological composition in which cookies are a structural part. Login flow, items in the shopping cart, recommendation showcases, remarketing... Most of them rely on cookies.
California CPRA explained: CCPA vs CPRA timeline and key differences, sensitive personal information, sharing of data, CPPA enforcement, GPC requirement, and tripled penalties for minors.
Find out if the MTCDPA applies to your site, key compliance deadlines, and new rules for cookies and consent in Montana
Iowa ICDPA DSAR guide: 90-day response deadline, 45-day extension, 60-day appeal process, limited deletion scope, opt-out from data sales, targeted advertising disclosure requirement, and 90-day cure period.
Utah UCPA DSAR guide: four consumer rights, limited deletion scope, no right to correct, no formal appeal process, no opt-out of profiling, 45-day deadline, and the guaranteed 30-day cure period.
Learn what your MTCDPA Privacy Policy must include after Montana's SB 297 amendments from the conspicuous "privacy" hyperlink and last-updated date requirements to sale disclosures, minor protections, and how to keep your notice operationally aligned with your stack.
A privacy policy is a document that outlines how an organization collects, uses, discloses, and manages a customer's data. It's essential for building trust with users and complying with legal requirements. However, if you're not familiar with it, don't worry as we're here to help you.
The Texas Data Privacy and Security Act (TDPSA) introduces sweeping changes to how businesses collect, use, and disclose personal data—and your privacy policy is now a frontline compliance tool. This article is a comprehensive guide for any company serving Texas residents, explaining how to align your privacy practices with the new legal standards.
What is a DSAR under NHDPA? Complete guide to consumer rights, response deadlines, and building a compliant Privacy Portal for your site.
Learn how to build a defensible TIPA Cookies Policy for Tennessee compliance covering consent architecture, opt-out requirements, the NIST affirmative defense, and how your cookie banner, privacy notice, and vendor management must work together under the Tennessee Information Protection Act.
The Connecticut Data Privacy Act (CTDPA) is a state regulation designed to protect the privacy of Connecticut residents. It also regards cookies, so in this article we will help you understand all about this new privacy regulation.
Everything you need to know about the Florida Digital Bill of Rights (FDBR): who must comply, the $1 billion threshold, 7 consumer rights, FIPA vs FDBR explained, penalties, and cookies.
What the Colorado CPA requires from your Cookies Policy: mandatory Universal Opt-Out Mechanism from July 2024, targeted advertising definition, dark pattern rules, and the 24-month consent refresh.
Everything about the Oregon OCPA: who must comply, the payment transaction exclusion, 25% revenue threshold, derived data in scope, GPC requirement from January 2026, and elimination of the cure period.
In this article, you will have a great introduction to the topic, as well as various other variations that revolve around the subject: Cookies and LGPD.
What the California CPRA requires from your Privacy Policy: SPI category, two mandatory links, data retention periods, sharing disclosure, right to correct, GPC, and minor protections.
What the Florida FDBR requires from your Cookies Policy: targeted advertising across affiliated sites, opt-out for sensitive data and voice recognition, dark patterns, and tripled penalties.
Google Consent Mode (GCM) is nothing more than a way for you to integrate the consent you collect from your visitors into Google technologies. In this way, upon receiving this consent information, collection can only occur with authorization, thus complying with the legislation and having direct evidence of compliance as defense for both you and Google.
Learn how to build a TIPA-compliant Privacy Portal for Tennessee. Understand DSAR deadlines, consumer rights, opt-out mechanisms, and the affirmative defense that sets TIPA apart from every other US state privacy law.
The Colorado Consumer Privacy Act went into effect July 1, 2023 (CPA). CPA is a vital piece of legislation designed to protect the privacy of residents in Colorado. Understanding its requirements is essential for any business operating in the state. This act is all about giving control back to the consumers regarding their personal data. But what does this mean for you and your business, especially when it comes to managing cookies on your website?
What the Florida FDBR requires from your Privacy Policy: annual updates, 6 mandatory content categories, specific notices for sensitive and biometric data sales, and the 7 consumer rights.
What the California CCPA/CPRA requires from your Privacy Policy: 12-month lookback, annual updates, Do Not Sell link, sensitive PI disclosures, toll-free number, and the 7 consumer rights.
What the Connecticut CTDPA requires from your Privacy Policy: active email contact, opt-out link, 15-day consent revocation, opt-out preference signal from January 2025, and teen protections.
What the Colorado CPA requires from your Privacy Policy: 5 mandatory elements, purpose specification duty, secondary use prohibition, 24-month consent refresh, and Universal Opt-Out Mechanism disclosure.
Utah UCPA explained: the most business-friendly US state privacy law, dual threshold requirement, opt-out for sensitive data, no right to correct, guaranteed 30-day cure period, and key differences from other state laws.
What the Oregon OCPA requires from your Cookies Policy: opt-out link, GPC from January 2026, opt-out without authentication, derived data in scope, teen protections, and the elimination of the cure period.
California CPRA DSAR guide: new rights to correct and limit SPI, opt-out without multiple steps, GPC as valid opt-out, 12-month minor rule, private right of action, and CPPA enforcement.
Your website have users accessing from Texas? So be ready… the Texas Data Privacy and Security Act is here to shake things up. Don't worry; we've got your back. This guide will walk you through everything you need to know to ensure your website complies with the new regulations.
How to handle DSARs under the Virginia VCDPA: consumer rights, 45-day response deadlines, the appeal process, free requests twice per year, and how to build a compliant Privacy Portal.
In this article, we'll explore the GDPR foundations and provide practical insights from the basics to more advanced concepts of its legal basis.
How to handle DSARs under the Florida FDBR: 7 consumer rights, two required submission channels, 45-day deadline with only 15-day extension, tripled penalties for children, and compliance guide.
What the Iowa ICDPA requires from your Cookies Policy: opt-out for data sales and targeted advertising, opt-out model for sensitive data, no GPC requirement, no specific link text required, and the 90-day cure period.
Rights, Policy and how to understand about the DSAR Montana MTCDPA
Despite cookies being more well-known, what is the main difference between cookies and session storage and local storage? Why choose one over the other? This article will help you with these doubts!
What the California CPRA requires from your Cookies Policy: the sharing concept, GPC as valid opt-out, Do Not Sell or Share link, SPI geolocation, minor protections, and retention periods.
What are the criteria for this choice, and what are the strengths and weaknesses of each option? Well, we're here to help you because this decision needs to be well thought out!
Cookies Policy under NHDPA explained. Discover what's mandatory, dark patterns to avoid, and how to implement legal cookie consent.
Everything you need to know about the Virginia Consumer Data Protection Act (VCDPA): who must comply, consumer rights, cookie requirements, penalties, and how to get your site in compliance.
24 Jul 2025
Address: 7345 W Sand Lake Road, Ste 210 Office 5898 Orlando, FL 32819
15 Rue du Général Campredon, 34000 Montpellier, France
207 Rue de Bercy, 75012 Paris, France
EIN: 86-3965064
Phone: +1 (407) 768-3792
AdOpt
Resources
Product
Certifications