You collect data from New Hampshire consumers. But when one of those people asks to know what you have on them, what happens?

This page covers one piece of the picture. For the full scope of the NHDPA — who must comply, the thresholds, the consumer rights and the penalties — start with our complete guide to the NHDPA and cookies.

That question leaves a lot of businesses without an answer. And the New Hampshire Data Privacy Act (NHDPA, RSA 507-H), in effect since January 1, 2025, does not accept silence as a response.

The law guarantees clear and concrete rights to state consumers. And for each of those rights, there is a corresponding obligation on your side. This article covers all of it: what a DSAR is, what rights the NHDPA guarantees, how to process each type of request, which deadlines to apply, and what happens when something goes wrong.

DSAR stands for Data Subject Access Request. In practice, it is any formal request made by a consumer to exercise the rights the law grants them over their own data.

This includes asking to see what you collected, correcting incorrect information, requesting deletion of their data, asking for a portable copy, refusing the use of their data for advertising purposes, or contesting a decision your business made about a previous request.

If you are already familiar with the GDPR, the DSAR framework will feel quite familiar. The NHDPA follows the same logic: the data subject needs a functional channel to exercise the rights the law guarantees.

The Privacy Portal is the digital interface that centralizes this process.

Under RSA 507-H:4, residents of New Hampshire have six main rights:

The consumer can request confirmation that the business processes their data and obtain a copy of the personal data the business holds about them, under RSA 507-H:4, I, a.

The copy must be in a readable format. If processing is carried out by electronic means, the format must also be portable.

The consumer can request correction of inaccurate personal data, taking into account the nature and purpose of the processing, under RSA 507-H:4, I, b.

This includes any outdated, incomplete, or incorrect data. The business cannot ignore this request by claiming the data is old or was already used for a specific purpose.

The consumer can request the deletion of personal data they provided or that was collected about them, under RSA 507-H:4, I, c.

There are exceptions. The business may refuse if processing is necessary to comply with a legal obligation, for defense in legal proceedings, or for purposes expressly protected by law. But the refusal must be justified.

The consumer can obtain a copy of their data in a portable and machine-readable format when processing is carried out by automated means, under RSA 507-H:4, I, d. This makes it easier to transfer the data to another service.

The consumer can refuse the processing of their data for three specific purposes (RSA 507-H:4, I, e):

Targeted advertising.

Sale of personal data to third parties.

Profiling with legal or similarly significant effects on the consumer.

The opt-out for targeted advertising and data sale must be accessible via a clear and conspicuous link on the site, as required by RSA 507-H:6, V, a, 1. The business cannot create obstacles to the consumer exercising this right.

If the business denies a request, the consumer has the right to appeal the decision, under RSA 507-H:4, II. The business must provide an appeals process that is convenient and comparable to the original submission mechanism.

The deadline to respond to appeals is 60 days, under RSA 507-H:4, II, b.

If the appeal is also denied, the business must inform the consumer how they can file a complaint with the New Hampshire Attorney General.

The NHDPA is clear on deadlines and there is little room for interpretation.

45 days from the receipt of an authenticated request to respond (RSA 507-H:4, III, a).

The deadline can be extended by another 45 days in cases of high volume or complexity, as long as the consumer is notified within the initial period with the reason for the extension (RSA 507-H:4, III, a).

60 days to respond to appeals (RSA 507-H:4, II, b).

These deadlines begin when the request is received and authenticated. If the business requests additional information to verify the identity of the requester, the deadline is paused until that verification is completed, provided the request for information is reasonable and proportionate.

For deadline purposes, receipt of the request occurs when the business has the information necessary to identify the consumer and process the request.

If the identity verification process is still pending, the deadline starts only after confirmation. This is why the verification process must be agile and proportionate to the type of data involved.

Under RSA 507-H:6, V, the controller must make available at least one secure and reliable mechanism for consumers to submit requests to exercise their rights.

This mechanism must meet two fundamental requirements:

It cannot require the consumer to create a new account to exercise the rights guaranteed by law (RSA 507-H:6, V, b).

It must include a clear and conspicuous link to a page where the consumer can specifically exercise the opt-out of targeted advertising and data sale (RSA 507-H:6, V, a, 1).

A well-structured Privacy Portal offers:

A request submission form with clear categories (access, correction, deletion, portability, opt-out).

A proportionate and non-discriminatory identity verification process.

Automatic receipt confirmation with a tracking reference number.

