Opens profile photo
Follow
pilcrow
@pilcrowonpaper
I like making stuff - Currently working on
Tokyo, Japanpilcrow.vercel.appJoined November 2017

pilcrow’s Tweets

After receiving tons of, uhhh... "feedback," I've updated the recent article on GDPR to present a more nuanced viewpoint and conclusion. Specifically, I have provided further elaboration on legitimate interests.
1
5
Show this thread
Uh... ok so it hit the front page of HackerNews and r/webdev. I'm kinda anxious with how much attention it's getting I have never felt so relieved reading a comment tho:
Image
Quote Tweet
I wrote my first blog! It's about GDPR and analytics, but it should be a good general introduction to EU privacy laws as well. pilcrow.vercel.app/blog/gdpr-anal
2
13
It's important to remember that each EU member may interpret laws differently. Notably, France's CNIL has allowed for non-essentials cookies to be used without consent under some conditions. However, this should only be applied to French users and it is not a EU wide decision.
1
1
Show this thread
Names and home addresses are obvious, but online identifiers, such as email addresses, IP addresses, and session ids, are included. Any data that is linked to a single user (or approximately so), whether it reveals any personal info or not, is considered personal data.
1
1
Show this thread
GDPR prohibits the processing (incl. storage) of personal data without a legal basis (e.g. consent). Personal data is a broad term that describes data that relates to an identified or identifiable user. The combination of non-personal data may be personal data as well.
1
1
Show this thread
EU laws make it remarkably difficult to count unique visitors, even in a privacy friendly way. To count visitors, you need to either: 1. Assign ids to users 2. Store data to the client Both options will likely result in a violation of GDPR and/or the ePrivacy Directive (EU+UK).
2
1
Show this thread
I do not feel comfortable advertising my analytics library as "GDPR compliant" when it's really "maybe GDPR compliant" I'm giving up on counting unique visitors from EU A 🧵 (last one on EU laws!)
2
10
Show this thread
I think I found an ingenious way to count daily unique visitors. GDPR compliant (likely - can't say for certain), no cookies, no localstorage, no fingerprinting, no IP addresses, no user agents.
5
14
Keep in mind that data may not be considered anonymized if it's stored alongside data that, in combination, could be used to identify the user. For example, storing the masked IP address with the user id (which connects to an account that stores IPs)
1
1
Show this thread
Cookieless analytics (like Plausible) counts unique visitors by creating a hash of the IP + user agent with a daily rotating salt. Even if the salt is deleted in 24 hours, I'm still not sure if that counts as anonymization.
1
1
Show this thread
As for hashing, it might still be considered pseudonymization. For IPv4, there's only 4 billion combinations, which means hashes can be brute-forced in a few seconds. Brute-forcing IPv6 is near impossible so hashing it might be fine but ehhhh.....
1
1
Show this thread
What's the difference? Pseudonymization is the process of making data "no longer be attributed to a specific data subject without the use of additional information." Encryption is one example as you can decrypt it if you have a key.
1
1
Show this thread
Correction - pseudonymised data are still considered personal data and require consent to be processed. I meant to say anonymized data, which does not have that requirement. IP masking (which I gave as an example) are considered anonymization, though it's still a grey area.
Quote Tweet
I spent the entire day researching GDPR and the ePrivacy Directive uuuhhgggg Anyway, here's what I found (NOT LEGAL ADVICE!)
Show this thread
1
3
Show this thread
A lot of things are still in the gray zone but your website should have a privacy policy if you handle personal data. Make sure you mention where the data is being processed as well.
1
Show this thread
Anything related to analytics and ads is not considered "strictly necessary." There isn't an EU wide consensus yet on exceptions but not using cookies at all for analytics is the safest bet.
2
Show this thread
You may skip getting a consent if it's reasonable from the user's perspective. For cookies, this means you can only store those that are deemed "strictly necessary" for the website to run, including auth and storing user preferences.
1
1
Show this thread
The most commonly known one being consent, but it also includes "legitimate basis," legal obligation, and vital interests of the user. Security related things (like IP logging) may fall under the last basis.
1
1
Show this thread
Any data that can be used to identify a user (actual person) is considered personal data. This includes names and IP addresses, but not email addresses. Alongside setting cookies, processing (includes storing) such data is prohibited unless you have a legitimate legal basis.
2
3
Show this thread
I thought about using IP addresses for counting unique visitors, but those are personal identifiable data, which is subject to much stricter rules. Hashing or encrypting it may not make it GDPR compliant as well.
3
Show this thread