Skip to content

Consent and preference management

One place where customers say how they want to be contacted, and every system obeys it.

Prefer is a central record of customer consent and preferences per channel, purpose and brand, checked through an API by every sending system. It is built for companies with more than 100,000 contacts.

No account. No card. No sales call.

  • Consent per channel, purpose and brand
  • Checked by every sending system via API
  • A preference centre instead of all-or-nothing

Could you show what a customer consented to, and when?

Answer eighteen questions about where consent is stored, what each record holds, how it is enforced before sending and how requests are handled. See which checks are in place and what to look into first. Runs in your browser. No account, no card, no call.

Your consent records today

Answer for how things are today. Runs in your browser. Nothing is sent.

Where consent lives

Can you list every system that collects or stores consent?

When a customer unsubscribes in one system, is every other sending system updated?

Have you compared suppression lists across systems for contacts suppressed in one and active in another?

Is one system agreed as the record when systems disagree about consent?

What each record holds

Does each consent record show when it was given?

Does each record show where the consent was captured?

Is the exact wording the customer agreed to kept with the record?

Is consent recorded per channel rather than as a single yes or no?

Is consent recorded per purpose and per brand, where you have more than one?

Before anything is sent

Does every sending system check consent at the moment it sends, not only when a list is built?

Are campaign lists pulled fresh rather than reused from an earlier export?

Do you know how old each consent is, and what the rules you operate under say about that?

Choices and requests

Can customers choose channels and topics, rather than only unsubscribing from everything?

Is a deletion request carried out in every system that holds the customer?

Can you answer an access request with everything held about a customer across systems?

Proof

Could you produce a customer's full consent history quickly if asked?

Is every change to a consent record logged, with what made the change?

Is a named person or team responsible for consent data across all systems?

Answer the questions to see your score. It updates as you go.

Method: yes scores a question in full, partly scores half and no scores nothing. Each is weighted from one to three by how much it matters to showing what a customer agreed to, and the score is the weighted share, as a percentage. Unanswered questions are left out. It is not a legal assessment.

One record of consent that every system obeys

A central system of record for consent and preferences, enforced before anything is sent and auditable when a regulator asks.

Consent in full detail

Every consent and preference is stored per channel, per purpose and per brand.

Timestamp, source and wording

Each consent records when it was given, where it came from, and the exact wording the customer agreed to.

Enforced before every send

Every sending system checks an API before it sends, so one set of preferences is enforced everywhere.

A real preference centre

Customers choose channels and topics in a single preference centre, rather than facing an all-or-nothing unsubscribe.

Audit trail for regulators

A full audit trail shows what each customer consented to and when.

Deletion and access requests

Deletion and access requests are honoured across systems.

The problem

Companies collect consent in a dozen places and store it in a dozen systems that disagree.

A customer unsubscribes from email and keeps receiving texts, or opts out entirely and is contacted anyway because a campaign pulled from a stale list.

This is both a compliance breach with real fines and the fastest way to destroy trust, and nobody can prove what a customer consented to or when.

Who it is for

  • Marketing leaders

    Leaders at companies with more than 100,000 contacts who need every campaign to respect what customers chose.

  • Data and compliance leaders

    Teams who must be able to prove what a customer consented to, and when, across multiple channels and systems.

  • Multi-channel consumer businesses

    Retail, financial services, telecoms, travel and media companies whose consent is collected in many places.

How it works

Prefer, from the first step to the result.

  1. 1

    Run the free Consent Audit

    Upload contact and suppression lists from up to three systems.

  2. 2

    See the contradictions

    Suppressed in one system and active in another, missing sources, and consent too old to rely on.

  3. 3

    Centralise consent

    Every consent and preference in one system of record.

  4. 4

    Enforce it at send

    Every sending system checks the API before it sends.

Questions people actually ask

What does the free Consent Audit find?
Contacts suppressed in one system and active in another, consents with no recorded source or wording, and records whose consent is too old to rely on under current rules. You upload contact and suppression lists from up to three systems.
How are preferences enforced?
Through an API that every sending system checks before it sends.
What is recorded for each consent?
The channel, purpose and brand, together with the timestamp, the source and the exact wording the customer agreed to.
Can customers choose what they receive?
Yes. A single customer-facing preference centre lets people choose channels and topics instead of an all-or-nothing unsubscribe.
Can we show a regulator what a customer agreed to?
Yes. A full audit trail records every consent and preference, with its timestamp, source and wording.
Does it handle deletion and access requests?
Yes. Deletion and access requests are honoured across systems.
What does it cost?
1,200 dollars a month up to 500,000 contacts, 3,400 dollars a month up to 5 million contacts, and enterprise pricing above that. The audit is free.
Why should I trust the consent records check?
The score counts the checks you can answer yes to, in your browser. It is not a legal assessment and cannot find individual records; the free Consent Audit compares contact and suppression lists from up to three systems to find where they contradict each other.

Pricing

The Consent Audit is free. Monthly pricing is set by the number of contacts.

  • Consent Audit

    Freelists from up to three systems

    Find where your systems disagree about consent.

    • Suppressed in one system, active in another
    • Consents with no source or wording
    • Consents too old to rely on
    Get in touch →
  • Up to 500,000 contacts

    Recommended

    $1,200per month

    The central consent system of record.

    • Consent API for every sending system
    • Preference centre
    • Full audit trail
    Get in touch →
  • Up to 5 million contacts

    $3,400per month

    The central consent system of record.

    • For larger contact bases
    Talk to us →
  • Enterprise

    Customabove 5 million contacts

    For the largest contact bases.

    • Priced for your volume
    Talk to us →

Prices in USD.

Could you show what a customer consented to, and when?

Answer eighteen questions about where consent is stored, what each record holds, how it is enforced before sending and how requests are handled. See which checks are in place and what to look into first. Runs in your browser. No account, no card, no call.

Open the free tool

It runs in your browser. Prefer never sees your inputs.