A log of each request and response for audit purposes.

An appeal channel for denied cases.

The cookie consent on the site and the Privacy Portal must be integrated so that consumer preferences are reflected in real time in the company's systems.

The business needs to verify that whoever is submitting the request is actually the data subject. But this process cannot be a barrier.

The NHDPA does not specify a single verification method, but the general standard is that verification must be proportionate to the sensitivity of the data involved and the risk of harm to the consumer.

In practice, this means:

For low-risk data: an email confirmation may be sufficient.

For sensitive data or high-risk harm scenarios: a second verification factor may be necessary.

What is never acceptable: requiring documents that go beyond what is reasonable to verify identity, such as physical ID documents for access to simple browsing data.

The business also cannot require the creation of a new account, the use of third-party platforms unrelated to the original service, or the provision of more personal data than necessary for identification.

Under RSA 507-H:4, III, c, request processing is free of charge once per year per consumer.

From the second request within the same 12-month period, the business may charge a reasonable fee or decline processing if the request is manifestly unfounded, excessive, or repetitive.

But the burden of proof is on the business. In other words, if you want to charge or refuse, you must be able to demonstrate that the request is in fact excessive. A subjective assessment is not enough.

Each type of request has a specific workflow. Here is how to process each one.

Receive the request and authenticate the data subject.

Locate all personal data the business holds about this consumer across its systems.

Prepare a copy in a readable format.

Include in the response: categories of data, purposes of processing, third parties with whom the data was shared, and retention period.

Send the response within the 45-day deadline.

An up-to-date data mapping exercise is what makes this process viable. Without a clear inventory of where data lives, the search becomes manual and error-prone.

Receive and authenticate.

Identify which data is inaccurate and where it is stored.

Correct the data in primary systems and, where applicable, notify third parties that received the data so they can also make the correction on their side.

Confirm to the data subject that the correction was made.

Receive and authenticate.

Check whether a legal exception exists that allows retaining the data (legal obligation, judicial defense, purpose protected by law).

If no exception exists: delete the data from all systems where it is stored, including backups where technically feasible.

Notify third parties that received the data to also delete it where applicable.

Confirm to the data subject with details of what was deleted and, if anything was retained, the legal justification.

Receive and authenticate.

Generate a file with the data subject's data in a portable, machine-readable format (such as JSON or CSV).

Deliver it to the data subject securely within the deadline.

This is the most urgent of all. When the consumer exercises the opt-out of targeted advertising, data sale, or profiling with significant effects, the systems must be updated immediately.

And there is a specific deadline for this: under RSA 507-H:6, I, f, after consent is revoked, the business has a maximum of 15 days to cease processing.

This means that CRM systems, email marketing platforms, advertising pixels, and analytics tools must be configured to accept and process this command within 15 days. It is not optional.

A consent management platform integrated with the company's systems automates a large part of this workflow.

The business may deny a request when:

It cannot verify the identity of the data subject.

The request is manifestly unfounded or excessive.

Processing is necessary for a legal or contractual reason that prevails over the right to deletion.

In all cases, the denial must be communicated to the data subject within the 45-day deadline. The communication must:

State the reason for the denial clearly.

Explain how the data subject can appeal the decision.

Indicate the available appeal process.

The appeal process must be accessible and practical. The business has 60 days to respond to the appeal (RSA 507-H:4, II, b). If the appeal is also denied, the data subject must be informed that they can file a complaint with the Attorney General.

The NHDPA expressly prohibits businesses from discriminating against consumers who exercise the rights guaranteed by law (RSA 507-H:6, II).

This means the business cannot:

Deny products or services to a consumer who exercised the opt-out.

Charge different prices because a right was exercised.

Offer lower quality service as retaliation for a request.

There is a specific exception: loyalty programs or benefits that offer value in exchange for the use of data are permitted, as long as the benefits are reasonably related to the value the data represents to the business.

RSA 507-H:6, I, g brings an additional protection that directly impacts the Privacy Portal: when the business has actual knowledge that a consumer is between 13 and 15 years old, it cannot process that person's data for targeted advertising or sell it without explicit consent.

If your portal receives requests from users in this age range, the process must have a differentiated flow to ensure that this consent exists or does not exist, as the case may be.

Every processed request must be documented. This includes:

Date and time of receipt.

Type of request.

Identity verification process performed.

Action taken.

Date and form of response to the data subject.

