Update to Global Privacy Practices - Winter 2019 #156
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Mar 14, 2019
bluemazzoo
commented
Apr 12, 2019
Contributor
Author
|
Thank you all for your comments and feedback! As stated in our blog post, the comment period ends today. I am closing this pull request for internal review of any remaining comments. We will commit final clarifications or edits when we merge this pull request next Friday, April 19. At that time, the updated version of this policy will be effective. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update to the Global Privacy Practices policy includes a number of changes for compliance purposes and changes in law, including changes to the following sections:
removedU.S.–Swiss Safe Harbor Framework