You’re probably right in terms of how the back end data collection is structured. However, you can also set up your site to limit functionality when people are in the European Economic Area covered by GDPR. You can flag the data and users at the point of protection in accessing the app to identify if the user (as a whole) and/or certain data collection activity was protected by GDPR.
Any data collected when on US soil is not GDPR protected. It only protects data gathered while in the covered European economic Area. So even if we American Citizens or Residents ask for our data to be destroyed or returned to us as GDPR protects, the companies are not required to do so - even if they can do so- if the data was submitted from here in America because the data wasn’t protected by GDPR.
Certain TT functionality isn’t available in the EEA because of GDPR protections; that is where most companies ensure compliance - at the point of collection.
My company tracks it on an individual flag (e.g. did the patient or applicant set up their data account with us while in the EEA or was it when on US soil?) as well as functionality basis (if you are in the EEA you can’t enter certain info without reading and signing off a million disclaimers that we may not be able to return or destroy the records if US law supersedes the requirement to retain it).
If we get a bunch of requests invoking the GDPR privileges we may find ourselves in a manual record management quagmire but so far very few individuals have asked.
This is how my global company handles EU data in big applications. The EU customers are “fenced off”, meaning North America or Asia Pacific employees can’t look them up. They also minimized the number of data fields that appear in the EU application to fit the GDPR philosophy of only collecting essential data for conducting necessary business processes. But in other regions, you can use all the fields.
China passed its own law in 2021 and we will likely have to fence off their customer data in a separate cloud as well. They seem to be wary of information about Chinese citizens being stored in non-Chinese located databases or for people outside China being able to access it.
I have to say that people in other countries like Europe/ China are much more privacy conscious. Particularly anywhere that has experience within ~100 years of fascist or totalitarian governments. Americans are mostly concerned about health information and identity theft but are quite happy to hand over all kinds of other information to marketers. I think we need to be much more skeptical of the entire social media landscape, not just Tictok.
I can't speak to what we gather on the patient side for Marketing purposes, but from the applicant side (for careers), in order to comply with our federal contractor requirements, we have to ask a lot of demographic questions (which are voluntary for applicants) to analyze how effective we are at reaching our affirmative action goals. If you aren't willing to acknowledge that we may not be able to destroy those records as quickly as you require (because of our legal reporting purposes), we can't even let you complete an employment application. If you ARE willing to move forward, then we mark the data as GDPR-protected so in the event you ask for it to be deleted, we can determine what we can delete according to our document retention schedule for compliance purposes.
For AAP data, that is generally 3 years. So if your data is marked as GDPR-protected AND you ask for it to be deleted after the period beyond which we are required to retain it, then we will. If not, we'll let you know the earliest we can delete it and we put it in a queue. Obviously GDPR hasn't been in place for long enough to match both of those requirements, so we have a queue - it is fewer than 10 people and we get hundreds of thousands of applications a year.
We don't get a lot of applications from people in the European Economic Area. But we get a LOT of Chinese applications, especially for our research institute. I wasn't aware that China passed a similar law so I'll touch base with Legal on whether they have started assessing our systems for compliance with that. Since we aren't physically doing business in other countries, a lot of our requirements are lower than multinational companies, so it may be a nonissue for us. GDPR was extensive in its scope and impact if violated.
As we continue to invest in analyzing our patient data for equity in access and receipt of care, we also increase the demographic data we ask patients to submit - also voluntarily. It's not all nefarious in intent. But it is definitely sensitive and requires handling accordingly!
Michelle I thought I saw a stat that 80% of U.S. companies are GDPR compliant, but now I’m seeing the opposite stat so maybe I goofed on that one.
So I’ll only speak to my company; we’re totally GDPR compliant.
PDQ
(cut)
Gotcha (on what's above).
That makes sense (what i cut out). We have similar end-user access restrictions on top of data warehousing restrictions.
Related - at my company, you only have access to what you need to do your job. No more. Sometimes less as a result of trying to protect the data, and it can make doing your job frustratingly slow - you have to request the data from others. But it makes business practice compliance easier.
Interesting summary of the bill - apparently goes beyond only banning TikTok to infringing on privacy and possibly messing with mass comms. While I could care less about TikTok, some of what is outlined here really worries me.
Interesting summary of the bill - apparently goes beyond only banning TikTok to infringing on privacy and possibly messing with mass comms. While I could care less about TikTok, some of what is outlined here really worries me.
Yup, this was never really about Tik Tok. Tik Tok was just a convenient tool because they could use whip up people's anti-Asian hate and fear of CCP for cover. They were hoping people wouldn't see past that to look deeper at their real agenda. Its GOP playbook 101.
share.memebox.com/x/uKhKaZmemebox referal code for 20% off! DD1 "J" born 3/2003 DD2 "G" born 4/2011 DS is here! "H" born 2/2014 m/c#3 1-13-13 @ 9 weeks m/c#2 11-11-12 @ 5w2d I am an extended breastfeeding, cloth diapering, baby wearing, pro marriage equality, birth control lovin', Catholic mama.
Interesting summary of the bill - apparently goes beyond only banning TikTok to infringing on privacy and possibly messing with mass comms. While I could care less about TikTok, some of what is outlined here really worries me.
Yup, this was never really about Tik Tok. Tik Tok was just a convenient tool because they could use whip up people's anti-Asian hate and fear of CCP for cover. They were hoping people wouldn't see past that to look deeper at their real agenda. Its GOP playbook 101.
Is there a path to separating what the GOP is doing vs what tech security experts are saying?
Post by bugandbibs on Mar 31, 2023 12:54:04 GMT -5
pixy0stix, I think it starts with universal rules/guidelines/restrictions that aren't based on country of origin. i.e., these are the things that you are not allowed to do with personal data or tracking, etc... Much like our judicial system, the concept of innocent until guilty, we need to have a burden of proof beyond "they could do this". I am really uncomfortable with banning things by country of origin and use of VPNs.
General consumer protection is where it starts for me. We can't hold our "enemies" to standards that we don't follow ourselves just because "we" don't benefit from the information they gather.
share.memebox.com/x/uKhKaZmemebox referal code for 20% off! DD1 "J" born 3/2003 DD2 "G" born 4/2011 DS is here! "H" born 2/2014 m/c#3 1-13-13 @ 9 weeks m/c#2 11-11-12 @ 5w2d I am an extended breastfeeding, cloth diapering, baby wearing, pro marriage equality, birth control lovin', Catholic mama.
Tiktok combating misinformation is completely false. Like any social media platform, it's riddled with misinformation. It's especially bad for health information.