Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Privacy Manifest #115

Open
lambda123254 opened this issue Dec 25, 2023 · 1 comment
Open

Privacy Manifest #115

lambda123254 opened this issue Dec 25, 2023 · 1 comment

Comments

@lambda123254
Copy link

With the recent updates announced at WWDC 2023 (https://developer.apple.com/videos/play/wwdc2023/10060/), Apple has emphasized the importance to add Privacy Manifest to the developers. Can you please share details about the Privacy Manifest for this library? It'd be awesome if you could add a Privacy Manifest to this library.

@JohnEstropia
Copy link
Collaborator

The Privacy Manifest is something that app publishers should audit for in all their dependencies. This is not the responsibility of library authors. I can think of the several reasons this is the case:

  • Apps most of the time use only a subset of the library's full functionality. If you use Firebase Crashlytics for example, you don't want to inherit "Tracking" from the Google frameworks if all you need is "Diagnostics".

  • Open Source owners might not update their manifest regularly. At best, you'd just have to wait for them to update it. At worse, they rush it with inaccurate declarations.

  • Open Source repos are forked all the time. Repos containing privacy manifests do not tell us if extended functionality still respects the manifest file of the original.

  • Most Open Source licenses already contain a variation of "use at your own risk" wording, and basically waives the responsibility away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants