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 #289

Merged
merged 5 commits into from
Sep 20, 2023
Merged

Privacy Manifest #289

merged 5 commits into from
Sep 20, 2023

Conversation

weichsel
Copy link
Owner

Fixes #285

Changes proposed in this PR

  • Adds privacy manifest including tracking and API usage

@weichsel weichsel self-assigned this Sep 20, 2023
@weichsel weichsel merged commit 5559b82 into development Sep 20, 2023
10 checks passed
@weichsel weichsel deleted the enhancement/privacyManifest branch September 20, 2023 18:29
<string>NSPrivacyAccessedAPICategoryFileTimestamp</string>
<key>NSPrivacyAccessedAPITypeReasons</key>
<array>
<string>3B52.1</string>
Copy link

Choose a reason for hiding this comment

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

@weichsel From a code search, ZIPFoundation calls stat() (a required reason API) in FileManager+ZIP.swift. However, it does not call UIDocumentPickerViewController or UIDocumentBrowserViewController, and it does not reference UIKit anywhere, so it looks like ZIPFoundation does not specifically request users to grant access to timestamps of files or directories.

Users may grant access to access timestamps of files or directories in an app that integrates with ZIPFoundation, but that would be the app's responsibility to declare 3B52.1, instead of ZIPFoundation.

Could you elaborate why do you declare 3B52.1 for ZIPFoundation? Or would you consider removing it?

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.

Privacy Manifest
2 participants