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

The Privacy Advisor | We Can Do Better Than "Safe Harbor 2.0" Related reading: All the Safe Harbor Answers: Part 1

rss_feed

""

While the U.S. Department of Commerce and the European Commission haggle through the next iteration of an agreement that would provide a mechanism for companies to transfer European citizen data to the U.S., there's one thing we can all agree on: The "Safe Harbor" name carries way too much baggage. 

Even worse, it has engendered a multitude of nautical puns (Safe Harbor is sunk!) and visual metaphors (Look, a lighthouse!) that all of us could really do without. We need something to engender new bad puns and visual metaphors, right?

Thus, we at the IAPP have decided to create a simple and straightforward naming contest. First round: You suggest a better name. Second round: You vote on your favorite of the top five names submitted. Third round: A winner is crowned and we send an official recommendation, backed by the full might and strength of the IAPP (such as it is), to both sides of the Atlantic that the name be adopted. 

To be clear: By submitting your entry you agree to have your name associated with the winning title as it will be submitted to the U.S. Department of Commerce and the European Commission as a suggested new name for the next iteration of Safe Harbor (we're optimists; it will happen). The letter will also be posted on IAPP channels. Information submitted will only be used for the purpose of the Safe Harbor naming contest and to contact the winner. Please be aware that although we are submitting this suggested name for adoption, it does not in any way guarantee the name will be used. This is simply a suggestion.

However, when you hear an EU commissioner refer to Safe Harbor from the keynote stage as "the S word," you can be assured they're on the hunt for something better.

You want in? Game for a little privacy fun? Submit your idea here:

https://www.questionpro.co/t/ACtQeZTGFh

Comments

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