iOS Location Services Clarifications #2626
Merged
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.
Changes proposed in this PR:
Added a new section that guides users to Location Services -> System Services, allowing them to customize which system services they want to have location enabled for if they choose to leave it on.
Additionally, clarified that users can also scroll down and stop location analytics data from being sent to Apple to be used to improve Apple Maps, which was not previously included in the privacy recommendations
Added additional information about Location Services which was not there previously, which is below:
Clarified that a purple arrow indicates an item has used location recently, while a grey arrow indicates an item has used location within the last 24 hours
Also added that App Tracking is disabled for Apple users under the age of 18
Contribution terms (click to expand)
1) I am the sole author of this work. 2) I agree to grant Privacy Guides a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable license with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform, relicense, and distribute my contribution as part of this project. 3) I have disclosed any relevant conflicts of interest in my post. 4) I agree to the Community Code of Conduct.