Skip to main content
FinocketFinocket
Get Started

Consent & compliance

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.

Start freeAll modules

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 we're 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.

Campaigns in Finocket: sending-hours, consent posture and the message templates below
Finocket dashboard showing earnings, spend and outstanding at a glance
What it does

Inside Consent & compliance

01

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.
Campaigns in Finocket: sending-hours, consent posture and the message templates below
02

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.
Finocket dashboard showing earnings, spend and outstanding at a glance
03

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.

Consent & compliance

A blocked send keeps its copy

04

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.

Consent & compliance

Data-subject requests (DSR)

05

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.

Consent & compliance

Jurisdiction-aware rule packs

More in Consent & compliance

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 the rest of Finocket

Email & sequences
Every send is resolved against the consent ledger and suppression list before it can leave.
Forms & lead capture
Every form submission files its consent proof into the ledger automatically.
CRM & deals
A contact's consent state travels with their record through the pipeline.
QR & tracking
Leads attributed from a scan carry a consent state the ledger tracks.

Part of Outreach & compliance. See how every module connects.

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.

You can prove every message you sent was wanted, and act on a data request the day it arrives.

Where this wins

Consent-first outreach (consent ledger + unsubscribe)Xero does not have thisOne enforced send chokepoint with a logged decision per messageZoho CRM does not have this

Learn how it works

Email, campaigns and consent

Launch email campaigns with audience counts up front while one send chokepoint applies consent, suppression, your own sending hours and your country's rules to every single message. Blocked sends are logged, never silently dropped.

CRM & deals: pipeline, follow-ups and the customer ledger

Work a sales pipeline inside your books: auto-created deals for every captured lead, one-tap invoicing from a deal, follow-ups on WhatsApp or email, a per-client money ledger, and consent-safe lead import.

Leads: capture, score, route and respond on time

Every enquiry (form, QR, booking, WhatsApp, call, email, SMS, voice note, or one you add by hand) lands on one deduplicated Leads board, gets scored A–D, assigned to a teammate, and started on a first-response timer.

Browse the full help book

Ready to ditch the spreadsheet?

Free for solo users until 31 Dec 2026 — no partner code needed. ₹99/month after that. No credit card. Your books stay yours.

Start freeLog in