Scan your app's SDKs and backend to see what data you really collect, then fill Apple's App Privacy labels accurately and consistently.
Help me answer the App Privacy questions honestly for my app
How it works
- Inventory what your app collects: Vovy asks Claude Code to list every SDK in your project, like analytics, crash reporting or sign-in, and what each one sends off the phone.
- Map it to Apple's categories: A table maps each item to Apple's types, like Contact Info, Identifiers, Usage Data and Diagnostics, and whether it is linked to the user.
- Fill in App Privacy: Vovy opens App Privacy in App Store Connect and answers each question from the table, including whether any data is used for tracking.
- Reuse it for Google Play: If you ship on Android, Vovy fills the Data safety form from the same table so both stores say the same thing.
- Publish the labels: Vovy shows the final label preview and publishes it once you approve, since it appears on your public store page.
What you provide
- Your app's code
- App Store Connect access
What you get
- A data inventory table
- Accurate Apple privacy labels
- A matching Google Play Data safety form
FAQ
What if I get it wrong?
You can update labels anytime without a new build. Inaccurate labels can lead to rejection or removal, so accuracy matters.
Does using Google Sign-In count as collecting data?
Yes. If you store the user's email or name, that is Contact Info linked to the user.
Do I need an ATT prompt?
Only if you track users across other companies' apps or sites, such as some ad attribution. Many apps do not.
Related tasks
All tasks