Hi,
I tried to check the Dropbox App's App Privacy notes itself and see what would make sense for the App Privacy setting in the Apple App Store for an App using the SDK.
As the SDK is limited, the option to have it render an Webview to login exposes the whole Dropbox Frontend and its interaction and therefore makes this aspect a part of your own App. If you would rely on login via the installed Dropbox App, some of the elemtents below would not be needed.
Currently my selection is as follows. I added some remarks in brackets () from my interpretation.
The selection below does not reflect any of my own App's data privacy, but only the ones inherited by integrating Dropbox SDK.
Also for the Data Types and content - there is a set of User Content which very much differs on your use case. My use case is "Other User Content" only, not having video/audio/photos and such.
# Data Types
7 data types collected from this app: Name, Email Address, Other User Content, User ID, Device ID, Product Interaction, Other Diagnostic Data (User Content types depend on your app's data)
# Contact Info
## Name
- Used for App Functionality (you can login to dp via webview in your app, showing names)
- Linked to the user's identity (you can login to dp via webview in your app)
## Email Address
- Used for App Functionality (you can login to dp via webview in your app, showing names)
- Linked to the user's identity (you can login to dp via webview in your app, showing names)
- Used for tracking purposes (dp might use this for tracking as the main dp app does mention it)
# User Content
## Other User Content
- Used for App Functionality
- Linked to the user's identity
# Identifiers
## User ID
- Used for Developer’s Advertising or Marketing, and App Functionality (guessing as dp during Login or API calls could use the data and the main dp app is listing this - e.g. bound in the access token)
- Linked to the user's identity
## DeviceID
- Used for Analytics, Developer’s Advertising or Marketing, and App Functionality (guessing as dp during Login or API calls could use the data and the main dp app is listing this - e.g. bound in the access token)
- Linked to the user's identity
- Used for tracking purposes
# Usage Data
## Product Interaction
- Used for Developer’s Advertising or Marketing, App Functionality, and Analytics (guessing that API calls might be used, login also)
- Linked to the user's identity
# Diagnostics
## Other Diagnostic Data
- Used for App Functionality (not sure)
- Linked to the user's identity (not sure)
