DSAR management

Handle data subject access requests from submission to completion. Track SLA deadlines, assign tasks to your team, and provide a public portal for data subjects to submit requests, all with privacy-by-design data handling and automatic PII redaction. On the hosted service it is included, with up to 100 requests a month through the public form (1,000 with the volume upgrade).

Request lifecycle

Every DSAR moves through a defined lifecycle with automatic SLA tracking. The system monitors deadlines and alerts your team when action is needed.

1

Submitted

Request received

2

Identity check

Verify data subject

3

In Progress

Processing request

4

Review

QA before delivery

5

Completed

Response delivered

SUBMITTEDIDENTITY PENDINGIN PROGRESSON HOLDCOMPLETEDREJECTED

Privacy by design

PrivacyCloud is designed so that facilitating DSARs does not create new privacy risks. We collect the minimum data needed, redact it automatically after the retention period, and never include individual PII in reports.

Data minimization

The intake form collects only name, email, and request type. Phone and relationship are optional. Address is never collected via the portal.

Consent at intake

Data subjects must explicitly consent to processing before submitting. The privacy notice explains retention periods and redaction.

Auto-Redaction

After the retention period (30 days after closing on the hosted service; 90 days by default when self-hosted), all personal data is automatically replaced with 'REDACTED'. The anonymized audit trail is preserved.

PII-Free reports

The DSAR Performance Report contains only aggregated metrics: request volumes, SLA rates, type distributions. Zero individual data.

Manual redaction & deletion

Admins can manually redact PII or hard-delete completed requests at any time, without waiting for the retention period.

Audit trail integrity

Actions, timestamps, and staff IDs are preserved after redaction. Who did what and when remains traceable; only the data subject's PII is removed.

Request types

PrivacyCloud supports all GDPR data subject rights as request types.

ACCESS

Right to access personal data held by the organization (Art. 15)

ERASURE

Right to be forgotten: deletion of personal data (Art. 17)

RECTIFICATION

Right to correct inaccurate personal data (Art. 16)

PORTABILITY

Right to receive data in a machine-readable format (Art. 20)

OBJECTION

Right to object to processing of personal data (Art. 21)

RESTRICTION

Right to restrict processing of personal data (Art. 18)

Public portal

Give data subjects a dedicated portal to submit requests. The portal is customizable with your organization's branding and generates a shareable link you can add to your privacy policy. The portal starts switched off: it goes live when an owner or administrator switches on "Public form active" in the rights-request settings, and that switch is recorded in the activity log. Until then, anyone who opens the link sees your privacy contact.

Portal URL

https://app.privacycloud.com/dsar/your-org-slug

Share this URL in your privacy policy so data subjects can submit requests directly. The portal includes a consent checkbox and privacy notice explaining how their data will be handled.

Portal configuration

Form title & descriptionCustomizable
Enabled request typesSelect which rights to offer
Custom CSSMatch your brand
Thank-you messagePost-submission text
Retention period30 days after closing (hosted); 90 by default (self-hosted)
Privacy notice linkLink to your policy

Task management

Break down each DSAR into actionable tasks and assign them to team members. Track progress, add notes, and ensure nothing falls through the cracks.

Example Tasks for an Access Request

Verify identity of data subjectPrivacy officer
Search CRM for subject recordsIT team
Search email archivesIT team
Compile and review data packagePrivacy officer
Redact third-party dataLegal
Deliver response to data subjectPrivacy officer

SLA tracking

The system automatically calculates SLA deadlines based on your applied jurisdictions. Deadlines are per-framework: GDPR (one month, extendable by two further months where necessary), CCPA/CPRA (45 days, extendable once by a further 45 days where reasonably necessary), LGPD (15 days), and 40+ others. Reminder emails go out 7, 3 and 1 day before the deadline and once when it is overdue. Where the law allows an extension, the Extend deadline button on the request applies it once and records your reason.

15-45

days by jurisdiction

Auto

deadline calculation

Alerts

approaching & overdue

Data retention & auto-Redaction

PrivacyCloud automatically redacts personal data from completed DSAR records after the configured retention period. This ensures the platform does not become a risk vector for the organizations it serves.

1

Request completed

DSAR fulfilled

2

Retention period

30 days after closing (hosted); 90 by default (self-hosted)

3

Auto-Redaction

PII replaced

4

Anonymized record

Stats preserved

What gets redacted

  • Requester name, email, phone
  • Request description and details
  • Communication content and attachments
  • Task data exports and notes

What is preserved

  • Request type (Access, Erasure, etc.)
  • Status and SLA dates
  • Audit trail (actions + timestamps)
  • Aggregate statistics for reporting

Performance report (PDF export)

Export a DSAR Performance Report as a polished PDF for regulators, auditors, or board presentations. The report contains only aggregated metrics: no individual personal data.

Report sections

Executive summaryTotal requests, on-time rate, avg resolution
Volume by typeAccess, Erasure, Portability breakdown
Status distributionOpen, completed, overdue counts
SLA compliancePer-jurisdiction deadline analysis
Monthly trend12-month received vs completed
Aging analysisOpen requests by age band

Processing a DSAR request

1

Receive request

System

A data subject submits a request through the public portal (with consent) or you create one manually in Rights requests.

2

Verify identity

Privacy officer

Confirm the identity of the data subject. Update the request status to reflect the verification outcome.

  • •Request additional ID documents if needed
  • •Mark identity as verified or rejected
3

Create and assign tasks

Privacy officer

Break the request into tasks and assign them to the relevant team members.

4

Collect and review data

Team

Team members search systems, compile data, and upload findings. The privacy officer reviews for completeness.

5

Deliver response

Privacy officer

Send the final response to the data subject and mark the request as completed. PII will be auto-redacted after the retention period.