Consent and purposes
How Optima ties every use of personal data to a declared purpose, the customer's consent and the reader's access level.
Optima treats privacy as part of how data is stored and read. Every time personal data is read or written, three questions are answered. This page explains them, and the controls you have: purposes, consent, retention, erasure and the audit log.
The three questions
- Is the person acting allowed to act for this purpose? Each user and each API key is granted a set of purposes. This is a property of the reader.
- Does this purpose permit this field? Each attribute can be tagged with the purposes that allow processing it. This is a property of the data. An untagged field is available for any purpose.
- Did the customer agree? The customer's consent record for the purpose is checked at the time of reading. It is never cached from an earlier decision. This is a property of the individual.
In addition, a PII access level limits how sensitive the fields you see can be. Fields are tagged with a level in the schema, and you see a field only if your own level reaches it.
Writing personal data is processing too, so writes are purpose-bound in the same way as reads.
Purposes
A purpose is a declared reason for processing data, for example marketing, analytics or personalization. Purposes are the shared vocabulary that ties the rest together: consent records grant or withhold them per customer, schema tags say which fields each one allows, users and keys are granted them, and every request declares one.
You manage purposes under Settings → Workspace → Privacy, on the Consent purposes tab. A purpose has:
| Field | Meaning |
|---|---|
| Name | Unique. Must not contain a dot (.); a name with one is refused. Purposes created earlier with a dot keep working. |
| Description | Shown to visitors in the consent banner and the preference centre. You can add a translation per language; visitors whose language has no translation read the default text. |
| Lawful basis | The legal ground the purpose relies on: consent, legitimate interest, contract, legal obligation, vital interests or public task. It decides how a missing consent record is read. |
| On withdrawal | retain data or erase data. With erase, an explicit withdrawal by a customer who had granted the purpose starts a purpose-scoped erasure automatically. |
| Channel | Scopes the purpose to one channel, so campaigns can refer to the purpose for whichever channel they use. |
| Topic | Groups purposes on the preference page. It has no effect on enforcement. |
| Visible in preference centre | Shows the purpose as a toggle the customer can control. Keep operational purposes hidden. |
To create one purpose per channel in one go, for example marketing for email, SMS and push, use New purpose family. Campaigns and offers then refer to the family with a single placeholder and the channel actually used decides which purpose is checked. A purpose that erases data on withdrawal cannot also be channel-scoped or visible in the preference centre, because the withdrawal itself is a record that must be kept.
How a missing consent record is read
The lawful basis decides what "no record" means:
| Lawful basis | No record | Withdrawn |
|---|---|---|
| Consent (opt-in) | Blocked. The customer has not been asked. | Blocked |
| Legitimate interest (opt-out) | Allowed. The customer has not objected. | Blocked (objection) |
| Contract, legal obligation, vital interests, public task | Not consent-gated | Not consent-gated |
Widening a purpose's lawful basis, for example from consent to legitimate interest, instantly unblocks every profile that never opted in. The change applies to all stored data, so the console asks you to acknowledge it before applying.
Consent records
A consent record states whether one profile has granted or withdrawn one purpose. It carries the purpose, whether it is granted, the source (where the decision came from), when it was recorded and an optional expiry. With no expiry, consent does not lapse.
Records arrive from the SDKs and consent banner, from web forms and the preference centre, from imports and the API, or from your own team through Manage consents on a profile. They appear on the profile's Consent & Privacy tab, which also shows the customer's Consent receipts.
A consent receipt is evidence of an interaction: which policy text the customer saw, on which channel, and what they chose. A record without a receipt shows no evidence. Consent policies, on their own tab, store the exact consent wording the customer saw. A policy version is immutable once created: new wording is a new version, and only active or inactive can change afterwards. Receipts point at the version, so you can show precisely what a customer agreed to.
Acting purpose
The Acting purpose selector in the top bar declares why you are looking at customer data. It decides which personal fields you can see, and it is written to the audit log. You can choose only among the purposes you have been granted. With No purpose selected you see only unrestricted data. When fields are hidden, the page says how many and why.
A tenant administrator or privacy officer grants purposes and sets the PII level of users and API keys. See licences and roles.
Retention
Retention policies remove old data automatically. On the Retention tab you choose a Scope:
- Profile attribute: expires attribute values on profiles of an entity type.
- Event: deletes whole events of a type, with all their attributes.
- Event attribute: expires attribute values inside events of a type. The events stay.
Each policy has Retain days, optionally an Attribute key, an optional purpose and what to do On expiry: Anonymize or Delete. Policies that name a purpose act only on values that were collected under that purpose.
Erasure
A customer's right to be forgotten is carried out as an auditable erasure request, never as a plain delete. It is created from the profile's More actions menu. Filing needs privacy_officer (the server checks it) and profile write access such as data_editor (the menu item is disabled without it). Ask your administrator to give the person filing both. The Erasure tab then tracks its Status, who requested it, when it completed and the last error, if any. Erasure removes the person's data, and they drop out of identity clusters the next time resolution runs.
Larger bulk removals are scheduled on the Deletions tab as Scheduled deletions of profiles, events or dataset records. You can cancel one before it runs, but not once it is retrying after an error, because part of it may already be deleted.
Audit log
The Audit log tab records every read and write of customer data: who (Actor), what (Operation), the Result, the Consent state at the time, which Attributes were involved and when. Filter by date range and other fields. It is the evidence that processing was lawful, and it is read-only.
The Access levels tab lists the PII access level of each user and API key.
Where customers meet consent
Customers meet consent through the consent banner and forms on your website and in your apps, the SDKs, the preference centre and one-click unsubscribe links in email. Withdrawals made there flow into the same consent records described above and are respected on the next send.