> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pool.day/llms.txt
> Use this file to discover all available pages before exploring further.

# App Review and privacy labels

> What to write in App Store Connect's privacy questions, the review notes and your purpose strings when your app uses PoolKit.

PoolKit reads photos on the device, so most of what your app's privacy label says depends on what **your** app does with the results. This page lists what PoolKit itself sends, so you can answer for it, and what reviewers usually ask.

## What PoolKit sends, and how to label it

App Store Connect asks about data that leaves the device. With PoolKit's defaults, two things do.

| PoolKit sends | When | App Privacy type | Linked to the person | Tracking | Purpose |
| - | - | - | - | - | - |
| A random install ID | Every launch with a network | Identifiers: Device ID | No | No | App Functionality |
| Derived text and labels for cloud assist | Only when your configuration and the grant allow it | User Content: Other User Content | No | No | App Functionality |
| Run reports: counts, timings, device model, iOS version | Only with `sendsRunReports` | Diagnostics: Performance Data | No | No | App Functionality |

The package's `PrivacyInfo.xcprivacy` declares the same, and Xcode merges it into your app's privacy report. Nothing PoolKit sends is used for tracking or advertising, and none of it is linked to an account.

Places and faces never reach Pool. Coordinates under `.locations` go to Apple's geocoder and Maps, which App Store Connect does not count as your collection. If **your app** sends places, interests, profiles or anything else from PoolKit to your server, label that yourself: for example Location (Precise or Coarse), User Content (Photos or Videos) or Other Data, linked if you tie it to an account.

## Purpose strings

iOS shows `NSPhotoLibraryUsageDescription` in the photo prompt, and reviewers read it. Say what the person gets, in your app's words:

* "Find the things you saved in your photos, so we can suggest gifts you will like."
* "Show the trips you took and the places you saved for them."

Avoid "to improve your experience" or anything that does not name the feature. Ask for photo access when the person reaches the feature, not at launch: PoolKit shows the system prompt on the first `requestAccess`, so call it from the feature.

## Notes for the reviewer

Add a short note in App Review Information, for example:

> Photos are analysed on the device by PoolKit to find products the user saved. No photo leaves the device. To try it: allow photo access when the Wishlist tab asks, take a screenshot of any product page, and open Wishlist.

If the review device's library is empty, the feature shows nothing. Say how to see it working, or ship a demo mode that uses PoolKit's test fixtures (see [Testing](https://docs.pool.day/testing.md)).

## Guidelines reviewers check

| Guideline | What it asks | With PoolKit |
| - | - | - |
| 5.1.1 (i) Privacy policy | A policy that says what you collect and why | List what you send to your servers. If cloud assist is on, name Pool as a processor. |
| 5.1.1 (ii) Permission | Ask for consent, and only for what the feature needs | One grant per feature with its purpose; ask in context. See [Grants](https://docs.pool.day/grants.md). |
| 5.1.1 (iii) Data minimization | Only the data the feature needs | Grants narrow sources, kinds of things and operations; `IndexOptions` narrows the window. |
| 5.1.1 (v) Account deletion | Delete data with the account | Revoke the grants and delete what you stored. PoolKit's index lives in your container and goes with the app. |
| 5.1.2 Data use and sharing | No sharing for tracking without consent | PoolKit shares nothing for tracking. Your own use of results is yours to disclose. |
| 5.1.2 (vi) Photos for other purposes | Data from the photo library must not be used for advertising or sold | Use results for the feature you asked for. Do not send them to ad networks. |

## People and places

`.people` and `.locations` are sensitive. Ask for them only for a feature that needs them, in their own grant, with a purpose that says so. Faces are biometric data under laws such as the GDPR and Illinois' BIPA, even when they stay on the device; check your consent screen and policy with your counsel before you ship [People](https://docs.pool.day/people.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.