Skip to content
English
  • There are no suggestions because the search field is empty.

DSR Email Forwarding to MineOS

Route privacy requests from your company's inbox directly into your MineOS portal for centralized DSR management.

What is email forwarding and why use it?

Many data subjects submit privacy requests by emailing a company's dedicated privacy address (such as dpo@yourcompany.com) rather than submitting through a Privacy Center form. Without email forwarding, these requests live outside MineOS and must be tracked manually.

By forwarding relevant emails to your dedicated MineOS address, those requests automatically appear in your Open Requests queue alongside all other DSRs — giving your team a single place to manage, respond to, and audit every request, regardless of how it was submitted.

How it works

When you forward an email to your unique MineOS address:

  1. A new ticket is created in your Open Requests queue with the source labeled "Email forwarding."
  2. The ticket opens at the Edit stage, where you manually enter the requester's details — name, email, request type, country, and state/province.
  3. Once complete, click Continue to process the request through your standard DSR workflow.

Note: You decide which emails to forward. Since privacy inboxes often receive general questions and complaints alongside DSRs, MineOS does not auto-import everything — only emails you explicitly forward will create tickets.

How to set up email forwarding

  1. In your MineOS portal, go to DSR → DSR Setup → Channels → Email Forwarding.
  2. Copy your unique forwarding address (it looks like tickets_eu-xxxxx@saymine.io).
  3. Manually forward relevant DSR emails to that address directly from your email client.
  4. Refresh your Open Requests page — the forwarded request will appear at the top of the queue as the most recent open request.

Image 23-03-2026 at 22.06 (1)Image 23-03-2026 at 22.06

Best practice: Enable the Email to DSR Parsing integration

By default, forwarded emails arrive as tickets pre-filled with the requester's name and email address. However, additional details from the email body — such as the request type (Right) and country — still need to be entered manually. The Email to DSR Parsing marketplace integration eliminates this step by automatically extracting that information from the email body and pre-populating it in the ticket, creating a fully structured DSR with no manual input. Learn more

To enable it:

  1. Go to Settings → Automations → Marketplace and search for "Email to DSR Parsing".
  2. Click Configure and set:
    • Cron schedule — how often MineOS scans for new forwarded tickets (default: every hour).
    • Notification channel — a Slack channel or email address for alerts on tickets that couldn't be parsed automatically.
    • Rights ID map — if you have custom DSR rights configured, map their names to internal IDs here.
  3. Click Finish. A green checkmark confirms the integration is active.

For the integration to parse emails correctly, forwarded messages should include the data subject's full name, email address, request type (e.g., delete, access, unsubscribe), and country.

Image 23-03-2026 at 22.09

Note: Email forwarding and email parsing require the Integration Builder feature to be enabled on your account. If you don't see Automations in your settings, contact your Customer Success Manager.

Related articles

Need help?

Contact your Customer Success Manager for further information and assistance.