1. We are incorporated in the UK. I could be wrong but I think the European Commission did indicate that the UK was an Adequate Country?
https://commission.europa.eu/law/law-topic/data-protection/i...
2. For the details that our privacy policy lacks, I think they can be found in our Data Policy. Any further issues, please let us know.
3. On the Data Protection Officer, I think one is only needed if sensitive data on a large scale is processed.
https://commission.europa.eu/law/law-topic/data-protection/r...
The definition of sensitive data can be found on this EU site and Beam does not process any of this type of data.
https://commission.europa.eu/law/law-topic/data-protection/r...
2. Your subprocessor uses AWS. No way to stay compliant if you transmit visitor IP to US cloud (even if they use European servers).
3. Sadly, wrong. You should immediately consult privacy professional. DPO is necessary. There are 3 tests.
https://ico.org.uk/for-organisations/does-my-organisation-ne...
Answer to question 2 is yes btw.
You are not compliant without DPO and because you are using AWS, even if indirectly.
In theory Amazon could license their brand and software to an independent (!) European company to offer a EU-AWS.
Basically if an American judge/agency can order Amazon to hand over European private data and they have the ability to comply without involving a European court the service is not GDPR compliment.
Now in practice this isn't how things are done but to the best of my knowledge the law hasn't changed (yet) and national dpas are starting to tighten the screws (slowly).
If I recall correctly there are EU-US talks to create Privacy Shield #3.
There was a case of Doctolib in the EU. French authority investigated Doctlib for using AWS.
They got off the hook because data was encrypted in the EU, outside of AWS and the encryption keys were inaccessible to AWS.
Similarly Sendinblue uses GCP and AWS as dumb storage of externally encrypted backups.
There are valid use cases. But these are very limited.
1. Glad we're in agreement!
2. We agree it is not GDPR compliant to transmit IP address data to the US. This is why we salt and hash all PII data so no IP address data is sent to the US. Please see our data policy.
3. Thank you for your suggestion. We have already consulted privacy professionals and have been assured no DPO is required.
Thank you for this conversation about GDPR. We appreciate your interest in Beam's work.
Can you share more detail on this? On this page[1], I see this:
hash(pepper(salt(ip address + user agent data))) = anonymized hashed data
Both the ipv4 space and typical user agent possibilities are pretty small, so it feels like you could easily de-anonymize it when you want to. That is, assuming the "salt" and "pepper" are stored somewhere. I assume you do store them, otherwise it's not helpful to identify repeat visits."its core activities involve processing of sensitive data on a large scale ---> OR <--- involve large scale, regular and systematic monitoring of individuals"
Any analytics provider is fundamentally doing "large scale, regular and systematic monitoring of individuals".
Quoting from WP 243 Annex provided by the EU:
"The notion of regular and systematic monitoring of data subjects is not defined in the GDPR, but clearly includes all forms of tracking and profiling on the internet, including for the purposes of behavioural advertising. However, the notion of monitoring is not restricted to the online environment."
The link is here
https://ec.europa.eu/information_society/newsroom/image/docu...
We anonymize and aggregate all data so can't track or profile any users, or do such monitoring offline.
I built this to track my own sites but I am curious if anyone else cares. I created a landing page to see if there’s any interest.
The product is working on a few sites of my own and is hosted on a raspberry pi in my home office. I’d need to do some work to make it available for others, but I don’t want to invest more into it unless there’s any interest.
Every so often I see something like this:
https://www.mayerbrown.com/en/perspectives-events/publicatio...
I suspect the UK is planning a number of changes that may change this, so even though I'm British, for the avoidance of doubt I prefer companies actually hosted in the EU and that will agree to conduct business in Europe (and thus under EU courts, rather than GB ones).
> 3. On the Data Protection Officer, I think one is only needed if sensitive data on a large scale is processed.
You are totally incorrect about that.
https://ico.org.uk/for-organisations/guide-to-data-protectio...
1. The GDPR is regulation from the European Union
2. PIPEDA has an Exemption order for BC (British Columbia, Canada) and applies "in respect of the collection, use and disclosure of personal information that occurs within the Province of British Columbia".
Firstly, the Exemption order states "Whereas the Governor in Council is satisfied that the Personal Information Protection Act, S.B.C. 2003, c. 63, of the Province of British Columbia, which is substantially similar to Part 1 of the Personal Information Protection and Electronic Documents Act, applies to the organizations described in the annexed Order;"
Secondly, which part of BC's Personal Information Protection Act would undermine it's adequacy ruling under the GDPR?
Finally, let's get into Fathom's pageview/event collection script and explain how it works:
1. There is no collection, use and disclosure of personal information that occurs within the Province of British Columbia
2. EU traffic is automatically routed via EU Isolation and processed on German-owned servers. This allows us to stop US government snooping on EU traffic
3. Fathom Analytics is incorporated in BC. But nobody in BC has access to our EU Isolation infrastructure. I'm the CTO of Fathom Analytics and I have access to our EU Isolation infrastructure. I'm not in BC. Additional access to EU Isolation is from Germany only. Heck, not even GitHub Actions has access to EU Isolation, we self-host GitLab to keep things completely isolated. We put a lot of time and effort into this.
I'll wait back to hear back from you on which parts of the BC's PIPA undermine the adequacy ruling. Our lawyer here in Canada is incredibly well versed in Canadian privacy law, so we can definitely loop her in if there's any confusion here.
I hope that addresses your point and helps inform other people who may be reading this.
> To date, Alberta, British Columbia, and Quebec have privacy legislation that takes commercial activities in those provinces out of the federal jurisdiction through the "substantial similarity" exemption to PIPEDA. Federal privacy law defers to provincial law if a province meets the substantial similarity test, providing a baseline of privacy regulation across Canada. This division of authority is important, because for provinces recognized as substantially similar, their laws have not been given the stamp of "adequacy."
I might have framed my statement too strongly. Fathom can be GDPR compliant assuming additional contractual clauses are in place. That is what is mentioned in the linked IAPP assessment.
> 3. Fathom Analytics is incorporated in BC. But nobody in BC has access to our EU Isolation infrastructure. I'm the CTO of Fathom Analytics and I have access to our EU Isolation infrastructure. I'm not in BC. Additional access to EU Isolation is from Germany only. Heck, not even GitHub Actions has access to EU Isolation, we self-host GitLab to keep things completely isolated. We put a lot of time and effort into this.
The same could be said about Amazon, Google, and Azure employees and their data centre employees in Europe. What matters is effective control. You are not in BC but the company, and your position and responsibilities are governed by the laws of the province of British Columbia.
Although, in the case of Canada, SCCs will be actually effective as there are no surveillance laws similar to the US.
So my question to you is: Which part of the Personal Information Protection Act in BC would undermine the EU's adequacy decision towards BC? The reason I'm pushing on this question is because the "stamp" occurs for a reason. Please let me know where the PIPA would lead to the European Commission labelling BC as inadequate.
2. We're mixing things up here with Amazon, Google and Azure. Those companies are subject to FISA 702[1] and EO12333[2]. We are not subject to these surveillance laws here in Canada. I've spoken at length about this before, about how the US government could compel one of these companies to secretly spy on people using their EU infrastructure. So our company is not in the same position.
I'll wait for your specifics around the PIPA.
[1] https://en.wikipedia.org/wiki/Foreign_Intelligence_Surveilla... [2] https://en.wikipedia.org/wiki/Executive_Order_12333
RE: 1
I am looking at this document: https://www.bclaws.gov.bc.ca/civix/document/id/complete/stat...
I assume this is up-to-date.
I will take one example: the Right to be forgotten. I don't see provision that satisfies the right to be forgotten: https://gdpr.eu/right-to-be-forgotten/
You seem to have a more in-depth understanding of PIPA. Can you point me towards a similar requirement in PIPA?
RE 2:
Right, I was referring to the fact that customers of Fathom sign contract/get into agreement with a company in British Columbia under its laws. It is mostly irrelevant where their CTO resides (it would be relevant if you resided in a non-adequate country, as your privacy policy would have to account for relevant data transfers).
The background of Schrems II was that the US government can compel US companies to track foreign nationals and it would be lawful under US law. This is where the argument of "company in X under Y laws" comes into play. For example, Amazon is a US company. An EU subsidiary is still subject to it's parents control. If that parent is a US company, it's subject to US surveillance laws. Hello Schrems II.
So I'm not fully following why we're having a discussion around processing happening in Canada when personal data (IP Address) hits our EU Isolation infrastructure.
If you have any sources you can cite where the European Commission states BC as an exemption to Canada's adequacy ruling, please throw it back to me. I've not seen that.
GDPR compliance is not to be confused with privacy.
You don't have Data Protection Officer (even if you have one, you ought to publish their details). Neither does Plausible.
Your privacy policy lacks details, e.g.: where you process data and what is data retention.
You are incorporated in not an Adequate Country, meaning you face challenges becoming GDPR-compliant without additional measures that span beyond SCCs. Similarly to Fathom (BC is not under PIPEDA, hence is not adequate).
Privacy-friendly? Probably. GDPR-compliant? No.