DSR Email Communications
The automated emails MineOS sends across the request lifecycle, and how to edit templates and use variables
MineOS sends automated emails to data subjects at key points in the request lifecycle. This section explains each email type, when it's sent, and how to configure it. The templates themselves are managed in DSR Setup → Templates, and you choose which template applies to each right in that right's Rules & templates settings.
The email types
- Verification — confirms the data subject's identity after they submit a request.
- Acknowledgement — confirms receipt once the request is verified.
- Completion — tells the data subject their request is done.
- Rejection — explains that a request has been rejected.
- Auto-reply for closed requests — responds when a data subject replies after their request is already closed.
Editing templates and using variables
Each template's content is editable, and templates support variables — placeholders that are filled automatically with request-specific details when the email is sent. One useful variable is brandName, which resolves to the brand assigned to the request, so every email shows the correct brand name even when a single template is shared across brands. For how to find, edit, and translate templates on the Templates page, see Managing Templates.
Per-right and per-brand
Which template applies is set per privacy right, so different rights can use different wording. The only exception is the Auto-reply for closed requests template, which is configured for all rights across the platform, as it a generic message which doesn't need special customization.
If you run multiple brands, the completion email (the "Send reply to user" template) can be set per brand from the right's workflow; the other templates use a single version across all brands, with brandName ensuring each email still reflects the correct brand.
Updated about 17 hours ago