How to Generate and Customize a Data Subject Request (DSR) Portal
Captain Compliance lets you create and manage data subject request (DSR) portals, with support for portal customization and request fulfillment workflows. This article explains how to create a DSR portal, customize its content and appearance, and confirm that requests are received correctly.
Step 1: Create a DSR portal
DSR portals are typically created at the organization level.
Select DSR Portal → Forms in the sidebar of the Captain Compliance app.
Select New DSR Portal.
Enter a DSR Portal Name and select Add Form.
This creates a DSR portal that you can customize and publish.
Step 2: Customize DSR portal details
Click your DSR portal.
Open the Detail tab.
Configure the fields listed below.
Company Name
Company Privacy Email: this field supports future functionality and should still be populated.
Header Text: displays informational content at the top of the portal.
Footer Text: displays supplemental information at the bottom of the portal.
Routing Workflow: optionally links a workflow, so that new submissions create tasks for your teams. See How to Process and Route Data Subject Requests.
Check email notifications
The DSR portal sends email notifications to authorized personnel when new requests are submitted. To make sure requests are received:
In an organization account, select Organization in the sidebar, open Notification, and check Destination Mail.
Confirm that a valid email address is entered, and select Save if you change it.
Important: without this configuration, requests may be submitted successfully but not routed to the appropriate inbox. Personal accounts do not show this menu. If you cannot find it, contact your Captain Compliance representative, and check DSR Portal → Requests regularly in the meantime.
Step 3: Customize DSR portal fields
Each DSR portal loads with a default set of fields. Review them carefully and adjust as needed.
Privacy laws generally require that organizations request only the information necessary to verify identity and fulfill the request. As a result:
Remove any fields your organization does not need.
Add fields only when they are necessary for request fulfillment.
To add a new field:
Go to Fields.
Select Add Fields → Create Field.
Configure the Field Label, Description, and Field Type.
You can reorder fields with drag-and-drop.
Default fields
The default set commonly includes:
First name
Last name
Email address
Relationship to the data controller
Whether the request is submitted by a third party
Relationship to the data subject (if applicable)
Country of residence
State or province of residence
Type of data subject request being exercised
Description of the request
For example, phone number is not included by default, but you can add it if your verification or response process requires it.
Step 4: Customize DSR portal appearance
Go to Appearance and configure the following options:
Image: upload your organization’s logo.
Theme Color
Font Color
Border Width
Border Radius
Show branding: shows or hides the branding on the form.
Type: Structured shows all fields at once; Linear presents a step-by-step sequence of questions.
These settings control the visual presentation of the DSR portal. They do not affect request processing logic.
Step 5: Test the DSR portal
Before publishing, test the portal end to end.
Select DSR Portal Link on the portal’s page and open the URL.
Submit a test request.
Go to DSR Portal → Requests in the Captain Compliance app and confirm that the request appears in the queue.
Open the request and try each request status: Pending, In Progress, Completed, and Not Applicable.
This step validates manual request intake and status management. Fulfillment can also be automated through integrations: see How to Automate Fulfillment of Data Subject Request (DSR) Portal Requests.
Step 6: Legal review
Before publishing, Captain Compliance strongly recommends submitting the DSR portal for internal and legal review.
Captain Compliance simplifies DSR intake and workflow management, but ultimate responsibility for fulfilling privacy requests rests with your organization. Make any required changes using the steps above.
Step 7: Publish the DSR portal
There are two common ways to deploy a DSR portal:
Most organizations link directly to the hosted DSR portal.
Some embed the DSR portal in a page of their own website.
To link to the hosted portal, select DSR Portal Link on the portal’s page and copy the URL.
To embed the portal, select DSR Portal Script and add both snippets to your page: the script tag, and the container element that marks where the portal should load.
<script
src="https://api-prod.cptn.co/requestForm/script"
access-token="YOUR_ACCESS_TOKEN">
</script>
<div id="captain_compliance_form_container"></div>Copy the snippet from the app, because it contains your portal’s access token. If your site sends a Content Security Policy header, see How to Configure a Content Security Policy (CSP) for Captain Compliance.
For where to place the link, how to confirm that the published portal works, and what to check if an embedded portal doesn’t load, see How to Publish Your DSR Portal with a Link or an Embed Script.
Once published, the portal is ready to receive live data subject requests. To manage requests after they arrive, see How to Process and Route Data Subject Requests.




