---
title: Process a privacy request
description: The Privacy Request module allows you to monitor and manage privacy requests submitted by your end-users. In the Didomi Console, you can update requests’ statuses in order to match the actual state of
---

[Skip to content](https://support.didomi.io/process-a-privacy-request#main-content)

- [English](https://support.didomi.io/process-a-privacy-request)
- [Français](https://support.didomi.io/fr/traiter-une-requête)

English

Show submenu for translations

[Customer portal](https://support.didomi.io/tickets-view)

![Didomi SAS](https://support.didomi.io/hs-fs/hubfs/Didomi-tail-name.png?width=182&height=34&name=Didomi-tail-name.png)

Open main navigation

Close main navigation

- - [English](https://support.didomi.io/process-a-privacy-request)
    - [Français](https://support.didomi.io/fr/traiter-une-requête)

  English
  
  Show submenu for translations
- [Customer portal](https://support.didomi.io/tickets-view)
- Go to didomi.io

 Go to didomi.io

 Our documentation has moved to docs.didomi.io. Please update any bookmarks.

- There are no suggestions because the search field is empty.

1. [Help Center](https://support.didomi.io/)
2. [Privacy Request](https://support.didomi.io/privacy-request)
3. [User Requests](https://support.didomi.io/privacy-request#user-requests)

# Process a privacy request

The Privacy Request module allows you to monitor and manage privacy requests submitted by your end-users. In the Didomi Console, you can update requests’ statuses in order to match the actual state of the request within your processing workflow.

### Status

Following are the six statuses and their definitions.

### **Unverified**

A request submitted by an end-user that hasn’t been validated yet.

When a request is submitted through a Privacy Requests widget, the status is by default set to unverified. In parallel, the end-user will get an email asking them to confirm their identity.

### **Verified**

A request either verified by the end-user through verification email or set to **verified** by the organization.

### **Work in progress**

A request currently being processed.

Please be aware that when you assign the status to **work in progress**, an email is sent to the end-user (requestor) informing them that your organization is processing their request.

### **Fulfilled**

A request that you have addressed and closed.

Please be aware that when you assign the status to **fulfilled**, an email is sent to the end-user (requestor) informing them that your organization has completed their request. In case of an access request, you can attach a link to this email to let your end-user download their data.

### **Refused**

A request you refuse to address.

Please be aware that when you assign the status to **refused**, an email is sent to the end-user (requestor) informing them that your organization won’t process their request.

### **Archived**

A request you don’t need to process anymore because you have either addressed or refused it.

Please note, no email is sent to the end-user (requestor) when the status is set to **archived**.

### Update privacy request status

You can update request status from two locations in the Didomi Console.

1. Go to the **Privacy Requests** tab, in the left menu.
2. Click on the **User Requests** tab.

### Update status from the request list

From this page, you can update a request status in its card, by using the select input at the top right corner.

![Group 27267 (1)](https://support.didomi.io/hs-fs/hubfs/Group%2027267%20(1).png?width=688&height=99&name=Group%2027267%20(1).png)

### Update status from the request view

In the request view page, you have the access to all relevant information about the end-user and their request. You can also update the request status by using the select input at the top right corner of the page.

![Group 27268 (1) (1)](https://support.didomi.io/hs-fs/hubfs/Group%2027268%20(1)%20(1).png?width=688&height=384&name=Group%2027268%20(1)%20(1).png)

In both cases, before the status is actually changed, **a confirmation popup will appear when you try to update the request status**.

Please be aware that when you assign the status to either **work in progress, fulfilled, or refused**, an appropriate email is sent to the end-user (requestor) informing them about the change in status.

### Communications with end-users

The Privacy Request module allows you to communicate with your end-user while you are processing their data requests. Automatic status change email updates to the end-user (the requestor) will be sent when a privacy request is made using the Privacy Request widget. A few configuration adjustments must be done in order to support the same workflow through API; for more information, see this page.

### End-user identity confirmation

When your end-user formulates a request from a Privacy Request widget, the email address requested in the second layer is the one used to send them emails during the request process, including the verification email to confirm the email address. The end-user needs to click on the CTA button to confirm email address.

![Group 2 (4)](https://support.didomi.io/hs-fs/hubfs/Group%202%20(4).png?width=600&height=554&name=Group%202%20(4).png)

### Work in progress notification

When you assign the status to **work in progress**, an email is sent to the end-user (requestor) informing them that your organization is processing their request.

![Group 2 (1) (1)](https://support.didomi.io/hs-fs/hubfs/Group%202%20(1)%20(1).png?width=600&height=388&name=Group%202%20(1)%20(1).png)

### Request addressed

When you assign the status to **fulfilled**, an email is sent to the end-user (requestor) informing them that your organization has completed their request. For most requests, there is nothing to provide to the end-user, but in case of an access request, you can attach a link to this email to let your end-user download their data.

![Group 2 (3) (1)](https://support.didomi.io/hs-fs/hubfs/Group%202%20(3)%20(1).png?width=600&height=496&name=Group%202%20(3)%20(1).png)

### Request refused

When you can’t or don’t want to address the request due to legitimate reasons, you can set the request status to **Refused**. And when you assign the status to **refused**, an email is sent to the end-user (requestor) informing them that your organization won’t process their request.

![Group 2 (2) (1)](https://support.didomi.io/hs-fs/hubfs/Group%202%20(2)%20(1).png?width=600&height=389&name=Group%202%20(2)%20(1).png)

If you would like any further information about how to configure these emails, do not hesitate to read our [developers documentation](https://developers.didomi.io/api/privacy-requests/emails).

- [Consent notice creation](https://support.didomi.io/consent-notice-creation#main-content)

    - [Basics](https://support.didomi.io/consent-notice-creation#basics)
    - [Consent notice per device](https://support.didomi.io/consent-notice-creation#consent-notice-per-device)
    - [Manage Vendors and Purposes](https://support.didomi.io/consent-notice-creation#manage-vendors-and-purposes)
    - [Customization](https://support.didomi.io/consent-notice-creation#customization)
    - [Multi-regulations](https://support.didomi.io/consent-notice-creation#multi-regulations)
    - [Frameworks](https://support.didomi.io/consent-notice-creation#frameworks)
    - [Integrations](https://support.didomi.io/consent-notice-creation#integrations)
    - [Console migration](https://support.didomi.io/consent-notice-creation#console-migration)
    - [IAB GPP Framework](https://support.didomi.io/consent-notice-creation#iab-gpp-framework)
    - [Accessibility](https://support.didomi.io/consent-notice-creation#accessibility)
- [Compliance report](https://support.didomi.io/compliance-report#main-content)

    - [CMP Vendor Sync](https://support.didomi.io/compliance-report#cmp-vendor-sync)
    - [Advanced Compliance Monitoring](https://support.didomi.io/compliance-report#advanced-compliance-monitoring)
- [Preference Management Platform](https://support.didomi.io/preference-management-platform#main-content)

    - [Configuration Tree](https://support.didomi.io/preference-management-platform#configuration-tree)
    - [Widget](https://support.didomi.io/preference-management-platform#widget)
    - [Deployment](https://support.didomi.io/preference-management-platform#deployment)
- [Google integrations](https://support.didomi.io/google-integrations)
- [Privacy Request](https://support.didomi.io/privacy-request#main-content)

    - [User Requests](https://support.didomi.io/privacy-request#user-requests)
    - [Widgets](https://support.didomi.io/privacy-request#widgets)
- [IAB TCF](https://support.didomi.io/iab-tcf#main-content)

    - [Google & TCF](https://support.didomi.io/iab-tcf#google-tcf)
    - [TCFv2 Presentation](https://support.didomi.io/iab-tcf#tcfv2-presentation)
    - [TCF v2.2](https://support.didomi.io/iab-tcf#tcf-v2-2)
- [Analytics](https://support.didomi.io/analytics#main-content)

    - [Consent Management Platform (CMP) Analytics](https://support.didomi.io/analytics#consent-management-platform-cmp-analytics)
    - [Preference Management Platform (PMP) Analytics](https://support.didomi.io/analytics#preference-management-platform-pmp-analytics)
    - [ACM (Advance Compliance Monitoring)](https://support.didomi.io/analytics#acm-advance-compliance-monitoring)
- [Integrations](https://support.didomi.io/integrations#main-content)

    - [AB testing](https://support.didomi.io/integrations#ab-testing)
    - [Paywalls](https://support.didomi.io/integrations#paywalls)
    - [CMS](https://support.didomi.io/integrations#cms)
    - [Generic integrations](https://support.didomi.io/integrations#generic-integrations)
    - [Marketing automation](https://support.didomi.io/integrations#marketing-automation)
    - [Customer Data Platform (CDP)](https://support.didomi.io/integrations#customer-data-platform-cdp)
    - [CRM](https://support.didomi.io/integrations#crm)
- [Lexicon](https://support.didomi.io/lexicon)
- [Legal Requirements](https://support.didomi.io/legal-requirements#main-content)

    - [Didomi SDK compliance](https://support.didomi.io/legal-requirements#didomi-sdk-compliance)
- [Privacy Center and Data Processing](https://support.didomi.io/privacy-center-and-data-processing)
- [FAQ](https://support.didomi.io/faq#main-content)

    - [CMP / Managing tags](https://support.didomi.io/faq#cmp-managing-tags)
    - [CMP / Data Privacy for publishers](https://support.didomi.io/faq#cmp-data-privacy-for-publishers)
    - [CMP / Implementing a consent notice](https://support.didomi.io/faq#cmp-implementing-a-consent-notice)
    - [Debugging](https://support.didomi.io/faq#debugging)
    - [CMP / CPRA](https://support.didomi.io/faq#cmp-cpra)
    - [CMP / Analytics](https://support.didomi.io/faq#cmp-analytics)
    - [PMP](https://support.didomi.io/faq#pmp)
    - [Share consent](https://support.didomi.io/faq#share-consent)
    - [Customization](https://support.didomi.io/faq#customization)
    - [Cookies](https://support.didomi.io/faq#cookies)
    - [IAB](https://support.didomi.io/faq#iab)
- [Versions & Proofs](https://support.didomi.io/versions-proofs)
- [Login & Security](https://support.didomi.io/login-security#main-content)

    - [SSO](https://support.didomi.io/login-security#sso)
    - [Users, Teams and Permissions](https://support.didomi.io/login-security#users-teams-and-permissions)
- [Privacy Hub widget](https://support.didomi.io/privacy-hub-widget)
- [Consent Notices (old flow)](https://support.didomi.io/consent-notices-old-flow)
- [Consent Notices (NEW FLOW)](https://support.didomi.io/consent-notices-new-flow)
- [Customer Portal - Tickets](https://support.didomi.io/customer-portal-tickets)
- [Organization settings](https://support.didomi.io/organization-settings)
- [SDK version control](https://support.didomi.io/sdk-version-control)

Didomi, verb in ancient greek (δ‌‌ιδο‌μι): consent.

Copyright © 2026, Didomi SAS

Cookies