[Setup] Add Privacy Manifest #296
Merged
Conversation
This file contains 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
zkline101
requested review from
a team and
des12437
and removed request for
a team
yo1995
previously approved these changes
Nov 9, 2023
There was a problem hiding this comment.
Based on a similar PR duckduckgo/iOS#1936 the format and the location where the manifest is added look good.
yo1995
approved these changes
Nov 9, 2023
des12437
approved these changes
Nov 9, 2023
|
Thanks! |
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.
Description
These are the things that need to be declared in the privacy manifest if we collect any of this info:
I only listed in the privacy manifest that we use course location for a qualified reason. I didn't see any other items we need to list, please confirm this as a part of reviewing this PR.
Here is the privacy report for the Samples:Samples-PrivacyReport 2023-11-08 15-52-45.pdfLinked Issue(s)
swift/issues/4177