Universal Consent & Preference Management Terminology Guide

Attribute

A data point or piece of information that provides details, context, or functionality for OneTrust objects, like collection points and purposes.

activationDate, businessDivision, createdBy

Collection Point

Interface where data subjects can give their consent, set their preferences, or provide data.

Custom API, Embedded Web Form, Hosted Web Form

Consent Dashboard

A customizable widget-based interface consisting of a comprehensive overview of all consent receipts, transactions, and consent metrics.

Consent on behalf of

Manual action of adding, modifying, and withdrawing consent on behalf of another data subject, managing their consent preferences.

Consent String

A standardized, machine-readable carrier of consent information that encodes user consent choices that can be sent to third-party systems and vendors.

TC String, GPP String

Data Element

A data point or piece of additional information about a data subject that is voluntarily provided by the end user themselves.

Date of Birth, State, Title

Data Subject

An identified or identifiable natural person who provides data and grants, withholds, or updates consent via an interface.

caroline.stradler@email.com

Data Subject Profile

An overall record of the data subject, any identifiers, the purposes they have consented to, transaction history, related data elements, and other details.

Data Subject Token

An alphanumeric code that, in combination with a magic link, generates a URL to directly access a preference center.

uQ5eBBoXZ6zhztKLrMrdOWTwUgq2SzJQB5q98hcq0E4=

Embedded Web Form

A type of collection point that can be customized and directly embedded on a website to collect consent information and automatically send it to OneTrust.

Geolocation

A way to track the data subject’s location using their IP address. Once consent is provided, it is stored in the data subject’s profile and associated consent receipts.

Hosted Web Form

OneTrust-generated web form that can be accessed via link and integrated on a website without coding. It collects consent and stores it directly in OneTrust.

Identifier

A unique piece of information used to distinguish and track individual users and their consent choices.

Cookie Unique ID, Email, Mobile

Interface

The point of interaction where OneTrust users display and collect information from data subjects.

Collection Point, Preference Center

Magic Link

A link that provides authenticated access to data subjects to a preference center when combined with a data subject token.

https://privacyportaltrial.onetrust.com/ui/#/preferences/multipage/token/16afef91-1205-4074-ad32-1e3ddc123b43/uQ5eBBoXZ6zhztKLrMrdOWTwUgq2SzJQB5q98hcq0E4=

Native Integration

A simplified method to set up and authenticate the integration process by using predefined data.

Eloqua, Hubspot, Salesforce Marketing Cloud

Preference Center

Interface where data subjects can manage their consent preferences for specific purposes and purpose preferences.

Purpose

A specific reason why a business processes someone’s data for which consent is needed.

Brand Communications, Marketing Emails, Product News

Purpose Preference

Additional choices related to purposes that modify how data will be processed.

Contact frequency: Daily, Weekly, Monthly

Communication channel: Email, Phone, SMS

Purpose Status

The current outcome of a data subject’s choice regarding a purpose.

Active, Opted Out, Withdrawn

Reason Template

A pre-defined text option for why a data subject wants to change their preferences.

I am receiving too many emails, I did not sign up for this, This information is no longer relevant

Receipt

The timestamped immutable grouping of transactions, data, and metadata belonging to a data subject’s single interaction with an interface.

Transaction

The individual choice made by a data subject for a single purpose within a given receipt.

Transaction Type

Type of action or inaction performed by the data subject for a purpose.

Confirmed, Expired, Hard Opt Out

Visibility Rules

Logical conditions that determine which form fields, purposes, or iterations of interfaces appear or are required based on interactions, profile information, geolocation, or other data.