GDPR

One workspace for your data-protection records: subject requests, processing activities, impact assessments, processor agreements, transfers, retention and consent.

GDPR (the European Union's data-protection law) places record-keeping duties on any organisation that handles personal data. This module gathers that work under one GDPR entry in the sidebar. It does not replace your legal team's judgement; it gives you the records and the audit trail to show a supervisory authority (your data-protection regulator) that you are accountable.

This chapter is the module reference. For the most common journey worked end to end — a person asking for their data, from inbox to closure — see the full walkthrough in Scenario: handling a data-subject request; HR staff who receive such requests first should start with the HR scenario.

If you do not see GDPR in the sidebar

The module is provisioned per tenant. When it is not enabled the entry is hidden and the registers cannot load. Ask your account manager to switch it on.

Who uses it

A Viewer and a Contributor can open every register. Creating and editing records needs Manager or Admin. Those buttons are absent rather than disabled for lower roles, which is why the register captures here show no Add button: they were taken as a Contributor. The two full-page create forms shown later were captured as a Manager. On the landing page the same rule hides the Start DPIA and Add Activity tiles from a Contributor.

A Contributor may still work subject requests, within limits. They can acknowledge a request that is unassigned or assigned to them. Moving a request on — Mark Verified, Start Work, completing it, refusing it, or editing its AI draft — works only on a request assigned to them; on any other open request the page says Unassigned — ask a manager to assign it to you before responding or refusing. Managers and Admins may act on every request. Deciding a DPIA needs the approval right only Manager and Admin hold.

What's on this screen

The landing page at /gdpr is headed GDPR Compliance. The Deadline Alerts panel fills the first screen: five pills — All, DSR, DPA, Consent, Transfer — above rows that each name a record and the party it concerns, with the due date underneath and a coloured days marker on the right. A coloured bar down the left edge of each row shows urgency: red for the most urgent, then amber, yellow and green. A subject-request line reads as the right being exercised and the person's email address; an agreement line as DPA and the supplier; a transfer line as Transfer and its processing activity.

Scrolling on brings four metric cards — Processing Activities, Data Subject Requests, Data Processing Agreements, Consent Records — then the Quick Actions tiles (Handle DSR and Transfers for everyone; Start DPIA and Add Activity for Managers and Admins). Below them sit a Recent Subject Requests panel, which points you to the queue with a View all link rather than listing requests itself, and a Compliance Checklist. The module has one sidebar entry, so those cards and tiles are how you reach its registers.

  1. In the sidebar, open PRIVACY & WHISTLEBLOWING and choose GDPR. The landing page opens and the alerts panel loads.
  2. Select a pill in Deadline Alerts. All is active on arrival; another narrows the feed to that one kind of record.
  3. Select an agreement line. It opens that processor agreement's own page, where the expiry date can be updated.
  4. Select a transfer line. It opens the transfer, whose Next Review Date raised the alert.
  5. Select a subject-request line. It opens the request. Work red markers first — that date has passed. On the captured screen an agreement 30 days overdue heads the list, with several requests overdue below it and later ones marked days remaining.
  6. The ? in the top bar opens this guide inside Aegis. Scroll on and select a card or tile to open the register behind it.
The GDPR Compliance landing page with the Deadline Alerts panel and its filter pills — /gdpr.
The GDPR Compliance landing page with the Deadline Alerts panel and its filter pills — /gdpr.
Consent alerts do not open a record

Subject-request, agreement and transfer lines open the record they name. A consent line has no page of its own to open, so it stays a plain line: go to the consent register and search for the person there.

Handling a data subject request

A data subject request (DSR) is a person asking to see, correct or delete the data you hold about them — or to restrict it, object, or receive a portable copy, or to challenge an automated decision. The queue at /gdpr/dsr is headed Data Subject Requests. Under the heading a short notice states the retention position, explained under “How long requests are kept” below. Then come a Search by email… box, All Types and All Statuses dropdowns and an Overdue Only tickbox, above a table of Type, Subject, Status, Requested, Due Date and colour-coded Time Left. The queue shows 20 requests a page, with page controls underneath when there are more.

  1. Open the queue from the Data Subject Requests card or the Handle DSR tile. The sidebar entry under PRIVACY & WHISTLEBLOWING returns you to the landing page.
  2. Read the notice under the heading: requests stay in the register indefinitely, and the personal data on a completed or refused request is anonymised three years after its response date unless it is under legal hold.
  3. Type part of an email address into Search by email…. The table narrows as you type, to the requests whose subject address contains it.
  4. Narrow further with the dropdowns or the tickbox; the filters combine. All Statuses also offers Open (not closed), which shows every request still in play.
  5. Read Status and Time Left to decide what comes first. A red Acknowledgement overdue badge beside the status means the Article 12(3) acknowledgement deadline has passed without one, even when Time Left is still green; a Legal hold badge marks a request exempt from anonymisation. Time Left turns amber close to the deadline and red once it has passed. The captured screen shows an acknowledged erasure request with 25 days left, a verified portability request with 21 days left, an in-progress access request with 4 days left in amber, and completed or refused rows showing a dash.
  6. Select a row. The request opens on its own page with a details grid and the Fulfillment section described next.
The data subject request queue with its retention notice, email search, type and status filters and the Time Left countdown — /gdpr/dsr.
The data subject request queue with its retention notice, email search, type and status filters and the Time Left countdown — /gdpr/dsr.

Working a request on its page

The request page carries a Fulfillment stepper: Pending → Acknowledged → Verified → In Progress → Completed or Refused. The details grid shows the request type, the data subject, the dates, the acknowledgement deadline, the request language where one was recorded, and Assigned to when someone is assigned. When an administrator has turned AI off for the organisation, a banner on the queue and on the request page says the AI steps are paused.

  1. Select Acknowledge Request (shown only while Pending). Aegis records the acknowledgement and its operator before attempting the notification. The delivery panel remains available after reload: send a pending notification only if no attempt has started. An uncertain or stalled attempt is never resent. Check the original outcome or contact the person through another channel, then record your confirmation and a note. Human confirmation is labelled separately from the mail service’s acceptance.
  2. Advance the request as the work progresses. Once a request is Acknowledged, Mark Verified records that the requester's identity has been confirmed; once Verified, Start Work moves it to In Progress. Both need the DSR-handling permission, and each moves the stepper one stage.
  3. If an AI-Drafted Response panel appears, review it. It shows the suggested reply, a confidence figure, and how many systems and records the data lookup found. Use Edit Draft to correct the text (the panel then shows Edited by reviewer) or Reject Draft to discard it, with an optional reason. Approve & Send is offered only once the request is In Progress; it records the draft as the response and moves the request to Completed.
  4. To close the request with a response you write yourself, select Complete Manually (offered from Acknowledged onwards), type the response you sent (or will send) to the person into the required box, and select Confirm Completion. The request moves to Completed — final — and the text is kept on the record. Sending the answer through your normal channel remains your job; file a copy under COMPLIANCE → Evidence.
  5. To turn a request down, select Refuse, type the Refusal Reason and select Confirm Refusal.
  6. If the request uncovers a personal-data breach, log it under SECURITY INCIDENTS. The 72-hour notification clock is handled there.
  7. Open AUDIT → Audit Log to see who moved a request, when, and to what.
Status What it means
Pending Logged; no acknowledgement sent
Acknowledged Receipt recorded; check the separate notification delivery status
Verified Identity confirmed by the recorded method
In Progress Being worked on
Completed A response is recorded; final
Refused Turned down with a recorded reason; final
Expired Set automatically once the deadline passes an open request

Logging a new request

With Manager or Admin rights the queue shows New Request, which opens the full-page form at /gdpr/dsr/new, headed New Data Subject Request. Its subtitle says it plainly: the GDPR response clock starts on creation. The form has two cards, Request Details and Verification & Notes, and every field carries a line of help underneath.

  1. Choose the Request Type. Access is preselected, and the line under the box explains the right each type exercises — here Article 15.
  2. Type the Data Subject Email. It is the address the request came from, used to verify identity and to send the response.
  3. Optionally add the Data Subject Name — the name to address the response to. Left blank, the email address is used.
  4. Set the Request Language to the language the request was made in. It reads Not specified (English) until you choose; the list offers English, French, Dutch, German, Spanish, Italian and Portuguese, each in its own name. The AI response draft is written in this language (Article 12(1)).
  5. Record the Verification Method — how the person's identity was confirmed, if it already has been.
  6. Add Notes for whoever handles the request. They are internal, never shared with the data subject. Then select Create Request at the foot of the form. The request saves as Pending with a due date 30 days out, and its detail page opens.
The full-page form for logging a new data subject request — /gdpr/dsr/new.
The full-page form for logging a new data subject request — /gdpr/dsr/new.

Where your licence includes AI, the organisation has AI switched on, you hold the right to run AI actions and you have acknowledged the AI transparency notice, creating the request also starts the AI pipeline in the background. If any of those is missing, the request is still saved; it does not enter the pipeline, and you handle it manually. In the pipeline, Aegis looks the person up across your connected systems, maps what it finds, and drafts a response. The draft appears on the request page as the AI-Drafted Response panel described above. If a step fails, the page shows AI draft not available with the reason, and you handle the request manually.

The deadline counts from the date you log it

Aegis sets the due date 30 days from the moment the record is created, not from the date the request arrived. If it reached you earlier, note the real received date so your team manages the true legal deadline. The acknowledgement is the only message Aegis sends.

How long requests are kept

Aegis never deletes a data subject request. The register is your Article 5(2) accountability record: a supervisory authority asking how you handled the requests you received in a given year has to be able to see them. There is deliberately no delete button and no delete endpoint.

What does expire is the personal data on the request. Three years after the Response Date, a request whose status is Completed or Refused is anonymised automatically, overnight:

The date it happened is shown on the request as Anonymized.

A request under Legal hold is never anonymised, whatever its age. A hold is for when litigation, a supervisory-authority inquiry or an internal investigation means you may still need the original identifiers. The hold is shown as a badge beside the status, both in the queue and on the request page. The request page has no switch for setting or clearing it: the hold is set through the Aegis API, so ask whoever administers your integrations.

Set a legal hold before the three years elapse

Anonymisation cannot be undone. Once a request has been anonymised, the requester's identity is gone from the register for good, so a hold that should have been set and was not cannot be repaired afterwards.

Building the record of processing activities

A record of processing activities (ROPA) is the map, required by Article 30, of every activity in which you process personal data. The page at /gdpr/processing is headed Processing Activities. A Register switch sits at the top (All activities, Controller register (Art. 30(1)), Processor register (Art. 30(2))). Below it are a Search activities… box and an All Legal Bases dropdown on the left and Export ROPA on the right, then a table of Name (with a one-line description), a coloured Legal Basis badge for every basis the activity relies on, Data Categories as a count, a Special Data flag and Retention. A processor activity carries a Processor badge beside its name and a dash under Legal Basis.

  1. Open the register from the Processing Activities card. PRIVACY & WHISTLEBLOWING → GDPR in the sidebar takes you back to the landing page.
  2. Choose a register view. All activities is selected on arrival; the controller and processor views narrow the table to that role.
  3. Search by name, or pick a legal basis; the filter matches an activity on any of its bases. On the captured screen AI-assisted consumer credit pre-approval shows two badges, Contract and Legitimate Interests.
  4. Look for the Processor badge. The captured screen shows one on Card payment processing for merchant clients, whose legal basis reads as a dash because the basis belongs to the controller you process for.
  5. Select Export ROPA. A dialog offers JSON, CSV or PDF; choose a format and a Register — the controller register holds controller activities only, the processor register has the Art. 30(2) columns — and it downloads.
  6. Select a row to open the activity: purposes, data categories, recipients, retention, security measures and transfer safeguards, plus a Related Data block counting attached consents and transfers. A Yes under Special Data means Article 9 special-category data.
  7. With Manager or Admin rights, Add Activity sits beside the export button and opens the form for name, legal basis, purposes, categories, recipients, retention, security measures and transfer safeguards. The same rights add an Actions column with a Start DPIA link on every row.
  8. File the export under COMPLIANCE → Evidence so an auditor can find the version you relied on.
The processing-activities register with its register switch, legal-basis badges, a Processor badge and the Export ROPA button — /gdpr/processing.
The processing-activities register with its register switch, legal-basis badges, a Processor badge and the Export ROPA button — /gdpr/processing.

Role, controller, owner and legal bases

The activity form records who is accountable for the processing, not only what it is. The detail page shows the same fields.

Field What it records
Role Controller (the organisation decides why and how the data is processed; the Art. 30(1) register) or Processor (it processes on behalf of another controller; the Art. 30(2) register). Existing activities are controllers.
Controller on whose behalf Processor activities only, and required: the controller you process for, with optional Controller contact details. A processor activity is not asked for a legal basis or a legitimate-interests justification; those belong to the controller.
Controller entity / Processor entity Only when another legal entity, such as a group company, plays that role for this activity. Left empty, the organisation from Settings applies; the detail page then marks the controller as organisation default.
Owner Pick a user, or type a name for someone without an account. Setting one clears the other. A deactivated owner is shown as inactive.
Additional legal bases Tick every further Art. 6(1) basis the activity also relies on, for example contract and legal obligation. Legal Basis stays the primary basis. Whenever legitimate interests is relied on at all, the Legitimate Interests Justification is required.

The export follows these fields: an Owner column and a per-activity Controller column, and every legal basis an activity relies on.

Assessing high-risk processing

A data protection impact assessment (DPIA) is the analysis Article 35 requires before high-risk processing. The page at /gdpr/dpia opens with a When is a DPIA Required? panel listing four triggers, then a Search assessments… box with All Statuses and All Risk Levels dropdowns, a count — 14 assessments on the captured screen — and the table: Processing Activity, Status, Residual Risk, Consultation and Decision, which shows the approval date once an assessment is approved. Managers and Admins also see Create DPIA beside the heading and Start from Processing Activity beside the count.

  1. Open PRIVACY & WHISTLEBLOWING → GDPR. Managers and Admins take the Start DPIA tile; everyone else reaches the register at /gdpr/dpia.
  2. Search by activity name. The table narrows to the matching assessments, and the count follows.
  3. Filter by status — Draft, Pending Review, Approved or Rejected.
  4. Filter by residual risk — Low, Medium, High or Critical. Where Article 36 prior consultation applies, Consultation reads Required.
  5. Read the trigger panel first. If none of the four applies, record why instead. Then select a row to open the assessment: necessity, proportionality, risks and mitigations, and its residual risk.
  6. Decide it. With Manager or Admin rights the detail page carries Approve DPIA and Reject DPIA on any assessment not yet decided; a rejection asks for a reason. A decided assessment cannot be decided again.
  7. A high residual risk you accept rather than mitigate belongs in RISKS as well. Aegis does not raise the risk for you. Keep the signed write-up under COMPLIANCE → Evidence.
The DPIA register with the trigger-conditions panel, its search and filters, and the assessments table — /gdpr/dpia.
The DPIA register with the trigger-conditions panel, its search and filters, and the assessments table — /gdpr/dpia.

Creating an assessment

Create DPIA opens the full page at /gdpr/dpia/new, headed Create DPIA. Start from Processing Activity takes you instead to the processing register, where each row's Start DPIA link opens the same form with that activity already chosen. Every assessment is anchored to one activity, and an activity can have only one — so build the ROPA first.

  1. Select the Processing activity the assessment covers. The dropdown lists your recorded activities; with none recorded, the form says so and links you to the register.
  2. Necessity (required): why the processing is necessary for the stated purpose.
  3. Proportionality (required): how it is proportionate to that purpose.
  4. Under Risks & Mitigation, list the Identified risks to data subjects — one per line.
The full-page DPIA creation form — /gdpr/dpia/new.
The full-page DPIA creation form — /gdpr/dpia/new.

Further down, below the captured part of the form:

Recording processor agreements

A data processing agreement (DPA) is the contract Article 28 requires with every supplier that processes personal data for you. The page at /gdpr/dpa has a single All Statuses dropdown above Vendor, Status, Version, Signed Date and Expiry Date. Version adds the standard contractual clauses version in brackets where one is recorded, for example (SCC: 2021/914 Module 2). An active agreement that expires within 30 days shows its expiry date in amber with a warning sign. The captured screen shows the register filled with agreements in every status; a new tenant starts on No data processing agreements found.

  1. Create the supplier first. Vendors live under RISKS → Vendors, and an agreement must point at a vendor record that already exists.
  2. Keep the signed contract itself under COMPLIANCE → Evidence. This register holds facts about the document, not the document.
  3. Return to the landing page and select the Data Processing Agreements card. The register opens.
  4. With Manager or Admin rights, Add Agreement appears beside the filter and opens a dialog: vendor, status, DPA and SCC version, signed and expiry dates, the breach-notification window in hours (leave Breach Notification (hours) empty when the contract names none: it then reads Not specified, and Aegis does not assume 72 hours), and whether encryption, audit rights and location restrictions are agreed.
  5. Use All Statuses to work one slice — Draft, Pending Signature, Signed, Active, Expired or Terminated.
  6. Select a row. The agreement opens on its own page with its details, the breach window and security terms, any location restrictions, and the AI metadata screening described below. On renewal, Managers and Admins select Edit and update the dates; the expiry date feeds the deadline alerts on the landing page. Delete asks for confirmation first.
The processor-agreement register with its status filter and SCC versions beside each agreement version — /gdpr/dpa.
The processor-agreement register with its status filter and SCC versions beside each agreement version — /gdpr/dpa.

Transfers out of the EEA

Transfers record when personal data leaves the European Economic Area and the safeguard that authorises it. The page at /gdpr/transfers is headed International Data Transfers and opens with a Transfer Mechanisms reference panel — adequacy decisions, standard contractual clauses (2021 version), binding corporate rules and Article 49 derogations — then a Filter by country… box and an All Mechanisms dropdown above Destination, Mechanism, Processing Activities, Last Review Date and Next Review Date. A next review date that has passed shows in red with a warning sign; on the captured screen that is the first row, a transfer to the United States under standard contractual clauses.

  1. In the sidebar, open PRIVACY & WHISTLEBLOWING → GDPR, then select the Transfers tile on the landing page. The register opens.
  2. Read the mechanisms panel first: the one you pick sets what the record must prove. Unsure which mechanism applies? The ? in the top bar opens this chapter inside Aegis.
  3. Type a country into Filter by country… or pick a mechanism. The table narrows to the matching transfers.
  4. Keep Next Review Date current — it is what raises a transfer in the alerts. Select a row to open the transfer.
  5. Scroll to Transfer Impact Assessment (TIA). The section appears only where your licence includes the GDPR automation feature. Run TIA queues an AI-assisted adequacy and Schrems II analysis, which returns an overall risk, a confidence figure and recommendations.
  6. Once you have read the result, select Mark as reviewed; the section then shows who reviewed it and when. Use Copy, Export PDF or Export DOCX on the TIA, and file the result under COMPLIANCE → Evidence.
The international-transfers register with the mechanisms reference panel and an overdue review date flagged in red — /gdpr/transfers.
The international-transfers register with the mechanisms reference panel and an overdue review date flagged in red — /gdpr/transfers.

Recording a transfer

With Manager or Admin rights, Add Transfer opens the full page at /gdpr/transfers/new, headed New International Transfer, split into Transfer Information and Safeguards & Risk.

  1. Select the Processing Activity the transfer belongs to.
  2. Select the Destination Country. Choosing Other adds a free-text field for the country name.
  3. Select the Transfer Mechanism. Standard Contractual Clauses is preselected, with the Article 46(2)(c) reference beneath; an adequacy decision asks for its reference instead. For a United States recipient certified under the EU-US Data Privacy Framework, choose the adequacy decision mechanism (the hint under the field says so).
  4. Confirm the SCC Version — 2021 SCCs (Current) unless you have a legacy set still in force.
  5. Name the Recipient, and fill Data Categories beside it.
  6. Record the Legal Basis. Then, under Safeguards & Risk, describe the Supplementary Measures (encryption, pseudonymisation) and the risk summary, and save. The transfer opens on its detail page.
The full-page form for recording an international transfer — /gdpr/transfers/new.
The full-page form for recording an international transfer — /gdpr/transfers/new.

Two further fields sit in the form, and in the inline edit on a saved transfer's detail page:

Retention schedules

Retention defines how long each category of personal data may be kept, as Article 5(1)(e) requires. The register is at /gdpr/retention and is reached by address — it has neither a card nor a tile on the landing page. A short panel of retention principles sits above the table, which lists policy name, retention period, data categories, disposal method and review date, with an All Methods filter and, for Managers and Admins, Add Policy, which opens a full-page form at /gdpr/retention/new. Each policy records the retention criteria, a disposal method — Deletion, Anonymization or Archival — and a next review date. Aegis holds the schedule but deletes nothing when a period ends; the disposal records that prove you followed it belong under COMPLIANCE → Evidence.

Keeping consent records

Where consent is your lawful basis, Article 7 requires you to show it was freely given, specific, informed and unambiguous. The page at /gdpr/consent opens with a note saying plainly that consent records normally come from your own application's consent collection, and that this view is for managing and withdrawing them. A Search by email… box, an All Types dropdown and an Active Only tickbox — ticked by default — sit above Subject, Type, Purposes, Given, Status and Actions. Type is a coloured badge (the captured screen shows Informed, Specific and Explicit), and Purposes is a count. On the captured screen every listed record is Active and the Actions column is empty, because it was taken as a Contributor. A new tenant starts on No consent records found.

  1. Open the register from the Consent Records card, reached through PRIVACY & WHISTLEBLOWING → GDPR in the sidebar.
  2. Search by email address, or untick Active Only to bring withdrawn records back. The tickbox filters on withdrawal alone, so a consent past its expiry date that was never withdrawn stays in the list either way.
  3. Select a row to read the full record: activity, purposes, consent type, the proof and version you recorded, and the metadata captured at the time. Its badge reads Active, Withdrawn or Expired.
  4. With Manager or Admin rights, Record Consent logs one by hand — email, activity, type, purposes, dates, proof and version.
  5. To process a withdrawal, a Manager or Admin selects Withdraw in Actions and confirms. The status becomes Withdrawn, the time is stamped, and it cannot be undone.
  6. A withdrawal is a record, not an instruction to your systems: stop the processing where it happens, then use AUDIT → Audit Log to prove when.
  7. The wording and version shown to the person is the proof behind the record — keep it under COMPLIANCE → Evidence.
The consent register with its search, type filter and Active Only tickbox — /gdpr/consent.
The consent register with its search, type filter and Active Only tickbox — /gdpr/consent.

The AI assist

Four AI actions are live in this module where your licence includes them. Each consumes the tenant's AI credits, and each stops when an administrator turns AI off.

The first three are Manager or Admin actions. The response draft is reviewed by whoever handles the request. The AI drafts and a person decides: you review, edit and save — or edit, reject or approve the response draft — and the assessor of record is always a named human. Nothing an AI action produces reaches a data subject or changes a record's status until someone acts on it.

Tips and limits

Where this connects

A personal-data breach must reach the supervisory authority within 72 hours where required — handle and time-stamp it in Incidents. Agreements depend on Vendors; residual risks you accept from a DPIA belong in Risks; contracts, exports and write-ups belong in Evidence. The cross-system lookup that gathers what you hold about a person draws on the systems joined up in Connectors. Who may do what here follows Part 3 — What each role can do, and the whole journey runs end to end in When someone asks for their data.