Product / Consent management

Consent rules every team follows. Every agent too.

Capture consent on every form, enforce it on every send, and keep one set of rules no matter which team or agent built the campaign.

Marketo parity
MarketoYes
InflectionYes, consent rules enforced across every team
Capture

Consent captured where it's given

Forms carry consent fields that map straight to the contact, so the record shows what each person agreed to and when.

Enforce

One set of rules for every send

Unsubscribes, subscription preferences and consent rules apply to every email, whether a marketer, a CSM or an agent built the campaign. Agents can't route around them.

Compliance

Built for regulated teams

Inflection is SOC 2 Type II attested and supports GDPR, with a DPA available, and CCPA.

SOC 2 Type IIGDPRCCPA
SOC 2 Type II · GDPR · CCPASOC 2 Type II attested. GDPR supported, with a DPA available. CCPA supported.

How it works

  1. Add consent to formsFields map to the contact automatically.
  2. Set the rulesOps sets consent and preference rules once.
  3. Send anythingEvery campaign checks the rules before it sends.
  4. Show your workEach contact's record shows what they agreed to.

Questions buyers ask

Do agent-built campaigns follow the same consent rules?

Yes. Consent and preference rules apply to every send, whoever or whatever built the campaign.

Is Inflection GDPR and CCPA compliant?

Inflection supports GDPR, with a DPA available, and CCPA, and is SOC 2 Type II attested.

Where is consent stored?

On the contact, from the form or source where it was given.

Give every team speed without risking consent.

Book a demo and we'll walk through your consent rules.