2 ms·
It costs to comply with GDPR even if you are doing no tracking. 1. If GDPR applies to you and you are not in the Union you must have a designated representing
by tzs 4y ago
It costs to comply with GDPR even if you are doing no tracking.
1. If GDPR applies to you and you are not in the Union you must have a designated representing in the Union to receive GPDR requests (both from individuals wishing to exercise their GDPR rights and from regulators). So right off the bat you have to engage some service in the Union to handle that for you. There are such services that aren't very expensive, but it is something you have to deal with.
2. IP addresses are personal data according to many GDPR experts. Normal logging that is done by most web servers leaves you with a GDPR burden to deal with. It seems likely that storing this would be allowed without the need to obtain explicit consent because there is a legitimate business interest to that logging, but you still have to deal with requests from people to delete their data. So more hassle.
3. You will have to keep up with developments as regulators rule on the meaning if the tons of subjecting things in GDPR.
If you are not in the Union but people who are in the Union use your site GDPR applies if either you are:
A. offering goods or services to them (free or paid), or
B. monitoring their behavior as far as their behavior takes place in the Union.
For A you have to envisage offering goods or services to them. The mere fact that they can reach your site and use it is not sufficient.
If you aren't monitoring behavior in a way that makes B apply, then whether or not GDPR applies comes down to whether or not you envisaged offering goods and services to people in the Union. That's a fairly subjective thing and I don't think there have been enough cases involving that yet for it to be clear just what that means.
Blocking EU visitors makes it clear you did not envisage serving them saving you all the aforementioned hassles and annoyances.
- Dylan16807 4y agoIf IP address logging is enough to count as monitoring, then sending a block page doesn't fix the problem. If you're confident enough that you have a non-tracking response to EU citizens, then you already did the hard part, and you might as well dump the article contents into that response.
- Scoundreller 4y agoSeems like a business opportunity: a load balancing rule that sends EU requests to your log-free tracker-stripping static file-generating server appliance (possibly EU hosted) which has google Adsense on it and a GDPR responder that responds to every GDPR request specifying all that.
- tzs 4y agoLogging IP addresses looks like it counts as storing personal data of the visitor, but it isn't at all clear that it counts as "monitoring of their behavior as far as their behavior takes place within the Union" which is what monitoring has to do for that to be a bases for GDPR to apply. There's a recital (Recital 24) that elaborates on that part of GDPR. From that: > In order to determine whether a processing activity can be considered to monitor the behaviour of data subjects, it should be ascertained whether natural persons are tracked on the internet including potential subsequent use of personal data processing techniques which consist of profiling a natural person, particularly in order to take decisions concerning her or him or for analysing or predicting her or his personal preferences, behaviours and attitudes. A simple IP based location block doesn't seem like it really fits that, and so wouldn't snare you via the "monitoring of their behavior as far as their behavior takes place within the Union" part of the GDPR's territorial scope article (Article 3 section 2(b)). If that's the case, then whether or not GDPR applies comes down to whether or not you envisaged offering goods and services to people in the Union (Article 3 section 2(a) and Recital 23). Blocking would be intended to show that you did not envisage doing so. That gets you out of needing to have a representative in the Union and needing to deal with data deletion requests.
- erik_seaberg 4y agoThe hard part isn’t not tracking, it’s convincing hostile regulators that you are in fact not tracking. Sometimes they want 8–14 week delays before launching features: https://gdpr-info.eu/art-36-gdpr/ https://gdpr-info.eu/art-36-gdpr/