Legal
Every artefact is versioned and dated. A material change flips the re-acceptance flag, which is what triggers the in-product acceptance prompt — the wording you agreed to is provable afterwards, not asserted.
Terms of Service
The contract between your organisation and us: what we sell, what you may submit, and how either side ends it.
Privacy Policy
What personal data we hold as a controller, what we only process on your instruction, and how long each is kept.
Data Processing Agreement
The Article 28 contract. Clickwrap on every plan, not an enterprise-only negotiation.
Acceptable Use Policy
What you may not submit and what we do when someone does it anyway.
Accuracy Policy
Which checks are deterministic, which are probabilistic, how catch-all and unknown are handled, and what you are charged for each.
Refund Policy
The refund decision matrix, the window, and the moment the clock starts.
What a version bump actually does
- A material change to the Terms, DPA or Acceptable Use Policy requires re-acceptance.
- Until it is accepted, three surfaces close: bulk upload, API bulk submit and connector sync.
- Nothing else closes. Reading your dashboard, downloading existing exports and downloading invoices stay open, because a terms dispute must never trap your data.
- There is a 30-day grace period from the effective date, during which you see a banner and the gate is not applied.
- Typos and contact-address corrections never gate anything.