# A consent ledger that proves you were allowed to send

> A per-contact consent ledger, a suppression list checked on every send, data-subject export/delete requests and jurisdiction rule packs. Currently in beta.

Canonical page: https://finocket.com/product/consent-compliance

Status: available

## What it solves

The risk in outreach is being able to prove, later, that the recipient agreed and that you honoured every opt-out. Reconstructing that after a complaint is impossible if it was never recorded. Finocket keeps an append-only consent ledger per contact and a suppression list that's checked before anything leaves, so the proof exists from the start.

## How it is different

Consent is wired into the one send chokepoint every message passes through, so a suppressed or non-consented contact simply can't be mailed, and blocked sends are logged rather than silently dropped. Data-subject export, delete and do-not-sell requests are first-class and email-verified. It's in beta today, usable via early access and not yet generally available.

## What it does

### Append-only consent ledger

Every contact's consent state is recorded in an immutable per-contact ledger. Corrections are new rows, so you can always show what was true when you sent.

### Suppression list on every send

A suppression list is checked at the send chokepoint before any message leaves, so opt-outs are honoured automatically, not by memory. Identifiers are canonicalised at the boundary, so an opt-out recorded in one phone-number format still blocks a send addressed in another.

### A blocked send keeps its copy

When the chokepoint refuses a message, the exact subject and body that would have gone out are recorded alongside the decision, so a compliance question later has an answer, rather than an empty row where the message used to be.

### Data-subject requests (DSR)

Export, delete and do-not-sell requests are first-class and verified by email, with the subject-rights machinery built in.

### Jurisdiction-aware rule packs

Rule packs for India apply sender identity and physical-address footers, one-click unsubscribe and jurisdiction rules at the one send chokepoint every message passes through.

### WhatsApp goes through the same door

Every dispatched WhatsApp message is linked to its consent decision in the database, so 'did this message have a lawful basis?' is a question you can answer with a query rather than an argument. A wa.me deep link is not a send path.

## Works with

- [Email and sequences that can't send without consent](https://finocket.com/product/email-sequences): Every send is resolved against the consent ledger and suppression list before it can leave.
- [Capture leads with consent proof built in](https://finocket.com/product/forms-lead-capture): Every form submission files its consent proof into the ledger automatically.
- [A sales pipeline that lives inside your books](https://finocket.com/product/crm-pipeline): A contact's consent state travels with their record through the pipeline.
- [Dynamic QR codes that turn scans into leads](https://finocket.com/product/qr-tracking): Leads attributed from a scan carry a consent state the ledger tracks.

## Frequently asked questions

### How does Finocket prove I had consent?

An append-only per-contact consent ledger records what was true when you sent (corrections are new rows, never edits), and a suppression list is checked on every send, so opt-outs are honoured automatically.

### Can I handle deletion and do-not-sell requests?

Yes. Data-subject export, delete and do-not-sell requests are first-class and verified by email, with India rule packs applied at the chokepoint.

### Is this generally available?

Yes. The consent and compliance layer is live and generally available.

---
This is the Markdown copy of https://finocket.com/product/consent-compliance, published by Demystify Systems LLP. It is not a separate page: cite the canonical page.
