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

Add Privacy Manifest #807

Closed
chrs1885 opened this issue Dec 1, 2023 · 8 comments · Fixed by #822
Closed

Add Privacy Manifest #807

chrs1885 opened this issue Dec 1, 2023 · 8 comments · Fixed by #822
Labels
enhancement triage Issues that need to be triaged

Comments

@chrs1885
Copy link

chrs1885 commented Dec 1, 2023

Is your feature request related to a problem you're having? Please describe.
We recently became aware that, according to the new Apple privacy regulations, third-party SDKs will also be required to provide a Privacy Manifest to ensure compliance with privacy policies in the future.

Describe the solution you'd like
Add a privacy manifest.

Describe alternatives you've considered

Additional context
Privacy Manifest

@chrs1885 chrs1885 added enhancement triage Issues that need to be triaged labels Dec 1, 2023
@AntonyARHS
Copy link

Hello,

Do you have any idea which key should be defined regarding AppAuth?

@mattgapadmi
Copy link

AppAuth is explicitly listed by Apple as needing a privacy manifest:
https://developer.apple.com/support/third-party-SDK-requirements/

Can you please let us know when one will be provided?

@fraserscottmorrison
Copy link

Apps that include your library will be rejected if this isn't provided. Would you be able to include it in your next release?

@tkhho
Copy link

tkhho commented Jan 24, 2024

I wanted to bring this topic to your attention once again. Since AppAuth is explicitly listed, this will pose a barrier for all iOS apps using the framework. Therefore, this topic is rather important. Are there any insights into whether and within what timeframe this will be implemented? It is also crucial for app developers to be able to make a feasible plan.

Thank you for your great work, and this is not intended to be a complaint. I am not pleased with the move Apple made here, leveraging all app developers to enforce changes in frameworks within a relatively short time.

@mdmathias
Copy link
Collaborator

Hi all. Thank you for the issue and the comments. I appreciate your patience. :)

I have begun researching what is needed for the privacy manifest, and will follow up shortly (on the order of a few weeks) with a pull request. I will get a release out thereafter.

@snehalvaishnav28
Copy link

snehalvaishnav28 commented Apr 4, 2024

When attempting to update the App Auth from the Pod, the "PrivacyInfo.xcprivacy" file is not included with the library. this file is required, do I need to be added manually. Regarding permissions based on Apple's documentation, the sample manifest does not specify the permissions needed according to Apple's guidelines.

To address this, it's essential to understand the details of the SDK usage. For example, if the app accesses file timestamps via an API (NSPrivacyAccessedAPIType), the permissions required should be specified accordingly in PrivacyInfo.xcprivacy can you help with this two.

Thank you in advance.

@mdmathias
Copy link
Collaborator

@snehalvaishnav28 The screenshots in #822 show that the privacy manifest is bundled with an app built via Swift Package Manager and CocoaPods. Please use the latest release: https://github.com/openid/AppAuth-iOS/releases/tag/1.7.3.

The privacy manifest is empty because AppAuth does not do any tracking (or use any required reasons APIs) itself. Rather, it is the host app and its identity provider that may do the tracking. Host apps should declare their privacy impacting usage (including what their identity providers track) in their own privacy manifest files.

@snehalvaishnav28
Copy link

Thank you @mdmathias

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement triage Issues that need to be triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants