How Beamer is Complying with GDPR

6997
Mariano Rodríguez
May 23, 2018 | Last Updated Aug 17, 2021

At Beamer we value your privacy and your users’ privacy. We want to be clear about the data we collect, how we use it and your rights to control that information, which is why we’ve made some updates to our Privacy Policy.

We’ve made these updates to reflect the high standards established by the General Data Protection Regulation (GDPR). On 4 June 2021, the Commission issued modernized standard contractual clauses under the GDPR for data transfers from controllers or processors in the EU/EEA (or otherwise subject to the GDPR) to controllers or processors established outside the EU/EEA (and not subject to the GDPR).

We are in the process of updating our standard contractual clauses to reflect this and expect to have them implemented by the deadlines set out by the European Commission. Namely, Sept. 27, 2021 for new customers and Dec. 27, 2022 for all existing contracts.

Here’s a quick summary of the important updates to our Privacy Policy done initially to comply with GDPR when it was announced:

  • Clarification on what personal data we collect and its purpose
  • Third parties we share personal data with
  • Addition of a cookie notice to all marketing pages and blogs

We have also added the user’s right to be forgotten/have data erased. You can access any users data and/or delete this information using this link: https://app.getbeamer.com/privacy

Data Processing Agreement

In order to be GDPR compliant our customers should download our Data Processing Agreement  and Standard Contractual Clauses (SCC to be updated soon with the modernized version) from the link below and return a signed copy to legal@getbeamer.com. We also suggest that you add the proposed language below to your privacy policy:

Please review our updated Privacy Policy here: https://www.getbeamer.com/privacy-policy/

GDPR refresher: what is my role?

We know that GDPR can be a little overwhelming. With all the custom jargon like controller, processor, sub-processor, etc. it can a bit confusing to keep clear who all the players are and what your particular role is. That’s why we created this simple graphic image that illustrates how the different roles are related within the context of GDPR so you can find out what your specific responsibility is in different situations. Hope it helps 🙂

GDPR roles including controller, processor and sub-processors and how they work