1. Knowledge base
  2. Data subject requests (DSRs)

How to remove a data subject request type from your Clym widget

Steps to take to remove a data subject request type from being available in your Clym widget

Before removing a data subject request, or DSR, type from your widget, it is important to note that doing so may go against certain regulation requirements, which could put your website at risk of non-compliance. But there is no need to worry - by keeping default settings for your jurisdictions, Clym will ensure that each user sees the required data subject request options based on the regulation that protects them. However, if you still need to remove a DSR request type for any reason, removing a DSR request type is an easy 3-step process:


1. Sign in to your Clym Portal

You should have received a magic link in your initial onboarding email. Please click Sign in from the email to get started. Alternatively, navigate to Clym's home page and click on Sign in in the upper right-hand corner. 

Screenshot 2023-01-12 at 1.29.55 PM



2. Open your Website Settings

From the left side menu, select Website Settings. From here, you will see a list of all your domains, each with its unique settings.

Website Settings Information 1

Click the settings wheel next to the domain that you would like to change the default language for. This will open the website settings for that specific domain.

Website Settings Information 2



3. Remove the request type

From the Website settings menu, select the Geographical Settings drop-down arrow to expand the options. Click the three dots next to the jurisdiction that you want to edit. Click the clipboard and pencil icon to Edit.


In the pop-up window, click the drop-down menu next to Requests to expand the selections. To allow requests, first, ensure that Allow users to send requests is toggled on. Click the trash can icon next to the request type that you want to remove from your Clym widget. Click Submit.


If you encounter any challenges, please reach out to us at support@clym.io.