ReviewDesk
← Back

ReviewDesk guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

How does the California ADMT opt-out work for consumers and businesses?

Generate a free adverse-outcome letter — no sign-up Build a free pre-use notice See pricing

The short answer. California's ADMT regulations give a consumer the right to opt out of automated decision-making technology used for a significant decision about them, subject to defined exceptions — and where a business relies on the human-appeal route instead, that route must be real. For businesses the opt-out is an operations build: a working request channel, a manual decision lane, and records. ReviewDesk routes California opt-outs into the same inbox as review requests on paid plans, with the clocks running.

What is the California ADMT opt-out?

The California ADMT opt-out is a consumer right under the CCPA ADMT regulations: before or when automated decision-making technology is used for a significant decision, the consumer may direct the business not to use it for them. The business must then make the decision without the ADMT, unless an exception applies. The right is introduced to the consumer in the pre-use notice, which is why notice and opt-out machinery must be built together.

What does the consumer actually do to opt out?

The act itself should be simple: a clear route, presented in the pre-use notice, that a person can complete without an account, a phone call during office hours, or a scavenger hunt through settings pages. The consumer identifies themselves and the decision process, submits the opt-out, and receives confirmation. Everything after that simplicity is the business's problem — which is precisely the regulation's design. Rights that are easy to state and hard to exercise are the historical failure this framework is written against, so the measure of your implementation is the consumer's experience, not your policy text.

Confirmation deserves care. The consumer should leave with something durable — a reference, a timestamp, a statement of what happens next and how long the manual route will take. ReviewDesk logs the opt-out as a docket event with its timestamp, so the confirmation the consumer holds and the record the business holds describe the same event. If a dispute later asks 'did this person opt out before the decision?', both sides are reading one timeline.

What must the business build behind the opt-out?

A manual lane that is genuinely equivalent. When a consumer opts out, a person must make the significant decision from the underlying information — the application, the documents, the criteria — without the ADMT's output quietly shaping the result. That means the opted-out file must be separable in your pipeline, the criteria must exist in a form a human can apply, and the staffing must exist to decide within a timeframe comparable to the automated route. An opt-out that adds three weeks is a penalty wearing a procedure's clothes.

It also means discipline about leakage. If the human decision-maker can see the tool's score 'for context', the opt-out has been honoured in form only. Build the lane so the ADMT output is not generated, or not visible, for opted-out consumers, and record that in the case file. The workflow design questions are worked through in the opt-out versus appeal guide, because most businesses end up operating both routes side by side.

When do exceptions apply — and how should they be handled?

The regulations recognise circumstances where an opt-out need not be offered — the paradigm case being where the business provides a qualifying opportunity to appeal to a human who can overturn the decision, and other defined situations such as certain security and fraud contexts. Exceptions are where implementations go wrong in both directions: businesses claiming exceptions they do not qualify for, and businesses ignoring the conditions attached to the exception they legitimately use. If you rely on the appeal route, the appeal must meet its conditions — a real human, real authority, a real answer — and your notice must say so plainly.

Record the exception determination per workflow, not per incident. The scope-test habit applies here too: a timestamped worksheet entry stating which route the workflow offers and why. When a consumer challenges the absence of an opt-out, the answer should be a record made in advance, not a rationale assembled under pressure. ReviewDesk's California workflow records the route in the workflow itself, so the notice, the inbox configuration and the evidence pack all describe the same arrangement.

How do opt-outs interact with decisions already in flight?

Timing questions are inevitable: the consumer opts out after applying but before the decision; the decision was made yesterday, the opt-out arrives today. The defensible operating rule is that an opt-out received before the decision governs that decision, while an opt-out after the decision converts into the post-decision rights — explanation, correction, appeal or review. What is not defensible is a pipeline that cannot tell you which side of the line a given opt-out fell on. Timestamps settle these questions, which is why the inbox's docket discipline — every event, one timeline — is infrastructure, not bureaucracy.

Communicate the boundary in the confirmation itself. 'Your opt-out applies to decisions not yet made; for the decision made on 12 March, here is your explanation and your appeal route' is an answer a consumer can act on. Silence, or a generic acknowledgement, leaves them to discover the boundary by being decided about — the exact experience the regulations exist to prevent. The status-link pattern in the status-tracking guide shows how to keep the consumer informed without new correspondence for every step.

What records does an opt-out generate?

