Mobile App Privacy Data Map
List what data the app collects, why, and where it goes.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Create a data map for [APP_NAME]. Features: [FEATURES]. SDKs and services used: [SDKS_AND_SERVICES]. Account and device data collected: [DATA_COLLECTED]. Make a table with Data item, Purpose, Where stored, Who receives it, Retention, Needed or optional, and User control. Include identifiers, location, contacts, photos, analytics and crash data. Mark items collected only because a third-party library does so. Suggest data that can be dropped, delayed or made optional. Draft three plain-language sentences for the privacy section of the store listing and a one-screen in-app summary. Check the store's privacy label rules and local law [VERIFY] for [JURISDICTION] with a qualified adviser. Do not assume what a library collects; list it as a question to confirm. Add a short list of data you recommend not collecting at all and why, and a retention suggestion for each item you keep. Provide a plain-language answer to the question users ask most often, what do you know about me, in under 80 words. Finish with a checklist for each new SDK: what it collects, who owns the data, whether it can be disabled and who approves it.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.