← Back

Guide · Published November 14, 2026 · Reviewed November 14, 2026 · Ingenious AI team · Not legal advice

← All guides

How to Log Opt-Outs and Prove They Were Honored

The short answer: An opt-out is honored in the workflow and proven in the record — two different things, both required. California's kit duty compresses them into one line: honor the opt-out and record that it was honored. Connecticut's profiling opt-out adds the service standard: answer within 45 days (one extension allowed), with an appeal if denied. A provable opt-out record has four fields per request: receipt date, the decision it concerns, the honoring action taken (file flagged out of the automated path), and the confirmation that the tool did not run on that file. The fourth field is the one most logs omit — and the only one that actually proves honoring.

Check your duties and dates — free Build your first notice — free

What is opt-out logging? It is the per-request record of an ADMT or profiling opt-out: who asked, when, for which decision, and what the business did. The kit stores opt-outs in the same hash-chained decision record as the notices, so an opt-out can be audited against the decision it belongs to. The opt-out duties themselves are in California ADMT Opt-Out Requirements and Connecticut Profiling Opt-Out Rights.

Field one and two: receipt, and the decision it concerns

Log receipt with the date and the channel — in-flow control, email, phone note — because Connecticut's 45-day clock runs from receipt and every later question starts there. An opt-out logged when it is processed, rather than when it arrived, quietly rewrites the clock in the business's favour; the record should be incapable of that rewrite, which is one reason the kit logs at intake.

Link the request to the decision or the person-file it concerns. An opt-out that floats free of the decision data cannot drive the honoring step: somebody — or some system — must be able to answer 'which pending files does this request cover?' within the same working day. Where the person has no pending decision, record that too; the opt-out still governs future automated use of their data for covered decisions.

Field three: the honoring action, taken before the run

Honoring is a flag with consequences: the file leaves the automated path and is decided by the human route. The log should show the action and its timing relative to the tool's run. If the flag was set after the tool had already scored the file, that sequence is a finding to record honestly and fix procedurally — not a detail to smooth over in the log.

The human route must exist in reality: staffed, with decision authority, producing outcomes that reach the person. Log which route handled the file (team or reviewer role, not necessarily a name in every export) so the honored path is visible. A file flagged out of automation into a queue nobody works has been excluded from a decision, not opted out into one.

Worked example: Fairhaven Consumer Finance

Example — fictional business, real duty structure. Fairhaven is a fictional California lender that rebuilt its opt-out logging around the four fields. Its first audited month:

Field four: proof the tool did not run

The strongest honoring evidence is negative evidence: the automated run list for the period, with the opted-out file absent from it. If your tooling can produce run logs per file, reconcile them against the opt-out register monthly: every opted-out file should show zero automated runs after its flag date. Discrepancies are incidents — investigated, recorded, and answered to the person where their file was affected.

Where tooling cannot produce per-file run logs, the substitute is a process control with its own record: the flag lives in the system that assembles the tool's input batch, so exclusion is mechanical rather than remembered. Either way, design for the audit question in advance, because it will be asked in its exact form: 'show me this person's opt-out, and show me the tool never ran on them afterwards.'

Denials, appeals, and extensions: the edges of the log

Not every request is granted: a request may fall outside the duty (no opt-out applies; an exception position is taken) or outside the Act's scope. Denials belong in the same log with their reasoning, because Connecticut requires an appeal offer on denial — the appeal, its reviewer, and its outcome are further entries in the same chain. A log containing only granted requests is a log that has been edited by selection.

Extensions get the same treatment: Connecticut allows one 45-day extension; the log shows the extension was taken, when, and that the eventual answer met the extended date. The kit's record treats each of these as an appended event with its date — the sequence is the evidence, and sequences cannot be reconstructed credibly after the fact.

The monthly audit: fifteen minutes, four numbers

Close the loop with a monthly audit small enough to actually happen: requests received, median days to answer, honored files reconciled against run logs (exceptions found), and appeals with outcomes. Four numbers and a list of exceptions, reviewed by a named owner, filed with the record. The audit's value compounds: it catches the broken email route, the flag that stopped propagating, the vendor update that reset an integration — in the month they happened.

If the audit finds a file the tool ran on after opt-out, the response pattern is fixed in advance: record it, assess the decision's validity with advice, inform the person where their decision was affected, and fix the mechanism. Handled that way, an audit exception is evidence of a working system. The wider record discipline is in How to Keep ADMT Records for Three Years.

  1. Log every opt-out at receipt — date, channel, and the decision or file it concerns — never at processing time
  2. Make honoring a mechanical flag: file out of the automated path before the run, decided by a staffed human route
  3. Reconcile the opt-out register against the tool's run log monthly — opted-out files must show zero later runs
  4. Record denials with reasoning and an appeal offer, and extensions with their dates, in the same chain
  5. Run the four-number monthly audit (received, answer time, reconciliation exceptions, appeals) with a named owner

Sources, as carried in the kit's own data: the duty summaries in app/rules.py and the checker data in app/checker_data.py, verified against primary or authoritative sources on October 28, 2026. Run the free duties checker for your jurisdiction, decision type, and the tool's role, and compare the kit's plans for the record, builder, and review queue. More from Ingenious AI is on the hub.

Build your first notice — free

Related guides

See all ADMT guides for the full set.

Frequently asked questions

What should an opt-out record contain?

The receipt date and channel, the decision or file it concerns, the honoring action taken (the file flagged out of the automated path), and the confirmation — by run-log reconciliation or an equivalent control — that the tool did not run on that file afterwards.

How fast must opt-outs be answered?

Connecticut sets the standard for its profiling opt-out: within 45 days, with one 45-day extension allowed, and an appeal offered if a request is denied. California's duty is to honor the opt-out and record that it was honored.

What proves an opt-out was honored?

Negative evidence: the tool's run record for the period showing the opted-out file absent after its flag date, reconciled monthly against the opt-out register — or a mechanical exclusion control whose operation is itself recorded.

What if we deny an opt-out request?

Record the denial and its reasoning in the same log, and offer an appeal (Connecticut requires the appeal offer on denial). A log with only granted requests is incomplete.

Where should opt-outs be stored?

With the decision record for the person concerned — in the kit, the same hash-chained record as the notices and explanations, held for three years.

Build your first notice — free