Checkbox Docs

What a passing check means

What Checkbox checks mechanically, what still needs a person's judgment, and the evidence a pass leaves behind — so you know exactly what "Checks pass" covers.

Checkbox works like CI for the automatic-renewal laws. It checks, every time, the requirements a machine can check, flags the ones that need a person's judgment, and keeps signed evidence of what it saw. "Checks pass" means every check that applies to your site was observed and met its cited rule. It is not a legal opinion and does not guarantee compliance; the legal disclaimer applies.

Don't rely on Checkbox for legal certainty: if you need a legal opinion, talk to a lawyer. That said, every rule is written from the text of each law in the catalog and cited to it, and every release is tested against an accuracy set of nearly 1,000 cases (more than 1,300 labelled results) covering different page layouts, Stripe settings, emails and wording, with zero false passes on that set, plus more than 6,000 automated tests. We have high confidence in what Checkbox reports.

What Checkbox checks for you

Each of these is observed on your real pages, emails, billing settings or test subscriptions, and judged against the rule's cited text:

  • Before the purchase: the renewal terms (that it renews, the price, how often, how to cancel, trial terms) appear next to the purchase button, and the consent box starts unticked. On Stripe Checkout and Payment Links, the parameters are read from Stripe.
  • After the purchase: the acknowledgment email restates the terms and how to cancel.
  • Before a charge: trial-ending, renewal, yearly and price-change notices go out in the window each law sets, with the right content.
  • Cancellation: subscribers can cancel online, the cancel option can be found, the flow is not stuffed with obstacles, and a confirmation is sent. A Stripe test-mode subscription is signed up and cancelled end to end to prove it.
  • Your Terms: they do not contradict online cancellation or the renewal terms.

A check never passes for lack of evidence: something Checkbox could not see reads "Not checked yet", not pass (limits).

After setup: monitoring

Changes after setup are caught within about an hour, and at once when you run a check (Check now, verify_site, a test run). Live sites are scanned every hour by default, and every scan re-reads your Stripe settings first. The snippet also asks for a new look when a page it is on changes.

When something a passing check relied on changes (a page, an email template, a Stripe price or setting, your Terms), Checkbox checks it again right away. Until that finishes, the check keeps its last result: nothing reads as broken unless Checkbox sees it broken. If the new check fails, it reads "Needs a fix" and the owner gets an alert. API and MCP results carry data.rechecking (with why and since when) on a check that is being checked again, for those who want to see it.

One thing is different during setup: the site's own cancel button counts only after a test run pressed it and it worked. Until then the cancellation checks read "Not checked yet".

What still needs a person

Some requirements depend on facts or judgment a machine cannot settle. Checkbox does not guess; it asks the owner and records the answer as theirs, separate from what it observed:

  • Close calls on "clear and conspicuous" (for example a renewal line that is legible but not set apart), shown as "needs review" with the measurements.
  • Facts only the business knows, such as how a New York subscriber agreed to get notices by email.
  • Cancellation by phone or chat, and emails sent where Checkbox cannot receive them.
  • Claims beyond the automatic-renewal rules (general consumer-protection law), and laws outside the catalog.

Not checked by default (never reported as passing; available if you want them, see Checkbox Elements):

  • Vermont: bold renewal terms for plans of 1 year or longer, and a separate opt-in to the renewal for those plans.
  • D.C.: separate consent for free trials that convert to paid.

The proof a pass leaves behind

The checks tell you what to fix. The evidence is what you can show later, in a chargeback, a demand letter or a regulator's question:

  • Consent receipts: for each checkout, the renewal terms as rendered next to the button and the consent the subscriber gave (receipts).
  • Notice records: every required email Checkbox saw or sent, with its date and content.
  • Check history: what was observed (screenshots, page HTML, emails, settings), when, and against which version of the rules.

All of it is stored hash-chained and signed, and exports as a ZIP with a standalone verify.mjs that anyone, including your lawyer or the other side, can run to check it has not been altered (evidence).

For your lawyer

Checkbox does the repetitive checking and keeps the record; your lawyer makes the legal calls. For counsel is a one-page summary of the scope, how verdicts are reached and how to verify the evidence.

Checkbox is compliance software, not a law firm; nothing in these docs is legal advice (details). You remain solely responsible for your subscription program, and Checkbox takes on no legal liability for it (Terms). Checkbox is a System1 company; Trust center · Status. For AI agents: every page is available as Markdown at the same URL plus .md; the index is /llms.txt.