> Here’s the issue: the law uses the term “data subject” but doesn’t define the term. Some may assume that data subjects are EU citizens, but that analysis seems to exclude the explicit language of the law and practical considerations. There’s tourism, travel, residencies, students abroad, and much more to consider. Because GDPR uses inconsistent qualifiers when referring to data subjects and informal descriptions of who a data subject is, the public has been left with varying interpretations and significant challenges. [1]
In some interpretations, a US citizen who is traveling in the EU and orders something from a US company would be considered a data subject, and the company they ordered from would need to comply with the GDPR.
So how would that be enforced? Either through treaties or by requiring non-EU companies to establish a representative entity in an EU member state. [2]
[1] https://kirkpatrickprice.com/blog/what-is-gdpr-personal-data...
Should everyone who runs a website open to the public have to know the laws of Iran and obey those intended to apply to their website? Should websites have to attempt to block access to visitors from countries whose laws they either don't know or don't want to comply with? Both of those approaches break the internet as we know it.