The request, the confirmation, the route taken, the human decision and its outcome — each timestamped, each attached to the consumer's case. Over time those records answer management questions as well as legal ones: how many consumers opt out, for which decisions, with what outcomes compared to the automated route. A persistent outcome gap between the manual lane and the automated lane is a signal worth investigating in either direction — it may reveal a tool problem, a manual-lane problem, or a notice that is frightening consumers unnecessarily.

Keep the records for the same three-year horizon as the rest of the decision file, exported through the evidence vault when needed. An opt-out honoured but unrecorded is, evidentially, an opt-out that cannot be shown to have been honoured. The record-keeping model is set out in the audit-trail guide; California opt-outs are simply one more event type on that single timeline.

How should the opt-out be described in the pre-use notice?

In the same plain language as the rest of the notice, with three specifics consumers scan for: that the right exists, how to exercise it in one action, and what happens afterwards — a person decides, in roughly what timeframe, with the same criteria. Avoid legal labels as the headline; 'Ask for a person to decide instead' communicates more than 'Exercise your ADMT opt-out right', with the formal term present for precision beneath it. The notice builder at /try/notice drafts this block from your workflow so the wording and the machinery are designed together.

Finally, test the route as a consumer would — from a phone, without an account, against the clock. Every business that has embarrassed itself on opt-outs believed its route worked until somebody tried it. The five-minute test is the cheapest compliance control in this entire guide, and the one most often skipped.

Your five actions for the California ADMT opt-out

  1. Offer the opt-out through one clear action in the pre-use notice — no account, no phone-only route, no settings maze.
  2. Confirm every opt-out with a reference, a timestamp and a plain statement of what happens next.
  3. Build a manual decision lane with equivalent criteria and a comparable timeframe — and keep ADMT output out of the reviewer's sight.
  4. Record, per workflow, which route you offer and any exception you rely on, with its conditions, before launch.
  5. Test the whole route as a consumer, from a phone, before the notice goes live.

Worked example: an opt-out honoured in a hiring pipeline

A fictional staffing platform — TalentHarbor — screens applicants for warehouse and customer-service roles in California. Its pre-use notice offers the opt-out in one tap. In February, 860 applicants are screened; 41 opt out. Those 41 files are never scored: recruiters assess them from the application and a short structured call, using the same published criteria. The median time-to-decision for the opted-out group is four working days against three for the automated group — close enough that opting out is a choice, not a punishment.

Of the 41, nine are hired, a rate in line with the automated cohort. One opted-out applicant who is declined asks why, and receives the same quality of explanation as any automated-route applicant — the reasons are human reasons, recorded at decision time. When the platform's annual review samples the opt-out file, every case shows the request, the confirmation, the unscored file and the human decision on one timeline. The right was not a paragraph in a notice; it was a lane in the operation.

Frequently asked questions

What is the California ADMT opt-out?

A consumer right under the CCPA ADMT regulations to direct a business not to use automated decision-making technology for a significant decision about them, subject to defined exceptions. The business must then decide without the ADMT, typically through a staffed manual route.

How does a consumer exercise the opt-out?

Through the route given in the business's pre-use notice — which should be a single clear action requiring no account. The business must confirm the opt-out and explain what happens next. In ReviewDesk, opt-outs land in the review inbox as timestamped docket items on paid plans.

Can a business offer an appeal instead of an opt-out?

In defined circumstances the regulations allow a qualifying human-appeal route. The appeal must be genuine — a human with authority to overturn — and the notice must describe the arrangement accurately. See the comparison guide.

What if the opt-out arrives after the decision?

It cannot unmake a decision already made; the consumer's post-decision rights apply instead — explanation, correction and appeal or human review. Timestamps on the request and the decision determine which side of the line the case falls on.

Is this guide legal advice?

No. ReviewDesk is templates and workflow tooling, not legal advice. The opt-out is summarised from the CPPA ADMT regulations as reported in our research; consult counsel for your situation.

Keep reading: California ADMT: should you offer the opt-out, the human appeal, or both? · How long must you keep ADMT decision records — and what should the audit trail hold? · What goes into California's annual ADMT risk assessment (due 1 April 2028)? · How does one decision trace become Colorado, California and EU evidence packs? · What is a hash-chained decision record — and why does immutability matter as evidence? · All ReviewDesk guides · ReviewDesk home · Try the free desk · Free letter generator · Free notice builder · Pricing

ReviewDesk is built by Ingenious AI. Templates and workflow tools — not legal advice.