Spring 2022 updates to Privacy Statement #561
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
In this pull request we’re proposing changes to our Privacy Statement to help make our policies clearer and easier to understand. Here are the key updates: - Refreshed language to clarify our privacy practices and reflect requirements of new and updated privacy laws. These changes are not meant to change or narrow any of our previous privacy commitments. For example, in order to reduce redundancies and focus on personal data as a general term, we removed references to User Personal Information. - You now have more granular control over display of your data in connection with Community Features. You can check out the new private profile setting under “Contributions & Activity” here. - You can now find our California Privacy Notice by simply scrolling to the end of the Privacy Statement. Note that while you may see a lot of green (new) content in the diff, in some cases, this is because we’ve moved content around to convey our privacy practices in a simpler way. It doesn’t necessarily mean that we’ve changed the language. For example, we included a new section “Who is responsible for the processing of your information?” that contains some information from the “Organizations” section of our previous version. These updates will go into effect after the 30-day notice and comment period, on May 28, 2022 at 3pm PT.
Ljoshua32
approved these changes
May 15, 2022
Danielluwis
approved these changes
May 15, 2022
olholder
approved these changes
May 24, 2022
samanthachau
approved these changes
May 26, 2022
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.
In this pull request we’re proposing changes to our Privacy Statement to help make our policies clearer and easier to understand.
Here are the key updates:
Note that while you may see a lot of green (new) content in the diff, in some cases, this is because we’ve moved content around to convey our privacy practices in a simpler way. It doesn’t necessarily mean that we’ve changed the language. For example, we included a new section “Who is responsible for the processing of your information?” that contains some information from the “Organizations” section of our previous version.
These updates will go into effect after the 30-day notice and comment period, on May 31, 2022 at 3pm PT.