The General Data Protection Regulation 2016/679 was adopted by the EU on 14 April 2016 with an implementation date of 25 May 2018 giving site operators, governments, businesses et al well over two years to work on achieving compliance.
https://www.eugdpr.org
In my personal anecdotal experience, the May implementation date came and went, preceded by a flurry of smartphone app updates and some new terms & conditions popup windows on various websites.
Clau, namprikmakaam and the dozens of others who have inquired about GDPR compliance deserve more transparency than the noncommittal corpspeak boilerplate response that Lindsay-Jean cuts and pastes each time 2-3 days after this topic is brought up.
And don’t say “We don’t know” because there are actual answers.
There are people at Food52 who know real answers including every C-level officer (Food52 has a bunch) as well as every single Vice President, plus the entire engineering and product staff. You people have weekly senior staff meetings. The GDPR is not something that came out of nowhere.
Even mainstream media bombarded their readers with articles this spring about the impending date:
https://www.wired.com/story/europes-new-privacy-law-will-change-the-web-and-more/ (March 19)
https://www.cnbc.com/2018/03/30/gdpr-everything-you-need-to-know.html (March 30)
https://www.nytimes.com/2018/05/06/technology/gdpr-european-privacy-law.html (May 5)
plus a bunch of articles on the implementation date of 25 May 2018.
Questions:
1a.) Is this Food52 blockage for the EU temporary or permanent?
1b.) If this is not permanent when will Food52 be compliant with GDPR 2016/679? Most other sites/businesses/governments were able to correctly estimate the amount of work needed to accomplish this by the implementation date and started their efforts with ample lead time to prevent a service outage.
2a.) When did Food52 start work on GDPR compliance?
2b.) When was it clear that Food52’s GDPR compliance would not be reached by the 25 May 2018 implementation date?
3a.) How much work has Food52 done since the 25 May 2018 implementation date? (Percentage, man-hours, whatever, please provide a number.)
3b.) Food52 has been out of GDPR compliance three months past the 25 May 2018 implementation date. Are you increasing the amount of resources to rectify the issue?
4a.) Is Food52 aware that the California Consumer Privacy Act of 2018 is modeled after the EU GDPR?
4b.) Is Food52 aware of the implementation date of the California Consumer Privacy Act of 2018?
4c.) Is Food52 aware that other states may have similar legislative proposals for the California Consumer Privacy Act of 2018?
VP of Engineering Jim Bishop would be the person at Food52 most likely to know all of these answers without looking them up.
Is anyone at Food52 up to the task of providing some real answers and transparency to folks like Clau and namprikmakaam?
Note that the most questions posed above can be answered with a Yes, No, number or date.
Also due to the impending implementation of the California Consumer Privacy Act of 2018, this isn’t an issue that can be ignored. Denial is not an option.
American Food52 readers will be particularly interested in the answers for the questions posed in section 4.
I spent last month at home in the U.K. and France and was still unable to access food52 despite still receiving multiple emails with tempting recipes and beautiful items from your shop. Back in Asia where I currently live, no problem, but I have to ask - when does temporary become permanent? It is very frustrating for your U.K. readers, many of whom have already moved on to other websites. I appreciate that the new regulations may have made things difficult, but most people affected are simply hearing one thing: you’re not worth the effort to us. I know I am hesitant to continue to shop on this site in future.
Hi Clau, we're sorry you’re not able to access the site at this time, but this is a temporary measure to ensure we can best protect your data under new privacy regulations. We value your support; thanks for your patience and we can't wait to have you back!
4 Comments
Voted the Best Reply!
https://www.eugdpr.org
In my personal anecdotal experience, the May implementation date came and went, preceded by a flurry of smartphone app updates and some new terms & conditions popup windows on various websites.
Clau, namprikmakaam and the dozens of others who have inquired about GDPR compliance deserve more transparency than the noncommittal corpspeak boilerplate response that Lindsay-Jean cuts and pastes each time 2-3 days after this topic is brought up.
And don’t say “We don’t know” because there are actual answers.
There are people at Food52 who know real answers including every C-level officer (Food52 has a bunch) as well as every single Vice President, plus the entire engineering and product staff. You people have weekly senior staff meetings. The GDPR is not something that came out of nowhere.
Even mainstream media bombarded their readers with articles this spring about the impending date:
https://www.wired.com/story/europes-new-privacy-law-will-change-the-web-and-more/ (March 19)
https://www.cnbc.com/2018/03/30/gdpr-everything-you-need-to-know.html (March 30)
https://www.nytimes.com/2018/05/06/technology/gdpr-european-privacy-law.html (May 5)
plus a bunch of articles on the implementation date of 25 May 2018.
Questions:
1a.) Is this Food52 blockage for the EU temporary or permanent?
1b.) If this is not permanent when will Food52 be compliant with GDPR 2016/679? Most other sites/businesses/governments were able to correctly estimate the amount of work needed to accomplish this by the implementation date and started their efforts with ample lead time to prevent a service outage.
2a.) When did Food52 start work on GDPR compliance?
2b.) When was it clear that Food52’s GDPR compliance would not be reached by the 25 May 2018 implementation date?
3a.) How much work has Food52 done since the 25 May 2018 implementation date? (Percentage, man-hours, whatever, please provide a number.)
3b.) Food52 has been out of GDPR compliance three months past the 25 May 2018 implementation date. Are you increasing the amount of resources to rectify the issue?
4a.) Is Food52 aware that the California Consumer Privacy Act of 2018 is modeled after the EU GDPR?
4b.) Is Food52 aware of the implementation date of the California Consumer Privacy Act of 2018?
4c.) Is Food52 aware that other states may have similar legislative proposals for the California Consumer Privacy Act of 2018?
VP of Engineering Jim Bishop would be the person at Food52 most likely to know all of these answers without looking them up.
Is anyone at Food52 up to the task of providing some real answers and transparency to folks like Clau and namprikmakaam?
Also due to the impending implementation of the California Consumer Privacy Act of 2018, this isn’t an issue that can be ignored. Denial is not an option.
American Food52 readers will be particularly interested in the answers for the questions posed in section 4.
Please advise.
Thank you.