Transparency about the way an organization handles data of its customers is very important for building a relationship of trust. To assist you in this we have developed 'User Data Requests'. This allows your customers to review personal data they have shared with you and is being stored on our platform. Also it allows your customers to edit or delete their data from the platform.
Setting up User Data Requests
Open the profile menu at the bottom left and click on Settings. Click on the tab Privacy Requests. Enter the following:
- Request approval email: Here you can provide us with an email address that should be notified in the case a request is submitted by your customer. This email address will be provided to your customer in the event a request is disapproved.
- User Data Request link: Offer this link to your users to submit a User Data Request, for example by including it in your privacy statement.
Please note! When you are using the link in your privacy statement, but you haven’t set a (correct) email address, the requests can still come in, but you won’t get a notification. Data requests which are ignored, will be automatically approved after 90 days.
Example of the page behind the User Data Request link:
All data requests entered here can be Approved or Disapproved in Data > Data requests.
What information is considered Personal Identifiable Information?
When a data request is made, we will by default provide information that is known for the following fields:
- Email Address
- Phone
- First Name
- Last Name
When a request is received to remove Personal Identifiable Information, we will also delete the following datapoints by default:
- IP Address
- Cookie ID
Custom Fields
If you are using custom fields to store user properties in Spotler Activate Platform, you will be given the option to indicate Personal Identifiable Information (PII) is being stored in a custom field. When this is the case, we will also provide the values known for these custom fields when a request has been received by us. Data containing PII cannot be fetched from URL parameters.