> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/administration-guide/privacy.md).

# Record privacy and consent

Record why you process personal data and under what authority, show people versioned notices, keep an auditable consent ledger with point-in-time answers, and make access depend on consent.

**Applies to:** OpenIAM 2026.11.1

## What this is, and when you need it

The **Privacy module** is where you record *why* your organization processes personal data, *under what authority*, *what each person was told* and *what each person agreed to* — with an evidence trail built to be shown to a regulator. People see it as the **Privacy Center** in SelfService, where they give and withdraw consent; administrators work in five Webconsole screens; and policy-based access control (PBAC) can make an application or URL reachable only while a person's consent is granted.

Recording it this way turns each answer into evidence rather than assertion. A consent is bound to the exact notice version the person read, the ledger behind it is append-only and hash-chained, and any state can be reconstructed as of a past date — so *what was this person told, and what did they agree to, on the day of the incident?* has an answer you can show rather than argue. What it asks in return is that the pieces be built in order: a lawful authority and a processing activity before a purpose, a purpose before a notice, and a notice before anybody can consent to anything. **Start here** below sets out that sequence.

The module arrived in **2026.8.1** with its own `privacy-manager` service and `privacy` database; the Privacy Center followed in 2026.8.2, consent-aware PBAC decisions in 2026.9.1, and audiences, catalog locales and consent at the Access Gateway in 2026.11.1.

## How it differs from IT-policy consent

OpenIAM has two consent features and they are not the same thing. Choosing the wrong one is the most expensive mistake available here, because the data lives in different databases and neither reads the other.

