Apple asks every app to describe the data it collects, in a form in App Store Connect that becomes the privacy label on your product page. If your app has a feedback component, the data it sends belongs in that form. This guide goes through the questions for what a Nitpick feedback component collects. It is information to help you fill in the form, not legal advice, and you remain responsible for the answers.
When the form applies
Apple asks for these answers for every new app and every app update. "Collect" means that data leaves the device in a way that lets you or your partners read it for longer than it takes to answer the request in real time. Data that stays on the device is not collected. You must also declare what the code of third parties in your app collects, which includes SDKs. A feedback component that sends reports to a server is such an SDK.
What the component sends
Only after the user opens the panel and presses Send, for a general comment or after pointing at something:
- The comment the user wrote.
- A screenshot of your own app screen, if the user kept it, and the tap position.
- The names of the screen and the element that you marked.
- The device model identifier, the OS version, the language, the app version and the build.
When the app starts it also asks for the feedback settings of the app. That request carries nothing about the user. Feedback is anonymous: no name, email address, account id or device name.
Suggested answers
| Apple data type | Why | Linked to identity | Tracking | Purpose |
|---|---|---|---|---|
| Other User Content | The comment and the screenshot | No | No | App Functionality |
| Customer Support | The report is a message to the maker | No | No | App Functionality |
| Product Interaction | The tap position and the element | No | No | App Functionality |
| Other Diagnostic Data | Device model, OS version, language, app version | No | No | App Functionality |
These are the same four types that the Swift package declares in its own privacy manifest, see the privacy manifest guide for SwiftUI. The Apple page we read does not name a screenshot of your own app screen, so Other User Content is our reading, not Apple's wording. Device ID is not collected, because only a model identifier is sent.
Apple treats data as linked to identity unless the identifiers are stripped. Nitpick sends none, so the answer is no for what the component sends. This holds only if the screenshot shows no name, email address or account details. Mask those with .nitpickMask() or NitpickMask; if your screens show them unmasked, the screenshot can contain personal data, and you have to judge for yourself how to answer. If your own app adds a user id or an email address to a comment, answer for that as well.
Can the answers be optional?
Apple lets you skip a data type only when all four conditions hold. The data is not used for tracking. It is not used for third-party advertising, your own advertising or marketing, or other purposes. It is collected only in infrequent cases that are not part of the main function of the app, and it is optional for the user. And the data is provided by the user in your app's interface, it is clear to the user what data is collected, the user's name or account name is prominently displayed in the submission form alongside the other data elements being submitted, and the user affirmatively chooses to provide the data for collection each time. The Nitpick form is anonymous and never shows a name or account name, so it does not meet the fourth condition. Declare the four data types.
Other things Apple wants
A link to a privacy policy in App Store Connect, and in the app (App Review Guideline 5.1.1(i)). Put the paragraph from Privacy and store forms in your policy, and keep the note under Send. You can change your answers at any time without submitting an update.
Keep reading
For Android, read Google Play Data safety for a feedback component. If your app is built with Expo, the same answers apply, see the privacy manifest guide for Expo. To see how the screenshot is made, read feedback with a screenshot in SwiftUI.