Automate DSR Email Forwarding
Automatically classify and create fully structured DSR tickets from privacy requests received through your company’s privacy inbox.
Before You Start
- Make sure you have already set up Email Forwarding for your privacy inbox.
- Request access to the MineOS 'Automations' feature, if you don't already have it.
Setting Up
- Login to your MineOS account and goto Settings -> Automations.
- Select Marketplace and search for "Email to DSR Parsing". Click it and select Configure.

-
The cron expression determines how often the system scans for new Edit-stage tickets created via Email Forwarding. Runs ever hour on the hour by default, you may change this to run more or less frequently depending on request volume.
-
Set a Slack channel or email address to receive notifications about tickets that were not re-opened with the correct subject and right. (Guide for creating Slack Webhooks)

- Right to IDs map maps right names to their internal IDs. If you have custom rights configured add them here so we can classify them.

- You can retrieve the ID from the url in the right's setting page:

- You can retrieve the ID from the url in the right's setting page:
- Click Finish. You should see a Green checkmark noting the integration has been configured properly.
- In case an errors is thrown, you will get to your Slack - or Email whatever you chose to configure - a message: Forwarded DSR Request Not Processed (Ticket {ticketId})
FAQs:
-
Emails Requesting Multiple Rights
If a single email asks for two DSR rights (for example, 'please delete my data and send me a copy'), MineOS will open one DSR based on the primary right detected. A second DSR for the additional right will not be created automatically. Advise customers to submit separate requests per right for the most reliable processing.
-
Feature Flag Requirement
Email forwarding and email parsing are available to accounts with the Integration builder enabled. If its not available, ask you Customer Success Manager to enable it.
How to Structure Your Privacy Request Emails
To ensure MineOS can correctly classify forwarded emails, the message should include:
-
The data subject’s full name
-
The email address the request refers to
-
A clear request type (e.g., delete, copy, unsubscribe, etc.)
-
The requester’s country (required). Defaults to US if not inferred.
-
The requester’s state or province (optional)
This information can appear anywhere in the email body or subject—MineOS will extract it automatically.