Terms of use — PackAuth

What PackAuth is

PackAuth is packaging lifecycle compliance infrastructure. It resolves the rule packs you hold for the markets you declare. It runs deterministic checks over the data you supply, records the result, and holds the approvals and release certificates that follow.

It is a system of record and a system of enforcement.
It is not a regulatory adviser and never acts as one.
Every capability is an API endpoint before it is a screen.

What we do not claim

PackAuth checks what your rule packs cover, for the markets those packs cover, against the data it was given. That boundary is the point, so we state it plainly.

A market with no rule pack reports not covered, never a pass.
A pack that applies but is unpurchased is reported, not skipped.
A clean run means nothing the engine checked raised a finding.
It does not mean the packaging is compliant. Those differ.

Your responsibilities

You are responsible for the accuracy of the formula, specification, artwork and evidence you supply. PackAuth checks what you give it. It cannot tell that a supplied input is simply wrong.

A rule that cannot run blocks. An unrun rule is not a passed rule.
You remain responsible for packaging you place on a market.
Approving records who decided, on what evidence, at what version.
It does not transfer that responsibility to us.

Change and availability

Rule packs change when the regulations behind them change. A pack version change sends any live approval that relied on it back to revalidation required. That is intended behaviour, not a fault.

11 change classes demote a live approval automatically.
The lifecycle has 24 states and 39 legal transitions.
Support levels are set out in the contract for your plan.
Where this page and that contract differ, the contract governs.