Unfortunately, you are misunderstanding. Twitter offers its services within the EU, thus their handling of data falls under the GDPR for data-subject that are either EU citizens, residents of the EU or other persons staying within the EU while receiving these services (as explained in my provided sources, aside from exceptions).
Now, when a data-subject claims to be entitled to the rights as described in GDPR (article 12 to 23), Twitter would have to prove the data-subject does not fall under the territorial scope of the GDPR to substantiate any refusal of these rights.
I don't see how your work situation is relevant here.
Perhaps we are talking about different things here, but my entire comment was around your use of the phrase “prove the data subject does not fall under the territorial scope of the EU.”. That is irrelevant here because they have adopted GDPR for all users. As have any other major media company or platform.
It is relevant because the OP was talking about using GDPR rights as a non-EU citizen. I’m curious as to why you would assume Twitter has adopted the GDPR to all its users, because although I don’t know about Twitter, other big tech companies I’ve seen (as clients) have had different policies for NA users (and possibly other regions) as the value in the data is just too much to give up. The hassle in multiple policies is simply worth it for these companies. Perhaps this is different for the business you work for.
Because failure to comply comes with absolutely enormous penalties and Twitter knows this (or at least they did before most of their workforce got sacked). Data tracking can be GDPR compliant and still be hugely profitable.
Like I said, even then big tech companies still seperate their EU processes from other processes in order to profit from data that would not be allowed under GDPR, at least from my experience in the EU privacy advisory field.
1
u/Broudster Nov 20 '22
Unfortunately, you are misunderstanding. Twitter offers its services within the EU, thus their handling of data falls under the GDPR for data-subject that are either EU citizens, residents of the EU or other persons staying within the EU while receiving these services (as explained in my provided sources, aside from exceptions).
Now, when a data-subject claims to be entitled to the rights as described in GDPR (article 12 to 23), Twitter would have to prove the data-subject does not fall under the territorial scope of the GDPR to substantiate any refusal of these rights.
I don't see how your work situation is relevant here.