# For counsel

> One page for a lawyer reviewing a client's use of Checkbox — what it checks, what it does not, how a verdict is reached, how to verify the evidence, and what Checkbox does not promise.

Checkbox runs automated checks of a business's subscription sign-up, emails and cancellation against U.S.
automatic-renewal laws. This page is for the lawyer reviewing that use. **It is not legal advice, it does not guarantee
compliance, and no lawyer has reviewed the rules**; the [legal disclaimer](https://checkbox.site/docs/legal) and the [Terms](https://checkbox.site/terms)
control.

## What is covered {#scope}

- **Laws:** federal law (ROSCA and Regulation E), 27 states, DC and New York City. Each [law page](https://checkbox.site/laws) lists the
  rules, their citations and links to the official text; the [open dataset](https://checkbox.site/laws/data) has every rule as JSON or CSV.
- **What is checked:** the checkout disclosure and consent, the confirmation and notice emails, and cancellation
  (settings in the billing platform, and test cancellations in Stripe test mode).
- **How it is seen:** a real browser on the rendered pages, the billing platform's API, emails received at a BCC
  address, and, in a code repository, the checkout parameters in the source.

## What is not checked {#not-checked}

- Pages behind a login, unless the site installs the in-page snippet (those results are marked as reported by it).
- Cancellation by phone or chat, and emails sent where Checkbox cannot receive them.
- Facts a machine cannot see, such as how a New York subscriber asked to get notices. These are asked of a person and
  recorded as their answer, not as an observation.
- Laws outside the catalog, and general consumer-protection claims (UCL, FAL, CLRA, FTC Act § 5) beyond the
  automatic-renewal rules. Some billing platforms expose fewer settings; [limits](https://checkbox.site/docs/concepts/limits) lists them.
- Not checked by default: Vermont: bold renewal terms for plans of 1 year or longer, and a separate opt-in to the
  renewal for those plans (9 V.S.A. § 2454a(a)(1)-(2)); D.C.: separate consent for free trials that convert to paid
  (D.C. Code § 28A-203(c)(2)). These are never reported as passing; a merchant can add them (Checkbox Elements
  `extras="vt-dc"`).

## How a verdict is reached {#verdicts}

Each check applies a cited rule to what was observed. **Pass** means it was observed and met the rule; a check never
passes for lack of evidence. **Fail** says what was seen and the fix. **Needs review** means the evidence is
incomplete, or the rule calls for judgment (for example "clear and conspicuous"), and a person decides. One
exception, so the label matches what the merchant can change: on a Stripe-hosted page (Checkout, Payment Links), where
Stripe sets the size and colour of the custom text and the merchant cannot restyle it, the clear-and-conspicuous
measurement (size, weight, contrast against the surrounding text) is reported as **Checks pass with a note**: the
note gives the measurement and what the merchant can change instead, and whether that is conspicuous enough stays a
call for the merchant or counsel. Hidden text still fails. The sample report (checkbox.site/sample-report) shows one. Every result
carries the rules and catalog versions and a catalog hash, so it can be reproduced. Details:
[checks and verdicts](https://checkbox.site/docs/concepts/checks).

## Evidence you can verify yourself {#evidence}

This is the record a client can produce in a chargeback, a demand letter or a regulator's inquiry: the terms each subscriber saw next to the button and the consent they gave, every required notice and when it went out, and what each check observed. [What a passing check means](https://checkbox.site/docs/concepts/what-a-pass-means) lists what is checked mechanically and what is left to judgment.

What Checkbox observed (screenshots, page HTML, emails, settings, consent records) is stored hash-chained and signed
([evidence](https://checkbox.site/docs/concepts/evidence)). A consent receipt downloads as a bundle with a standalone `verify.mjs` (Node.js,
no dependencies) that checks every hash and signature against Checkbox's published keys
([receipts](https://checkbox.site/docs/receipts#verify)).

## Accuracy and corrections {#accuracy}

The rules are written by the Checkbox team from the text of each law; [how they are kept accurate](https://checkbox.site/docs/accuracy)
describes the sources and reviews. Errors are fixed and listed with dates in the
[corrections log](https://checkbox.site/docs/corrections). To report one, email [support@checkbox.site](mailto:support@checkbox.site).
