TOTAL: {[ getCartTotalCost() | currencyFilter ]} Update cart for total shopping_basket Checkout

""

""

The votes are in: The winning entry for the S*fe H*arbor Naming Contest is ... The Transatlantic Data Protection Framework (TDPF), submitted by Galaad Delval. 

The TDPF beat out the other four finalists pretty handily, picking up 34 percent of the nearly 1,000 total votes. The first runner-up was The EU-U.S. Data Exchange, submitted by Robert Niedermeier. The second runner-up was the North Atlantic Privacy Agreement, submitted by Christophe Hug. 

As promised, the winning entry will now be officially endorsed by the IAPP as the new name for the to-be-finished data-transfer agreement between the EU and the United States, currently being hammered out between the EU Commission and the U.S. Department of Commerce. Here are the letters as proof:

letter1 letter2

And from now on, that's what we're going to call it. No more "Safe Harbor 2.0" nonsense. From now on, full steam ahead with the Transatlantic Data Protection Framework. Unless they ignore us and call it something else. We'll see what happens.

Also, you're probably wondering who Galaad, our winner, happens to be. 

Turns out, he's currently living in Shanghai, China, where he works with the EY Chen & Co. law firm. He is a European citizen, who studied law in France and now wants to make privacy and data protection his profession. Galaad reports that he is currently studying for the CIPP/E and that, "As both the GDPR and the Safe Harbour 2.0 (or maybe one day the Transatlantic Data Protection Framework) will define our right to privacy and the limit on this right, I thought it to be a duty as a European citizen and a legal expert to research these matters to protect both individuals and companies against others and themselves."

Please join us in extending a hearty congratulations to Galaad, as well as wishing him good luck with his CIPP/E exam. And thanks to everyone who participated in the renaming contest. Hopefully, you enjoyed it as much as we did. 

Comments

If you want to comment on this post, you need to login.