Obligations
It is the most-searched shape of this question and the least useful one. A list of statutes by state tells you what exists. It does not tell you which of them reaches the thing you actually run — and those are very different lists.
Why the list is the wrong shape
This is not an argument that state-level information is useless. It is an argument that the list is the beginning of the question rather than the answer to it.
A statute in a state you touch may not reach your deployment
Every one of these instruments has conditions — entity thresholds, activity triggers, subject classes, exemptions. Being present in a state does not put you inside its statute.
A statute in a state you are not in may reach you anyway
Obligations attach by where the affected people are. A list organised by your locations is organised by the wrong axis.
The list is out of date the week you read it
Bills commence, provisions phase in on separate dates, and amendments renumber things. A static list is a snapshot presented as a map.
What we publish instead. The AI Tracker shows what exists and what is moving, updated continuously and with enacted law kept separate from pending legislation. The Intelligence Library shows each instrument with its jurisdiction, regulator and pinned provisions. Neither is a substitute for a determination, and neither pretends to be.
The shape of answer that works
It is a longer answer and it is the only one you can act on.
Derived from where the affected people are, not from where the organisation is registered.
Each tested against the deployment’s facts rather than assumed from the state’s reputation.
With the reason. This is the half that answers a regulator asking why you did not act on something.
Twelve states is twelve questions
A determination produces the per-state answer for one deployment, cited, including the states that were assessed and ruled out.