Skip to content
Optima docs
ConsoleAgentsBuilt-in agents

Privacy digest

A built-in agent that emails a weekly summary of consent grants and withdrawals and the state of erasure requests.

The privacy digest is a built-in agent that tells your data protection officer how consent changed last week and how erasure requests stand, without anyone opening the privacy screens. Once a week it reads two aggregate results and sends one plain-text email.

Who uses it

Tenant administrators create the instance. The owner of the instance needs privacy access (for example the privacy_viewer or privacy_officer role, or an administrator role), because the agent can read only what its owner may read. The owner's access governs the reads, not the recipients': everyone who receives the email sees its aggregate counts, even without a privacy role. The people who receive the email can be anyone on your team or any email address you enter. You need the Built-in agents feature in your licence.

Fields

ParameterWhat you enterDefault
recipientsThe people who get the email. Required.Owner (you)
scheduleWhen the digest is written, as a cron expression in the instance time zone.0 8 * * 2 (Tuesday, 08:00)
always_sendSend an email even when there is nothing to report.Off

Actions

  • Reads: how many consents were granted and withdrawn per purpose in each of the last five complete weeks (weeks run Monday to Monday in UTC), and the number of erasure requests opened, completed, still open and overdue. It reads counts and request ids, never personal data.
  • Sends: one plain-text email to the recipients you choose. The subject names the week, for example "Privacy digest: week ending 2026-10-26".

The email contains, in this order:

  • First line: the most important finding, or "No privacy issues this week."
  • Consent: for each purpose with a change, this week's grants and withdrawals next to the four weeks before, each as Optima returned it. A purpose whose withdrawals jumped well above the earlier weeks is named first.
  • Erasure: requests opened and completed since the start of the week, requests still open (pending, in progress, failed) and overdue ones, which are open for more than 30 days. Overdue requests are listed by id and status only. When the erasure list was too long to read in full, the section says "The erasure counts may be incomplete."
  • What I could not check: failed or unavailable reads, results that were cut off, and that access requests are not tracked by Optima.

When nothing needs attention, no email is sent unless Always send is on. A read that fails, or that is unavailable because the owner has no privacy access, is never treated as "nothing to report": the email goes out and names it as unavailable.

Every figure in the email is copied from Optima's own results, never estimated, and is checked against what the agent read. If the agent cannot back a figure up, the run fails and nothing is sent.

Limits

Access requests are not covered, because Optima does not track them. Consent counts come from the consent history: a grant that arrived through a profile merge and was withdrawn later may be missing. An erasure removes the erased person's consent history too, so the counts of a past week can be lower in a later digest than they were in the first one. The overdue list shows at most 20 requests. The totals of pending, in progress and failed requests are always exact. The counts of requests opened and completed in the period, and the overdue count, are computed from the newest 500 requests of each open status (for overdue, also the oldest ones) and the newest 500 completed requests; the email says when they may be incomplete and still goes out. The digest reports the calendar week (Monday to Monday, UTC) before the UTC week in which the run starts. It runs on Tuesday 08:00 by default because that moment is inside the right UTC week in every time zone; a Monday 08:00 run in a time zone east of UTC+8 would still be Sunday in UTC and report the week before last. If you set your own schedule, make sure its time, converted to UTC, is on or after Monday 00:00 UTC of the week after the one you want reported, and not later than that week's Sunday. With more than 500 open or completed erasure requests the erasure counts may be incomplete; the Erasure section and "What I could not check" both say so.

Examples

To try it, create the instance in dry run with a cheap model and set schedule to a time a few minutes ahead. Open the run log to see the email it would send. When you are happy with it, set the schedule back to the default (Tuesday 08:00) and switch the instance to live.

Common problems

  • No email this week. No withdrawal spike and no overdue erasure request, and Always send is off. Or the instance is stopped.
  • The email says a read was unavailable. The owner of the instance has no privacy access, so the agent was never given the read and the email names it as unavailable. Create the instance as a user with a privacy role.
  • The run failed with "numbers that no tool returned". Try a stronger model or look at the run in the run log.
  • The card is missing. Your licence has no Built-in agents feature.

On this page