|                           | [Consent and policy acceptance](https://docs.openiam.com/administration-guide/consent.md) | This section                                                                               |
| ------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| **The question**          | Did this person accept our acceptable-use policy?                                         | What do we process, why, on what basis, and what did they agree to?                        |
| **Shape**                 | One text, one acceptance, one re-acknowledgement period                                   | A register of purposes, each separately consentable, each backed by a lawful authority     |
| **Lawful basis**          | Not modeled                                                                               | A first-class register with its own lifecycle                                              |
| **Where the person acts** | A prompt at sign-in, and **Consent History** in SelfService                               | The **Privacy Center** in SelfService, and a consent page the Access Gateway sends them to |
| **Gating access**         | Before sign-in completes, per content provider                                            | Per request, through a PBAC policy that requires consent for a purpose                     |
| **History**               | Per-user acceptance history                                                               | An append-only, hash-chained ledger with point-in-time answers and receipts                |
| **Storage**               | The `openiam` schema                                                                      | Its own `privacy` database                                                                 |

"Everyone must accept the acceptable-use policy before they reach the portal" is the consent section. A record of processing purposes and lawful bases, with consent given and withdrawn per purpose, is this one.

## Choose your outcome

| I want to…                                                                                                       | Go to                                                                                                                                  |
| ---------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Register the lawful bases, processing activities and purposes I rely on, and decide who is offered each purpose  | [Register purposes and lawful authorities](https://docs.openiam.com/administration-guide/privacy/register-purposes-and-authorities.md) |
| Publish the notice people read before they consent, translate it, or change it in a way that requires re-consent | [Publish a privacy notice](https://docs.openiam.com/administration-guide/privacy/publish-a-privacy-notice.md)                          |
| See what one person has consented to, what was true on a past date, or hand them a receipt                       | [Look up a person's consent](https://docs.openiam.com/administration-guide/privacy/look-up-consent.md)                                 |
| Know what people see in the Privacy Center, and how preferences differ from consent                              | [What people see in the Privacy Center](https://docs.openiam.com/administration-guide/privacy/the-privacy-center.md)                   |
| Make an application reachable only while a person's consent is granted                                           | [Privacy decisions](https://docs.openiam.com/administration-guide/pbac/privacy-decisions.md)                                           |
| Send a person to a consent page, instead of refusing them, when consent is missing                               | [Ask for consent at the gateway](https://docs.openiam.com/administration-guide/privacy/enforce-consent-at-the-gateway.md)              |
| Clear failed deliveries, read the dashboard, verify the evidence chain                                           | [Operate the privacy service](https://docs.openiam.com/administration-guide/privacy/operate-the-privacy-service.md)                    |
| Look up a status, audit action, property or rejection message                                                    | [Privacy reference](https://docs.openiam.com/administration-guide/privacy/privacy-reference.md)                                        |

## Start here

A first deployment goes in this order, because each step is a precondition of the next:

1. [Register purposes and lawful authorities](https://docs.openiam.com/administration-guide/privacy/register-purposes-and-authorities.md) — authorities, then processing activities, then purposes. A purpose cannot be activated without an active authority and an active activity.
2. [Publish a privacy notice](https://docs.openiam.com/administration-guide/privacy/publish-a-privacy-notice.md) — a notice version cannot be activated until every purpose it covers is active, and a person cannot consent to a purpose no active notice covers in their language.
3. Check the result as a test user in SelfService → **Privacy Center**.
4. Only then, if consent should decide access, write the policy — [Privacy decisions](https://docs.openiam.com/administration-guide/pbac/privacy-decisions.md).

## The screens

The Webconsole puts four of the screens under **Governance → Privacy** and the fifth under **Monitoring → Health & Analytics → Privacy Health**. Each screen shows the same tab strip — **Dashboard**, **Consent Lookup**, **Operations**, **Health**, **Registry** — and a **Tenant** field, which is `default` unless your deployment uses another privacy tenant.

| Screen             | Route                               | What it is for                                                                                       |
| ------------------ | ----------------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Dashboard**      | `/webconsole-v2/privacy-dashboard`  | Consent, evidence and delivery activity for a period                                                 |
| **Registry**       | `/webconsole-v2/privacy-registry`   | Authoring purposes, processing activities, lawful authorities and notices; listing webhook endpoints |
| **Consent Lookup** | `/webconsole-v2/privacy-consent`    | One person's current consent, ledger timeline, state on a date, and receipts                         |
| **Operations**     | `/webconsole-v2/privacy-operations` | Deliveries that drifted and outbox events that failed, with replay                                   |
| **Health**         | `/webconsole-v2/privacy-health`     | Backlog, delivery failures and evidence-chain verification                                           |

**Consent Configuration** under the same menu is the IT-policy consent feature.

## What the model holds

| Object                  | What it is                                                                                            |
| ----------------------- | ----------------------------------------------------------------------------------------------------- |
| **Lawful authority**    | The basis you rely on, flagged consent-based or not, with a validity window                           |
| **Processing activity** | What is done with the data: systems, recipients, retention                                            |
| **Purpose**             | Why the data is processed — its owner, data categories, lawful authority, activities and **audience** |
| **Notice**              | What a person reads before deciding, in versions and locales, covering one or more purposes           |
| **Consent ledger**      | Hash-chained consent events per person and purpose, the state derived from them, and receipts         |
| **Preference**          | A choice that is not consent — a channel, a topic — kept apart from the ledger                        |
| **Evidence chain**      | Every consent event, decision, transition, delivery and operator action, hash-chained                 |
| **Outbox and webhooks** | How consent changes reach other systems                                                               |

Purposes, activities, authorities and notice versions are all **governed**: they move through `DRAFT` → `REVIEW` → `APPROVED` → `ACTIVE`, an edit to an approved or active one creates a new version, and only an `ACTIVE` one counts. Only an `ACTIVE` purpose can collect consent or appear in the Privacy Center.

## What this release does not include

This release does not include a data subject request case: nothing here accepts, tracks or routes an access, erasure or portability request, and the Privacy Center's **Your rights** tab shows contact text, not a form. To run such requests as a tracked process, model them as a request type under [Configure requests and approvals](https://docs.openiam.com/administration-guide/requests.md).

It also does not include a guardian consent flow, a cookie banner, or connector operations that act on consent in a managed system; systems that must honor consent changes receive them through webhooks.

## Related

* [Consent and policy acceptance](https://docs.openiam.com/administration-guide/consent.md) — the other consent feature, and how to tell which one you need
* [Decide access with policies](https://docs.openiam.com/administration-guide/pbac.md) — the policy engine that enforces consent
* [Audit actions and retention](https://docs.openiam.com/administration-guide/reference/audit-actions-and-retention.md) — how long audit records naming a person survive, a separate decision from anything here
* [Find audit evidence](https://docs.openiam.com/administration-guide/operations/find-audit-evidence.md) — the platform-wide audit trail


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openiam.com/administration-guide/privacy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
