Sales Lab · Trust infrastructure
Every cloned voice. Every consent. On a chain.
Voice cloning has a consent problem. We solved it on day one: every voice the Realism Engine clones is registered in a public, append-only ledger with a hash chain. You can verify any subject’s consent history with one HTTP request.
01 · Append-only
Grants and revocations are never edited or deleted. A revocation is a new entry that points at the prior grant. The previous state is always recoverable.
02 · Hash-chained
Each entry's hash includes its content + the previous entry's hash. Tamper one byte → the chain breaks visibly. Anyone with the data can verify.
03 · Public read
GET /api/consent-ledger?subject=<handle> returns the full chain + a verification result. No auth needed. Auditors, journalists, the subject themselves — all can walk the chain.
04 · Signed attestations
Each entry can carry a URL to a counter-signed PDF (DocuSign / Adobe Sign). The hash is what proves the entry exists; the attestation proves what was agreed.
Try it
curl https://saleslab.cloud/api/consent-ledger?subject=demo-subject
{
"ok": true,
"data": {
"entries": [...],
"verification": { "ok": true },
"entry_count": 4
}
}Why we built this before the regulators asked
Voice cloning is a wedge issue. Synthetic-media legislation is coming. We don’t want to be the vendor scrambling to retro-fit consent infrastructure when the FTC comes knocking. The ledger has been live since Sales Lab’s first cloned voice; the EU AI Act compliance work is a footnote on top of the work already done.