Frequently Asked Questions About GDPR

read

Overview

GDPR stands for the General Data Protection Regulation. It’s a law enacted by the European Commission in 2016 that goes into effect on May 25, 2018. It’s designed to protect the privacy of all EU citizens, including when those citizens engage with businesses located outside the European Union, by imposing regulations around personal data. For more information on GDPR, check out our blog series.

Disclaimer

The information provided here is intended to be educational and should not be construed as legal advice. Klaviyo encourages all of our customers -- and all ecommerce merchants -- to seek legal advice for counsel on how they specifically should prepare for GDPR.

Is it legal for me to transfer data from my European customers to Klaviyo?

Yes. Klaviyo is certified Privacy Shield compliant, and data transfer out of the EU is legal on this basis. Privacy Shield requires that US-based companies provide the same protections for data export from the EU that are required under EU law, including GDPR.

If we can't prove explicit opt-in for legacy profiles, is there a way to confirm consent via email?

You can certainly re-confirm using an informed, explicit opt-in email. Check out our guide to re-permissioningRemember, the key requirements for consent under GDPR are:

  • Don’t use pre-ticked boxes or any other type of default consent
  • Use clear, plain language that is easy to understand
  • Specify why you want the data and what you’re going to do with it
  • Give separate, granular options to consent separately for each method of contact
  • Name your organization and any third party processors you will be using
  • Tell individuals they can withdraw their consent at any time
  • Ensure that individuals can refuse to consent without detriment
  • Avoid making consent a precondition of doing business with you

How do we prove consent, including the day a subscriber opted in?

In addition to using double opt-in, you are required to retain the language that was presented to the consumer in the form, email or webpage where they provided consent. So, you will have to be able to produce both the time/date that they consented and exactly what they consented to.

For our email fields on our websites, do we need to add more checkboxes for the customers to tick before submitting their details? 

Klaviyo provides GDPR compliant forms with multiple checkboxes, allowing for granular consent (i.e. separate consent for email marketing and Facebook marketing).

You will need to select forms identified as GDPR compliant, and then customize them as appropriate given your marketing program. If you are gathering personal information about EU consumers through other platforms, you’ll need to make changes on those platforms as well.

What types of personal data do you process, where is it hosted, who is it shared with, and how long is it retained?

Information about the data that we process and the measures we take to protect it can be found in our Data Processing Addendum. Security measures specifically are outlined in Attachment 2 to the Addendum. You can also read our entire Terms of Service, where GDPR and a link to our DPA are available in section 6.3.

Should we be updating the fine print when we capture emails that include any information about how their data is being stored in Klaviyo?

Yes, your fine print should be updated to reflect the following guidance for EU prospects and customers:

  • Use clear, plain language that is easy to understand
  • Specify why you want the data and what you’re going to do with it
  • Name your organization and any third party processors you will be using
  • Tell individuals they can withdraw their consent

Do I need to provide opt-in emails in the local language to comply with GDPR?

Not necessarily, but Klaviyo provides local translations of GDPR compliant opt-in language in several languages.

Am I required to get consent on all my personal data from consumers?

Your only option to have a lawful basis for collecting or processing sensitive data is explicit consent. For other personal data, there may be several options when it comes to establishing a lawful basis, but consent is the most likely lawful basis.

Other lawful bases include

  • You are contractually required to process their personal data to fulfill the terms of a contract
  • You are required by law to process their personal data
  • You need to process someone’s personal data to save/protect their life
  • You need to process someone’s personal data to fulfill your responsibilities as a public official

There are other, more obscure lawful bases, but these are edge cases. Most businesses will need to have consent from the consumer in order to collect and process their data.

Can you anonymize my data so that I can view a profile but not see the personally identifiable information?

We do not currently allow customers to anonymize a profile, but anonymized data associated with that profile will remain in the account (i.e. Placed Order events, etc.) to preserve the accuracy of performance metrics. Data can be anonymized when extracted from the system, but within Klaviyo, you have full visibility to the data incorporated into any profile.

In that same vein, it is possible to delete contacts with a record of deletion to prove compliance, as well as export all the data on a given profile if requested by any of your contacts. 

Is an Abandoned Cart email GDPR compliant?

The answer to this one is not entirely clear, however, there is a prevailing view in the industry that you can still send abandoned cart emails under basis of legitimate interest. You can consider an abandoned cart email a communication relevant to the explicit intent to complete a transaction with your business.

That said, you need to be able to defend the notion of legitimate interest in order to use it as a lawful basis — and if you’ve sent someone 100 emails about an item they added to their cart 30 days ago, your abandoned cart series is indefensible. We strongly recommend you stick with an abandoned cart series of no more than 2-3 emails.

Other triggered emails, like browse abandonment and winbacks, on the other hand, are not GDPR compliant unless you restrict them solely to customers who have previously consented to receive marketing emails from you in a GDPR compliant fashion.

Was this article helpful?
12 out of 12 found this helpful