One of the first questions a business asks when they receive a privacy-related request from a user is: “how do we respond”? This guide contains templates for different types of privacy communication between privacy teams and their customers.
Communicating with your users regarding their privacy requests is an important part of running a best-practice privacy operation. But if you’re just getting started managing these requests, simply choosing the correct language can be its own unique challenge. We’ve prepared some examples that can serve any business hoping to smoothly manage subject requests. Each can be used to communicate with a subject that has filed any type of DSR…
Used to officially confirm to the user that their request has been received.
It may be sufficient to demonstrate or ensure that the Subject has access to the inbox or device for which they are claiming access. For instance, if a Subject requests to access or erase their data for firstname.lastname@example.org, this may be verified by sending them an email and asking them to reply from this address to confirm approval of the request. The following message should be used to verify the user has ownership/access to the inbox or device associated with the identity for which they have made the subject request.
If the business feels greater caution than Inbox Verification is necessary, a set of fixed questions may be asked to verify information the business already knows about the user. For example, as an e-commerce business, you might ask the user to confirm the date of their last order, the order number, and the dollar value.
Use this template to confirm successful identity verification and that processing will continue.
The topics these templates cover will often be the first interaction with users regarding their privacy relationship with your business. Adapting each of these templates to your company’s needs will ensure that a positive foundation is in place for ongoing respectful privacy management.
Learn more about all of the updates in the Fides 2.24 release here.
Ethyca’s Senior Software Engineer Adam Sachs goes through the thought process of creating Fideslang, the privacy engineering taxonomy that standardizes privacy compliance in software development.
Learn more about all of the updates in the Fides 2.23 release here.
Our Senior Software Engineer Dawn Pattison walks you through implementing data minimization into your business.
Learn more about all of the updates in the Fides 2.22 release here.
Ethyca’s Senior Software Developer Adrian Galvan explains how California is leading the way on AI regulations in the U.S.
Our team of data privacy devotees would love to show you how Ethyca helps engineers deploy CCPA, GDPR, and LGPD privacy compliance deep into business systems. Let’s chat!Request a Demo