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

feat(ios): update privacy manifest to include NSPrivacyCollectedDataTypes #195

Closed

Conversation

erisu
Copy link
Member

@erisu erisu commented Apr 18, 2024

Platforms affected

ios

Motivation and Context

Include NSPrivacyCollectedDataTypes that the plugin uses

Description

Added NSPrivacyCollectedDataTypes

  • NSPrivacyCollectedDataTypeDeviceID for NSPrivacyCollectedDataTypePurposeAppFunctionality
  • NSPrivacyCollectedDataTypeOtherDataTypes for NSPrivacyCollectedDataTypePurposeAppFunctionality

Testing

n/a

Checklist

  • I've run the tests to see all new and existing tests pass
  • I added automated test coverage as appropriate for this change
  • Commit is prefixed with (platform) if this change only applies to one platform (e.g. (android))
  • If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct keyword to close issues using keywords)
  • I've updated the documentation if necessary

@breautek
Copy link
Contributor

I've since found a page that actually defines what apple means by collected data: https://developer.apple.com/app-store/app-privacy-details/#data-collection

It turns out that collected data means data moved off the device longer than necessary to process in real-time. E.g. if the data is stored for longer than it is required to fulfil an action. In otherwords if the data is kept on device, or if its sent to a server but the server doesn't retain that data, then it's not "collected".

It makes this PR invalid.

@breautek breautek closed this Apr 18, 2024
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.

2 participants