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 file #18

Closed
wants to merge 1 commit into from
Closed

Add privacy manifest file #18

wants to merge 1 commit into from

Conversation

mii-chan
Copy link
Contributor

@mii-chan mii-chan commented Jan 24, 2024

Why?

Apps and third-party SDKs should contain a privacy manifest file by Spring 2024 to avoid the app review rejection.

How?

Since swift-user-defaults uses UserDefaults,

  • NSPrivacyAccessedAPITypes
    • NSPrivacyAccessedAPIType: NSPrivacyAccessedAPICategoryUserDefaults
    • NSPrivacyAccessedAPITypeReasons: C56D.1?

What I'd like you to review/discuss

https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api#4278401

C56D.1
Declare this reason if your third-party SDK is providing a wrapper function around user defaults API(s) for the app to use, and you only access the user defaults APIs when the app calls your wrapper function. This reason may only be declared by third-party SDKs. This reason may not be declared if your third-party SDK was created primarily to wrap required reason API(s).

Information accessed for this reason, or any derived information, may not be used for your third-party SDK’s own purposes or sent off-device by your third-party SDK.

I thought C56D.1 was appropriate as this library provided wrapper functions around UserDefaults API and added some Swift friendly functionalities.

This reason may not be declared if your third-party SDK was created primarily to wrap required reason API(s).

But according to this statement, we can't use it since it's exclusively a UserDefaults API wrapper? 😕
However, if C56D.1 cannot be used, which one would be appropriate for this library? (I don't think any of the options are suitable for our use...)

@mii-chan mii-chan self-assigned this Jan 24, 2024
<string>NSPrivacyAccessedAPICategoryUserDefaults</string>
<key>NSPrivacyAccessedAPITypeReasons</key>
<array>
<string>C56D.1</string>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

still not sure which reason is appropriate for this library...😭

@mii-chan mii-chan closed this Jan 25, 2024
@mii-chan mii-chan deleted the mii/privacy-manifest branch January 25, 2024 06:54
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

Successfully merging this pull request may close these issues.

1 participant