Back to the hub

What is the appeal process under the Texas Data Privacy and Security Act?

Section 541.053 of the Texas Data Privacy and Security Act requires a controller that refuses a consumer request to offer a conspicuous appeal process, similar to the original request route. The controller must answer in writing within 60 days of receiving the appeal, and any denial must carry a link to the attorney general.

Applies to: Controllers subject to the Texas Data Privacy and Security Act that decline, in whole or in part, to act on a consumer rights request. The appeal duty is triggered by the refusal itself, not by the type of right the consumer exercised.

Find out what applies to you

Run the free 2-minute Obligation Scan and get a plain-language list of what your business has to do, and by when.

Run the free 2-minute Obligation Scan

Most Texas Data Privacy and Security Act compliance work stops at the 45-day response clock. That is the visible deadline, and it is the one that gets diaried. The appeal obligation behind it is the one that tends to go unbuilt, because it only comes into play when a controller says no, and a company that has never refused a request has never had to find out whether its process exists.

It has to exist in advance. Section 541.053(a) requires the controller to establish a process, not to improvise one on receipt.

When the appeal duty is triggered

The trigger is a refusal, and the statute connects the two sections explicitly.

Section 541.052(b) sets the ordinary response clock: the controller shall respond to a consumer request without undue delay, and not later than the 45th day after the date of receipt, extendable once by an additional 45 days when reasonably necessary.

Section 541.052(c) handles the case where the controller declines. If a controller does not take action on a consumer request, it must inform the consumer without undue delay, and not later than the 45th day after receipt, of the justification for declining to take action and provide instructions on how to appeal the decision in accordance with section 541.053.

So the appeal instructions are part of the refusal notice. A refusal that states a justification but gives no appeal route is not a complete refusal under the statute.

What section 541.053 requires

The section is short, and all four subdivisions do work.

Subsection (a) requires the controller to establish a process for a consumer to appeal the controller's refusal to take action on a request within a reasonable period of time after the consumer's receipt of the decision under section 541.052(c).

Subsection (b) sets the design standard: the appeal process must be conspicuously available and similar to the process for initiating action to exercise consumer rights by submitting a request under section 541.051. The word to read carefully is "similar." If a consumer can submit a deletion request through a web form in two clicks, an appeal process that requires a notarized letter is not similar, and the statute does not permit it.

Subsection (c) sets the deadline: the controller shall inform the consumer in writing of any action taken or not taken in response to an appeal not later than the 60th day after the date of receipt of the appeal, including a written explanation of the reason or reasons for the decision.

Subsection (d) routes the consumer onward: if the controller denies an appeal, it shall provide the consumer with the online mechanism described by section 541.152 through which the consumer may contact the attorney general to submit a complaint.

The two clocks are separate

This is the detail that causes double-counting in compliance calendars.

The 45-day clock in section 541.052(b) runs from receipt of the original request. The 60-day clock in section 541.053(c) runs from receipt of the appeal. They are sequential, not nested, and the second is longer than the first.

A request received on 1 March that the controller refuses on 14 April, appealed by the consumer on 20 April, must be answered on the appeal by 19 June. The extension available under section 541.052(b) applies to the response to the request. Section 541.053(c) contains no equivalent extension.

Every denial hands the consumer the regulator

Subsection (d) is the provision most likely to be missed, and it is unusual. In the ordinary course, a business that denies an appeal simply denies it. The TDPSA requires the denial to carry the route to the attorney general with it: the online mechanism described by section 541.152, through which the consumer may submit a complaint.

That changes how a denial should be drafted. The consumer will be one click from the regulator, holding the written explanation the controller was required to give under subsection (c). The reasons in that letter are, in practice, the reasons the attorney general will read first. Weak or boilerplate reasoning in an appeal denial is a document supplied to the complainant at the moment they are most likely to use it.

You cannot contract out of it

Section 541.054 closes the obvious workaround. Any provision of a contract or agreement that waives or limits in any way a consumer right described by sections 541.051, 541.052, and 541.053 is contrary to public policy and is void and unenforceable.

That covers the appeal right by name. Terms of service that purport to make request decisions final, or to shorten the appeal window, or to require arbitration of a privacy request, do not survive the section as to those rights.

What to build

The appeal process is a small piece of product work and it is best built alongside the request intake methods rather than after them, since section 541.053(b) measures the appeal route against the request route.

In practice that means one more form, reachable the same way the request form is reachable, a template refusal notice that states the justification and links the appeal form, a 60-day timer that starts on appeal receipt, and a denial template that carries the attorney general link. The whole of it is smaller than the 45-day response workflow it sits behind, and it is the part a regulator sees first when a consumer complains.

Compliance checklist

  • Build a standing appeal process before you need it. Section 541.053(a) requires the controller to establish a process for a consumer to appeal a refusal within a reasonable period after the consumer receives the decision under section 541.052(c).
  • Make the appeal route conspicuously available and similar to the process for submitting the original request under section 541.051, as section 541.053(b) requires. An appeal that is harder to file than the request it challenges does not meet the standard.
  • Trigger the appeal offer at the point of refusal. Section 541.052(c) requires you to tell the consumer, no later than the 45th day after receipt, the justification for declining and the instructions for appealing under section 541.053.
  • Diary the appeal at 60 days from receipt and answer in writing, with the reasons, under section 541.053(c).
  • On any denial, include the section 541.152 online mechanism for contacting the attorney general, as section 541.053(d) requires.
  • Do not try to contract around any of it. Section 541.054 makes any provision of a contract or agreement that waives or limits a consumer right described by sections 541.051, 541.052, or 541.053 contrary to public policy, void, and unenforceable.

Sources

Last verified: 2026-09-18

Informational, not legal advice.