Privacy Settings Reference
Field reference for the Privacy tab on a user's profile: consent status, consent categories, and legitimate interest records.
Overview
Every user profile has a Privacy tab. It shows that user's consent record: what they've consented to, what they've revoked, and any legitimate interest categories that apply to them. This reference lists every field on that record. For the walkthrough of setting up and managing consent categories, see Managing consents.
Consent status
The top of the Privacy tab summarizes the user's current consent state as two lists.
| Field | Description |
|---|---|
| Consented | Categories the user currently has granted, shown as badges. |
| Revoked | Categories the user currently has revoked or has not consented to, shown as badges. |
Consent category fields
Each consent category on the Privacy tab has the following fields.
| Field | Type | Description |
|---|---|---|
| id | string | Unique identifier for the consent record. |
| title | string | Display name of the consent category, shown on the Privacy tab. |
| description | string | Optional description of the category, shown under its title. |
| channel | string | The source the consent was recorded from. |
| basis | string | The category's underlying consent basis. |
| consentCategory | string | The category identifier used when granting or revoking consent. Must match the category's defined identifier. |
| type | string | simple (or empty) for Consent categories, legitimate for Legitimate interest. Determines which section the category appears in. |
| checked | boolean | Whether the user currently has this category granted (true) or revoked (false). |
Consent categories vs. legitimate interest
The Privacy tab splits categories into two sections based on their type value.
| Section | type value | Description |
|---|---|---|
| Consent categories | simple or empty | Categories the user has actively consented to or declined. |
| Legitimate interest | legitimate | Categories processed under legitimate interest rather than active consent. The Legitimate interest section displays a fixed notice: "Lawful basis: subscription communication. End users may request objection (Art. 21)." |
Granting or revoking consent
Toggling a category on the Privacy tab sends a request with these fields.
| Field | Type | Required | Description |
|---|---|---|---|
| action | accept or reject | Yes | accept grants the category, reject revokes it. |
| consentCategory | string | Yes | Identifier of the category being updated. |
| masterId | string | Yes | The profile's Master ID. See Customer Profile Schema Reference. |
| timestamp | number (Unix seconds) | Yes | Time the action was taken. |
| source | string | No, defaults to api | Where the change originated. |
| validUntil | string | No, defaults to unlimited | Expiration for the consent, if any. |
📘 Good to know
Granting a category saves immediately. Revoking a category shows a confirmation dialog first, then saves once confirmed.
Use cases
- Check whether a user has an active consent for a channel before sending a targeted message.
- Review a user's Revoked list to confirm they've opted out of a specific category.
- Manually grant a consent category on a user's behalf, for example after receiving consent through an offline channel.
- Manually revoke a consent category for a user who asked to opt out.
- Confirm whether a category is processed under legitimate interest rather than active consent, and whether it can be objected to under Art. 21.
- Look up a category's
consentCategoryidentifier to match it against the category defined in Managing consents. - Use
masterIdto cross-reference a consent action with the same profile shown on the User details page.
Where to go next
Preference center
The preference center page allows your customers to see all the consent categories, including legitimate interests you had predefined in the project settings, and to unsubscribe from any of them if...
Access management
How organization and project roles control who can invite members, edit settings, and access data in Intempt, and how to build a custom role for either scope.