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 email@example.com, 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.
At Ethyca, we believe that software engineers are becoming major privacy stakeholders, but do they feel the same way? To answer this question, we went out and asked 337 software engineers what they think about the state of contemporary privacy… and how they would improve it.
The UK’s new Data Reform Bill is set to ease data privacy compliance burdens on businesses to enable convenience and spark innovation in the country. We explain why convenience should not be the end result of a country’s privacy legislation.
Our team at Ethyca attended the PEPR 2022 Conference in Santa Monica live and virtually between June 23rd and 24th. We compiled three main takeaways after listening to so many great presentations about the current state of privacy engineering, and how the field will change in the future.
For privacy engineers to build privacy directly into the codebase, they need agreed-upon definitions for translating policy into code. Ethyca CEO Cillian unveils an open source system to standardize definitions for personal data living in the tech stack.
Masking data is an essential part of modern privacy engineering. We highlight a handful of masking strategies made possible with the Fides open-source platform, and we explain the difference between key terms: pseudonymization and anonymization.
The American Data Privacy and Protection Act is gaining attention as one of the most promising federal privacy bills in recent history. We highlight some of the key provisions with an emphasis on their relationship to privacy engineering.
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!Book a Demo