In case of denial: recorded justification.

In case of appeal: the full appeal history and decision.

This documentation is what protects the business in the event of an Attorney General investigation. Without records, there is no way to prove that the process was completed within the required deadlines.

A Records of Processing Activities (ROPA) document that is kept up to date is the central element of this audit trail.

In 2025, before initiating a lawsuit, the Attorney General was required to notify the business and give 60 days to correct any violation (RSA 507-H:11, II). From 2026 onward, this cure period became discretionary (RSA 507-H:11, III).

This directly impacts the Privacy Portal: a business without a structured process to handle DSARs may face direct enforcement action, with no guaranteed time to correct.

Violations are treated under RSA 358-A:2 (Consumer Protection Act), with reference penalties of up to US$ 10,000 per violation.

AdOpt logs every consent and revocation interaction with a timestamp and unique identifier. When the consumer revokes consent through the Privacy Portal, the system automatically updates cookie and tracker triggers within the 15-day deadline required by the NHDPA.

AdOpt's auditable log serves as evidence that the process was completed as required by law. And when legislation changes, the platform updates automatically.

Over 60,000 websites already run with AdOpt.

Privacy is not a banner. It is a position.

Want to build a Privacy Portal for your site that complies with the NHDPA? Talk to our team.

Request submission channel without requiring creation of a new account (RSA 507-H:6, V, b).

Coverage of all 6 rights guaranteed by the NHDPA: access, correction, deletion, portability, opt-out, and appeal.

Conspicuous opt-out link for targeted advertising and data sale (RSA 507-H:6, V, a, 1).

45-day response deadline, with the option to extend by another 45 days with notification (RSA 507-H:4, III, a).

60-day deadline to respond to appeals (RSA 507-H:4, II, b).

Proportionate and non-discriminatory identity verification process.

Free response once per year per consumer (RSA 507-H:4, III, c).

Cessation of processing within 15 days after consent revocation (RSA 507-H:6, I, f).

Documented record of each request, action taken, and response sent.

Accessible appeals process with information on how to file a complaint with the Attorney General in case of a second denial.

Non-discrimination protection for consumers exercising their rights (RSA 507-H:6, II).

Differentiated treatment for consumers aged 13 to 15 (RSA 507-H:6, I, g).

Notification to third parties where applicable for deletion or correction of shared data.

Other US states with similar laws, such as the Texas TDPSA and the Tennessee TIPA, follow similar structures with variations in deadlines and application criteria.

1. Does the NHDPA require a dedicated Privacy Portal?
Not by name. RSA 507-H:6, V requires the controller to make available at least one secure and reliable mechanism for submitting requests. A dedicated Privacy Portal is the most organized way to meet this requirement, but a well-structured contact form or an active, monitored email address can also fulfill the obligation, as long as all legal criteria are met.

2. What is the deadline to process a targeted advertising opt-out?
There are two separate deadlines that must be observed. The general response deadline is 45 days from authenticated receipt, under RSA 507-H:4, III, a. But the deadline for actual cessation of processing after consent revocation is 15 days, under RSA 507-H:6, I, f. Both deadlines run simultaneously and must be met independently.

3. Can the business charge a fee for processing a DSAR?
Processing is free once per year per consumer, under RSA 507-H:4, III, c. From the second request within the same 12-month period, the business may charge a reasonable fee or decline if the request is manifestly unfounded, excessive, or repetitive. The burden of proving the excessive nature lies with the business.

4. What happens if the business denies a request without adequate justification?
The consumer can appeal the decision within 60 days, under RSA 507-H:4, II. If the appeal is denied, they can file a complaint with the New Hampshire Attorney General. From 2026 onward, the Attorney General can initiate direct action without guaranteeing a cure period for the business (RSA 507-H:11, III), with reference penalties of up to US$ 10,000 per violation under RSA 358-A:2.

5. How should requests from teenagers aged 13 to 15 be handled?
RSA 507-H:6, I, g requires special treatment for consumers in this age range. When the business has actual knowledge that the requester is between 13 and 15 years old, processing their data for targeted advertising and selling it without explicit consent are prohibited. The Privacy Portal must have a specific workflow to identify and handle these requests differently, ensuring that the additional restrictions are automatically applied.

With AdOpt, you're covered.

Ready to build a Privacy Portal for your site that complies with the NHDPA? Talk to our team.

New Hampshire NHDPA compliance rests on documents that need 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.