The Consent Center
Consent management is essential to data protection and the trust of your supporters.
With the Consent Center, you can adapt how consent is collected, stored, and managed depending on your organization's needs and the regulatory environment you operate in.
You can choose between two modes:
Essential Compliance: A streamlined setup with one global consent for all communications. Covers core legal requirements (privacy policy, opt-out). Suitable for regulatory frameworks like CCPA/CPRA, PIPEDA, and similar laws.
Advanced Compliance: A more granular configuration that allows consent to be managed by purpose (newsletters, campaigns, events, etc.) and by channel (email, SMS, phone, etc.). Designed to comply with GDPR 2024/900 and stricter regulatory environments.
The configuration you choose determines how consent is collected across forms, petitions, events, and the mobile application, and how it is managed in contact profiles.
Choosing your Consent Mode
Each mode is designed for different regulatory environments and organizational needs.
Available Feature | Essential Compliance (No Checkbox) | Essential Compliance (With Checkbox) | Advanced Compliance |
Recommended for | USA (most states), Canada (PIPEDA), Australia | California (CCPA/CPRA), Brazil (LGPD), Mexico, New Zealand | EU/EEA (GDPR), UK (UK-GDPR), Argentina, Chile, Philippines, Thailand |
Consent checkbox | ❌ | ✅ | ✅ |
Consent Center | ❌ | ❌ | ✅ |
Multiple consent purposes | ❌ | ❌ | ✅ |
Channel-level consent | ❌ | ❌ | ✅ |
Export consent register | ❌ | ❌ | ✅ |
If you operate in the EU, UK, or a similar legal framework, we strongly recommend using Advanced Compliance mode.
Setting up your Compliance Center
To access your Compliance Center, go to Space settings > General > Privacy & Security > Consent Center.
Regardless of the mode you choose, you can configure the following from the Compliance Center:
Privacy policy: Add the link to your privacy policy page (hosted on your website or as an online document). This will be applied by default across all your public pages.
Displayed notice: A short message shown at the moment data is collected to give contextual information to your supporters. This notice appears on all forms and petitions you create.
Transparency disclaimer (if applicable): An upfront statement that discloses who is behind a communication and why it is being shown (for example, who funded or created an ad).
🇺🇸 For US organizations: A transparency disclaimer must be enabled when using Qomon to run targeted political ads or ads based on personal data, in compliance with FEC regulations. A template is provided directly on the platform.
🇪🇺 For EU organizations: The transparency notice is one of the requirements under the TTPA (Transparency of Targeted Political Advertising). It informs supporters about how their data is processed, who has access to it, and for what purpose. Once enabled, it automatically appears on all your public pages (forms, petitions, events, etc.).
Configuring purposes and channels (Advanced Compliance only)
If you are using Advanced Compliance mode, you will also need to configure consent purposes and communication channels.
In the Compliance Center, click "New purpose" and either:
Select a pre-built compliance template (GDPR-compliant templates are provided for EU organizations)
Or fully customize a purpose to match your needs
Purposes define what you are collecting consent for (example: newsletter, fundraising, events, advocacy, or a specific campaign). You can customize the consent wording for each purpose.
Channels define how you communicate (example: email, SMS, phone).
Consent period is set by default, but can be customized if needed.
Examples are provided directly on the platform to help you get started.
💡 Reminder: for Essential Compliance, one consent applies to all communications.
What happens to your existing consents?
Your existing consents are fully preserved.
When you set up the new Compliance Center, all current consents are automatically migrated into a "Generic consent" purpose. No action is required on your end.
From there, you can progressively build your new consent structure by refining purposes, channels, and consent granularity.
You may also run a re-consent campaign if you want to accelerate the transition.
Collecting Consent in Qomon
Consent can be collected through several entry points in Qomon, including:
Forms
Petitions
Surveys
Event registrations
Mobile contact creation
WebApp contact creation
How consent is recorded depends on the consent mode you selected.
Consent on Forms, Petitions, Surveys, and Events
Here's how consent is collected on forms, petitions, surveys, and Event actions:
Feature | Essential Compliance (no Checkbox) | Essential Compliance (with Checkbox) | Advanced Compliance |
Consent Center | ❌ | ❌ | ✅ |
Checkbox displayed | ❌ | ✅ | ✅ |
Privacy policy text | ✅ | ✅ | ✅ |
Consent behavior | Submitting the form constitutes acceptance of the Privacy Policy and consent to be contacted | Checkbox determines whether consent is accepted or refused | Users explicitly accept or refuse specific consent purposes |
For Essential Compliance:
without Checkbox: submitting a form or petition constitutes acceptance of the Privacy Policy and consent to be contacted. The privacy policy text is displayed to ensure transparency.
with Checkbox: if the checkbox is checked, the consent is recorded. If it is unchecked, the consent is refused.
For Advanced Compliance: contacts can explicitly accept or refuse specific consent purposes. Each purpose is presented with a checkbox and a description.
Consent Management on Mobile
When creating or editing contacts in the Qomon mobile app, consent collection also depends on the selected mode.
Feature | Essential Compliance (No Checkbox) | Essential Compliance (With Checkbox) | Advanced Compliance |
Consent screen before saving a contact | ❌ | ❌ | ✅ |
Privacy policy text | ✅ | ✅ | ✅ |
Checkbox displayed | ❌ | ✅ | ✅ |
Access to the Consent Center | ❌ | ❌ | ✅ |
Consent behavior | Validating the contact accepts all communications | Checkbox determines consent | Multiple consent purposes can be managed |
For Essential Compliance:
without Checkbox: no consent screen appears, and validating contact creation automatically records consent.
with Checkbox: a consent screen appears before saving the contact. A checkbox must be confirmed to record consent.
For Advanced Compliance, a consent screen appears before saving the contact. Multiple consent purposes can be displayed.
Managing Consents on Contacts
Consent information is visible directly in each contact card.
In particular, you can view and manage:
The date and time of consent.
The purposes of consent (Advanced Compliance).
Consent by channel: email, SMS, calls, etc. (Advanced Compliance).
Imported consents.
The “Never contact again” status. This status blocks all communications, revokes all existing consents, and makes the contact’s historical information invisible to all users. It also marks the contact as “blacklisted.”
This granular control helps you respect individual preferences and remain compliant at all times.
The consent interface is the same for all modes, but the available information and the relevance of certain settings depend on the selected mode.
💡Reminder: To send a communication in Advanced Compliance mode, the user must first select one or more purposes. The contact may opt out of this specific purpose or from all communications from the organization.
Download your Consent Registry (Advanced Compliance only)
In Advanced Compliance, you can access a complete record of all consents collected for audit and compliance purposes.
This registry provides a clear overview of who gave consent, when, how, and for what purposes and channels.
Unsubscribe Management
Qomon provides unsubscribe mechanisms for different communication channels.
For Email:
Essential Compliance: one link to unsubscribe from all communications
Advanced Compliance: two links are available
Unsubscribe from all communications
Unsubscribe from a specific consent purpose or channel
For SMS / MMS: Senders can enable STOP SMS when sending messages. When used, the contact is unsubscribed from the relevant communication.
For Push Notifications: Push notification preferences are managed directly from the user’s mobile device settings or from the Qomon mobile app or white-label app.
Importing existing Consent Data
Already have consent data? You can import consents directly into Qomon.
This allows you to keep existing consent history while centralizing consent management within the platform.
👉 To learn how to import consents, read our dedicated article on consent imports.
If you have any questions or need anything, feel free to reach out to [email protected].




