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.
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 showsNSPhotoLibraryUsageDescription 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.”
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).
Guidelines reviewers check
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.
