Checklist pack
Store facts template
A living doc for privacy answers and store metadata. Update it whenever dependencies change — not during the upload panic.
Markdown version · pairs with Issue #2
App identity
- App name / bundle id
- Primary category
- Age rating assumptions
- Owner / contact email for store questions
Data types collected
For each type: collected? linked to identity? used for tracking?
- Contact info
- Health & fitness
- Financial info
- Location
- Sensitive info
- Contacts
- User content
- Browsing history
- Identifiers (device / user)
- Purchases
- Usage data
- Diagnostics
SDK inventory
- SDK name
- Why it exists
- Data it can access
- Required purpose string impact
- Privacy manifest / nutrition label impact
- Owner who approved adding it
If you cannot explain an SDK in one sentence, it is not ready for a production archive.
Purpose strings
- Camera / photos / mic / contacts / location / Bluetooth / tracking / etc. actually used
- Info.plist copy matches real trigger paths
- No leftover strings for deleted features
Tracking / ATT
- Do you track under Apple’s definition? yes/no
- ATT prompt path and timing
- What happens if the user denies
Export compliance
- Standard encryption only? or more?
- Answer used in App Store Connect
- Doc / exemption reference if needed
Update trigger: any new SDK, analytics vendor, auth provider, paywall, cloud sync, or permission path.
Do not wait for Connect to surprise you.