Legal and compliance
Runner prepares the binder. Your counsel does the judging.
Every business already has a lawyer. What they do not have is a straight answer to "what exactly are we serving, where, and what changed since you last looked at it?" Runner assembles that, and stops there.
Runner does not give legal advice, does not review a contract, and does not approve anything. Nothing it produces makes a business compliant with anything. It prepares a package for the lawyer that business already has.
What is in the package
The copy you actually serve, pulled from what serves it
Consent notices, chat disclosures, recording disclosures. Each one is read from the code that renders it to a visitor, so what your lawyer reviews is the same text a visitor sees, down to the character. Nothing is retyped into the package, because a retyped string is one edit away from being wrong.
A cover memo that says what is waiting on the review
One page at the front, splitting what is live today from what is held back until somebody approves it. A lawyer triages those differently, and being told which is which is most of the work of reading a stack of documents cold.
A specific question per document, never “please review”
Each question is built from that document's own recorded state — the version, the jurisdiction it was written for, whether a human has cleared it. A question somebody can answer is worth more than a document somebody has to interpret first.
A blank stays blank
Where a setting has not been decided — a retention period nobody has set — the package shows the gap and asks about it. It never fills one in with a number that looks plausible.
What changed since the last review
Official sources are read on a schedule and matched against the assumptions your setup relies on, so the next package opens with what moved rather than starting from nothing. Sources today are the United States, the European Union and South Korea.
Exported as Word or PDF, addressed to a person
The package leaves as a file your firm can mark up in the tools they already use, and it can be shared with a reviewer who has no login here.
Where preparing ends and deciding begins
Approval is a human decision, and the software has no way to make it
Copy that has not been cleared by a reviewer carries a pending flag, and nothing in the product can clear it — not a scheduled job, not a vendor's response, not an AI. Copy that has not been cleared is never shown to the public; the code refuses to publish it.
It reports what is served. It never says what it means
The package states which copy is live, which version it is, and whether a human has cleared it. It does not write prose about the law, and it never asserts that anything complies with anything.
The law comes from official sources, without a vendor account
Primary law and regulation are read directly from the official publishers. A business can add its own legal-data account on top, and that only ever adds to what is already there — the watch works when nobody connects anything.
See it against your own copy
Access is by application. A package is built from what your own properties serve, so it is worth having the properties connected before the conversation.