DSAR Forms UX and Rights Localization

  • Updated

Our DSAR forms have recently received a UX overhaul going from a default form that looks like this:

Screenshot 2024-03-04 at 1.35.03 PM.png


To a default form builder that looks like this:

Screenshot 2024-04-18 at 1.02.12 PM.png

We're giving requesters a more dynamic UX to enable more dynamic capabilities behind the scenes, allowing for rights localization. 

What is Rights Localization?

A Data Subject from California, Virginia, Texas, or Ontario can exercise different rights based on their jurisdiction.

Using the same framework to DSAR rights that we recently released for automatic language translation in DSAR forms, emails, and the secure messaging portal so that Data Subjects are presented with the rights applicable to the regulations they fall under.

By default, requesters will see the rights granted to them based on their location. A requester's location will be automatically set based on their IP address, but if you wish, you may also enable a dropdown to display on your form that allows requesters to alter their specified location.

Both a requester's geo-identified location and the location they select will be stored on the request, and mismatches between these two values will be flagged on the request page in case you see a sudden uptick in requests from Poland:

Screenshot 2024-04-18 at 1.19.28 PM.png

The Benefits of Rights Localization

Rights localization relieves you of the need to constantly track privacy law updates for states and countries worldwide since these changes are built into the product. As new states adopt privacy laws, requesters from those states will automatically see the rights available to them the day those laws become effective. The same will be true for future updates to any existing privacy laws. 

Rights localization also avoids the pitfalls of a one-size (or two or three-size) fits all approach that results in imperfect compliance with regional regulations and an increased burden in responding to request types of all kinds from all across the world.

Rights localization allows for the best of all worlds. Your form will stay compliant with regional subject rights regulations with no effort on your part. You can offer highly local rights to prospects and customers no matter where they reside. And you can reduce the time you spend responding to complex and hard-to-fulfill requests from regions where these kinds of request types are not required by law, again, with no effort on your part.

How will these Changes Work for Existing Customers?

When rights localization is released next week, all forms will automatically reflect the new forms UX with requesters to your form selecting their request type before filling out the rest of the form.

The rights localization functionality described above will be enabled by default for newly created forms. However, in order to avoid sudden changes in form functionality, previously created forms will need to opt into the new rights localization functionality.

Here's how this will work:

  • Rights localization will be controlled through a new Request Types tab.
  • For new forms, each request type will default to rights localization for that request type in the Jurisdictions section below:

Request Types.png

  • Previously created forms will have all deleted request types set to Disable for everyone, while any existing request types will be set to Enable for everyone. This will ensure that any request types that are enabled today and display for all requesters, regardless of location, will continue to do so, and any request types that have been deleted and do not display for any requesters will also continue to do so.