The problem
A great pilot result you can’t use isn’t proof.
You run a pilot, it works — and then the proof gets stuck. Was the quote okay to publish? Can you show the logo? If someone changes their mind later, how do you take it down cleanly? Without a record, every reuse is a small risk.
Under GDPR, any proof that involves another party is only lawful on a stored, withdrawable consent basis. The Consent Engine builds that requirement into the workflow, so doing it right is the path of least resistance.
The flow
Request → grant → publish → one-click revoke.
Request — ask for one specific use: a quote, an outcome, a logo right.
- 01 · Request
Ask for permission, specifically
After a pilot lands, ask the customer for exactly what you want to use — a quote, an outcome, a logo right — stating where and how it will appear.
- 02 · Grant
They agree, on the record
The customer grants consent for that specific use. What they’re agreeing to is explicit, and their agreement is recorded — not buried in a thread.
- 03 · Publish
It becomes labeled proof
The consented quote, outcome, or logo right is published as a clearly-labeled asset in your Proof Vault — a Pilot outcome, then in time a Live reference.
- 04 · Revoke
One click withdraws it
Consent is as easy to withdraw as to give. One click unpublishes the proof immediately, everywhere it was shown.
Built for compliance
Consent logged, erasure honored, every step auditable.
GDPR Article 17 — the right to erasure
A data subject can have their personal data removed. Revoking consent unpublishes the proof immediately — withdrawal is as easy as the original grant.
A logged, auditable trail
Every request, grant, and revocation is recorded. You can show precisely what was permissioned, by whom, for what use, and when it changed.
Why this is the lawful and the efficient path
The loop closes: a consented outcome becomes a labeled asset in your Proof Vault
More of the system