Audience · consent & suppressions

Permission,
recorded as evidence.

Per-topic consent state and audited suppressions that are never silently deleted.

Permission first. Every brand distinct.
Why it matters

A boolean cannot answer a regulator.

Most platforms track consent as a subscribed flag on a contact. When someone asks how you obtained an address, on what basis you are processing it, or what happened between opt-in and unsubscribe, a flag has nothing to say.

SendNectar records consent as a stream of events with a lawful basis, a source, an occurrence time, and evidence — and suppression as a scoped, hashed, revocable, fully audited record rather than a deletion.

Capabilities

Consent & suppressions, in detail.

01

Per-topic subscription state

Consent is held per subscription topic per brand, so a contact can want product updates and not want promotions, with each state independently evidenced.

02

Consent events, not flags

Every change is an event: requested, granted, confirmed, withdrawn, or migrated — with the lawful basis and the source that produced it.

03

Hashed suppressions

Suppressed addresses are stored as hashes with a scope, a reason, and a source. The record proves the block without keeping the address in the clear.

04

Scoped, not global

Suppression scope is tenant, brand, or topic. Unsubscribing from one brand does not silently kill deliverability in another.

05

Revocable and audited

A suppression can be lifted with a record of who did it and why. Nothing is deleted quietly, and nothing is irreversible without a trace.

06

Enforcement you cannot disable

Bounce, complaint, and unsubscribe processing is structural. There is no plan, permission, or setting that turns it off.

The product surface

The consent record.

These are the actual fields on a consent event and a suppression — the shape of the answer when someone asks.

Event type
requested · granted · confirmed · withdrawn · migrated
Lawful basis
consent · contract · legal obligation · legitimate interest
Evidence
Structured proof of the interaction, plus an optional consent document reference
Source & timing
Where consent came from and when it occurred, distinct from when it was recorded
Suppression scope
tenant · brand · topic
Suppression reason
unsubscribe · complaint · bounce · policy, with the source that reported it

Bring your provider.
Keep your brands distinct.
Start today.

Set up your first workspace, connect a provider, and publish a workflow — free, in test mode, before you pay a thing.