Checkbox Docs

Risk and decisions

Which items Checkbox always asks you to fix, which ones are your call, how accepting a risk works (owner only), and what reopens a decision.

Checkbox splits every item in your compliance plan into two kinds.

Do this. Three things are always asked for, and can never be accepted as a risk:

  1. the renewal terms clearly next to the purchase button, with consent (on your page, in your Stripe Checkout settings and on every live Payment Link);
  2. easy online cancellation (your own cancel path and your billing platform's self-serve cancel);
  3. the required reminder and acknowledgment emails.

They cost next to nothing in sign-ups and help prevent disputes (Stripe recommends a clear cancellation policy that customers agree to: Preventing disputes). If you or your agent try to accept, decline or mark one of them not applicable, Checkbox says no and explains why (the API answers 409 do_this_not_acceptable).

The first item means your renewal terms next to the button and the sentence that clicking it agrees to them.

Not checked by default. Two small-state rules are not part of your plan, and Checkbox never reports them as passing:

  • 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);
  • D.C.: separate consent for free trials that convert to paid (D.C. Code § 28A-203(c)(2)).

No item, question or accepted risk is created for them, and a site reaches done without them. They are available if you want them: Checkbox Elements with extras="vt-dc", the snippet-rendered disclosure with ?extras=vt-dc, or POST /v1/checks/region for Stripe Checkout.

Your call. Everything else (a Terms section, including Terms wording that contradicts online cancellation or a refund promise, the yearly terms notice in some states, charge or price-change notices, a cancellation-confirmation email, the New York questions…). The cancel path itself is Do this; what your Terms say about it is your call. Each one shows:

  • the law, with its citation;
  • the risk if skipped for your business: very low, low, medium or high, with a one-line reason (how it is estimated);
  • the cost to sign-ups of fixing it: none, small or noticeable.

You choose Fix or Accept risk.

Accepting a risk

  • Only the owner of the Checkbox organization can accept a risk, signed in to the dashboard (the site's To-do page), with a short reason.
  • Checkbox records who accepted it, when, the reason and what it knew of your business at the time (aggregate subscriber counts only, never names or emails).
  • The item then reads Risk accepted. It is never shown as passing, and the plan never says "Checks pass" while one is accepted: once every Do-this item is met and every Your-call item is met or accepted, the plan status is risk_accepted ("Done · risk accepted").
  • You can take an acceptance back at any time ("Fix it instead").

AI agents propose, never accept. An agent may call proposeRiskAcceptance (over MCP: call_api with operation_id: "proposeRiskAcceptance") with a reason. That sends you a link: nothing is accepted until you open it, signed in, and confirm with a reason in your own words (a reason that repeats the agent's word for word is recorded as the agent's). On a Your-call item, an agent's updateTask with wont_fix or not_applicable is the same proposal. An API key cannot accept a risk in any other way (answerTask has no such answer, and setting a finding to accepted_risk is refused for API keys). In the dashboard, marking a finding "Risk accepted" needs the owner role, is refused for a Do-this item, and is recorded like any other acceptance.

What reopens a decision

Checkbox checks these at every plan read and in the background. When one fires, the item reopens with the reason:

  • the subscribers the item's laws reach grow by at least 50% and by at least 25 since you accepted;
  • your business moves up a size band (fewer than 100, 100 to 1,000, 1,000 to 10,000, more than 10,000 subscribers);
  • the law Checkbox checks for that item changes;
  • your 90-day dispute rate rises a quarter of a percentage point or more above what it was;
  • the item comes to cover a requirement or a state you did not accept;
  • Checkbox did not know your subscriber numbers when you accepted (or only had an estimate), and now reads them from live Stripe;
  • 12 months pass.

When a decision reopens, Checkbox tells you through your notification channels, with the reason.

In the API, MCP and CI

  • Each task in the compliance plan has kind (do_this or your_call), risk_if_skipped, conversion_impact and risk_decision (open, fixed or accepted, with the reason, when, and revisit_triggers). The plan has exposure, exposure_summary and, while Your-call items are open, owner_decisions: one message to send the owner. Once every Do-this item is met, the plan's next_action is that one decision (decide_your_call); an agent may still fix any of the items.
  • checkbox ci: a failing Do-this item fails the run as before; an open Your-call item is "needs review" and does not fail the run unless you pass --strict; an accepted item (read with --online) is listed and never fails the run.

Not legal advice: the levels are estimates, and the law stays what it is.

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.