DSR mailbox

Read a mailbox where data subjects send their requests, so that each email starts the GDPR request workflow.

A data subject request (DSR: a person asking to see, correct, delete or move the personal data you hold about them) often arrives as an ordinary email. The DSR mailbox connector points Aegis at one dedicated mailbox, such as privacy@yourcompany.com, over IMAP (the standard protocol mail programs use to read a mailbox). Aegis reads new emails, sorts out which ones are requests, and opens a pending request for each one it recognises, so the legal deadline starts from the day the email arrived.

At a glance

Direction Into Aegis.
What it brings in New (unread) emails in one IMAP mailbox folder (INBOX by default), up to 50 per run.
Where it lands Each email is stored and classified by AI. An email recognised with high confidence as a data subject request becomes a pending request, with its acknowledgement and response deadlines started, and an AI draft response; a person reviews it before anything is sent (see GDPR).
Credentials and permissions The IMAP server, port (993 by default), username and password of the mailbox, with TLS on by default.
Owner of imported records A request created from an email is unassigned until someone assigns it.
When it runs Every 15 minutes, on plans with GDPR automation, and only while the connector reads Connected (its last connection test succeeded). With AI switched off, emails are still collected but not classified.
Set it up /connectors/dsr-mailbox, under the GDPR module rather than a connector module, by a Manager or Admin, on a plan that includes the connector.

Who uses it

Saving and testing also need the GDPR module switched on for your organisation. On the Connectors overview, the DSR Mailbox tile is greyed out with a Premium label when your plan does not include GDPR automation; without it the mailbox is never read, even if settings are saved.

What's on this screen

No screenshot of this page was captured for this edition of the guide; the description below follows the page as it is built. From top to bottom, /connectors/dsr-mailbox shows:

Prepare the mailbox

  1. Create a dedicated address for requests, separate from general inboxes, and publish it as the privacy contact in your privacy notice.
  2. Switch on IMAP access for that account. In Microsoft 365 this is a mailbox setting; in Google Workspace it is a Gmail setting.
  3. If the account uses two-factor sign-in, create an app-specific password for Aegis. Many providers reject the ordinary account password over IMAP.

Connect the mailbox

  1. Go to Connectors and select the DSR Mailbox tile. The setup page opens with the IMAP Configuration card at the top and the status badge reading Not Tested.
  2. Enter the IMAP Server host name (for example imap.example.com). Leave Port at 993 and Use TLS at Yes (recommended) unless your provider says otherwise; the hint names 143 for a connection without TLS.
  3. Enter the Username (usually the email address) and the Password. The Save Configuration button stays disabled until both the server and the username are filled in.
  4. Change Mailbox Folder only if requests are filed into a subfolder; it defaults to INBOX.
  5. Select Save Configuration. The button reads Saving..., then the settings are stored with the password encrypted. The save is recorded in the audit log. An invalid port or a missing field shows an error above the form and nothing is saved.
  6. Select Test Connection. The badge reads Testing... while Aegis signs in and lists the account's folders; it does not read or move any email. On success the badge turns to Connected and the green box shows the host, folder and folder count. Reading starts at the next 15-minute run.
Reading only starts after a successful test

Saving alone does not start reading the mailbox. Aegis reads it only while the connector is Connected, and that state comes from a successful Test Connection.

When the test fails

A failed test turns the badge to Connection Failed and shows a short reason. The reason is also kept on the page as the last recorded error, with the time it was recorded, so it is still there after a reload.

Every test, passed or failed, is written to the audit log with its outcome.

Change or rotate the settings

  1. Open the page. The form shows the saved values; the Password field is empty and its hint reads Leave blank to keep current.
  2. Change what you need and select Save Configuration. To rotate the password, type the new one; leaving it blank keeps the stored one.
  3. Select Test Connection again. Any change to the saved settings sets the connector back to not connected, so reading pauses until this test succeeds.

A stored password stays tied to the server, port and TLS setting it was entered for. If you change the IMAP Server or the Port, or switch Use TLS to No, enter the password again in the same save; Aegis refuses to carry the old one over, and records the refusal in the audit log.

Disconnect the mailbox

  1. In the Disconnect connector card, select Disconnect. A confirmation dialog explains that the configuration and credentials are deleted and reading stops.
  2. Confirm. Aegis deletes the stored settings and password, records the change in the audit log and returns you to the Connectors overview. Requests already created from emails stay in GDPR. You can configure the mailbox again later.

The AI assist

Each new email is classified by AI as a request or not, and by type (access, erasure, portability and so on). What happens next depends on how confident the classification is:

Confidence What Aegis does
70% or more Opens a pending request with the deadlines started and a note naming the email subject and confidence, then looks up what data you hold on the person and prepares a draft response. Admins and Managers are notified to review and confirm it.
30% to 70% Opens no request. Admins and Managers are notified that the email needs a person to look at it.
Below 30% Treats the email as not a request and takes no action.

The AI never acts on its own: a person confirms each request, reviews and edits the draft, and sends the acknowledgement and the response from the request in GDPR. Each classification is an AI action metered against your organisation's AI credits. When AI is switched off for the organisation, or the credits run out, emails are still collected but are left unclassified for the privacy team to handle by hand.

Tips and limits

Where this connects

Requests are handled in GDPR; the end-to-end flow is in Handle a data subject request. The other connectors and their shared lifecycle are in Connectors, and outgoing email is set up in SMTP.