Mobile App Data Privacy: What Apple and Google Require Before Launch
Privacy manifests, Data safety, account deletion and photo permissions: what Apple and Google require before an app launches, with a pre-launch checklist.
What do you need on privacy before launching an app?
Before you submit, Apple and Google expect five things to be true: your store privacy declarations (Apple's App Privacy details and Google Play's Data safety form) match what the app and every SDK in it actually collect; your iOS build declares an approved reason for each required-reason API in a privacy manifest; users who can create an account can also start deleting it inside the app, with a web link as well on Google Play; you request only the permissions the features need, using the Android photo picker where broad media access is not core; and you have an accurate privacy policy linked from the app and the listings.
Underneath the store rules sits the real work: collect less, ask at the right moment, control third-party SDKs, keep data only as long as needed and honour deletion everywhere it is stored. Local privacy laws add obligations that vary by market. This page explains technical and store requirements; it is not legal advice, so confirm legal obligations with qualified counsel.
Key takeaways
- Missing required-reason declarations stop iOS builds being accepted (reported as ITMS-91053).
- Apple treats deactivation as insufficient; deletion must start in the app.
- Google Play needs an in-app deletion path and a web link for deletion requests.
- Every Play app needs a Data safety form, even one that collects nothing.
- Broad photo and video access on Play is only for apps whose core function needs it.
- You are responsible for what your SDKs collect, in both stores.
Store privacy pre-flight: Apple and Google
Use this table as a pre-flight check. The last column is what tends to go wrong when a row is skipped.
| Requirement | Apple App Store | Google Play | What goes wrong if you skip it |
|---|---|---|---|
| Privacy declaration | App Privacy details in App Store Connect, including data collected by third-party partners | Data safety form for every app on closed, open or production tracks, including apps that collect no data | Submission blocked, or a declaration that does not match the app; on Play, discrepancies can lead to blocked updates or removal |
| Privacy policy | Required | Required, including for apps that collect no data | Listing incomplete; rejection |
| Required-reason APIs | Approved reason declared in a privacy manifest | No equivalent | Build not accepted by App Store Connect |
| Third-party SDKs | Privacy manifests (and signatures for binary dependencies) for SDKs on Apple's list | SDK data included in Data safety | Rejection, or declarations that understate collection |
| Account deletion | Start deletion in the app; deactivation alone is insufficient | In-app path and a web link for deletion requests | Rejection or policy enforcement |
| Photos and videos | Purpose strings for each permission | READ_MEDIA_IMAGES and READ_MEDIA_VIDEO only if core functionality needs broad access; otherwise the photo picker | Policy rejection on Play |
| Notifications | User permission required | POST_NOTIFICATIONS runtime permission on Android 13+ | Notifications silently not shown |
| Tracking | App Tracking Transparency before tracking | Advertising ID controls and policy rules | Rejection; inaccurate tracking disclosure |
Privacy manifests and required-reason APIs (ITMS-91053)
Apple keeps a list of APIs that can be misused to fingerprint devices, called required-reason APIs. If your app or any SDK in it uses one, the privacy manifest (PrivacyInfo.xcprivacy) must declare the API category and an approved reason. Apple's documentation is direct: "Starting May 1, 2024, apps that don't describe their use of required reason API in their privacy manifest file aren't accepted by App Store Connect." Developers report this failure as ITMS-91053, a missing API declaration.
Separately, Apple publishes a list of commonly used third-party SDKs (it includes Firebase packages, Flutter, Alamofire and OneSignal, among others). When a new app or an update adds one of them, the SDK must include its own privacy manifest, and a signature if it is a binary dependency. Apple's note on this is worth repeating to the whole team: "You are responsible for all the code the SDK includes."
In practice: update SDKs to versions that ship manifests, add your own app-level manifest for your code, and check the upload email from App Store Connect before you plan a release date around the build.
Account deletion: deactivating is not deleting
Apple's App Review Guideline 5.1.1(v) says: "If your app supports account creation, you must also offer account deletion within the app." Apple's account deletion guidance adds that "only offering to temporarily deactivate or disable an account is insufficient". If users must visit a website to finish, link directly to the right page. Apps outside highly regulated industries should not require a phone call, an email or another support flow to delete an account. Apps that use Sign in with Apple should revoke the user's tokens through the Sign in with Apple REST API.
Google Play requires an in-app path and "a web link resource where users can request app account deletion and associated data deletion", so people who have already uninstalled the app can still ask. You may keep some data for legitimate reasons such as security, fraud prevention or regulatory compliance, as long as you disclose that.
The engineering part is making deletion reach every system: the main database, file storage, analytics, support tools, email platforms and backups on their normal expiry. The authentication guide covers how sign-in and tokens fit in.
Google Play Data safety, even if you collect nothing
Every app published on Google Play's closed, open or production tracks must complete the Data safety form, including apps that collect no user data; those still need a privacy policy link. The form covers data collected and shared by SDKs in the app, not only your own code. Google does not verify the answers up front, but says that discrepancies can lead to blocked updates or removal. Apple's App Privacy details work the same way in spirit: you declare, and you are accountable for accuracy. Apple lets you update those answers without shipping a new build.
Photo, video and notification permissions on Android
Google Play's Photo and Video Permissions policy limits READ_MEDIA_IMAGES and READ_MEDIA_VIDEO to apps whose core functionality needs broad access to photos and videos, such as a gallery app. Others should use the system photo picker. Full compliance has been mandatory since 28 May 2025. The Android photo picker gives the app access only to the media the user selects; it is available on Android 11 and later through system updates, and on Android 4.4 to 10 through Google Play services.
Android 13 (API 33) added the POST_NOTIFICATIONS runtime permission, and notifications are off by default for new installs. Ask for it when the user can see why, not on first launch. Push notification strategy covers timing and marketing consent in detail.
On both platforms, request the least access that works (approximate rather than precise location, while-in-use rather than always) and keep the app usable if a permission is denied.
Third-party SDK audit worksheet
Analytics, advertising, attribution, crash reporting and support SDKs often collect data themselves, and both stores hold you responsible for disclosing it. Fill in one row per SDK before you answer either store's questionnaire. Check each SDK's own documentation for what it collects, and configure it to collect less where it allows. AI SDKs and model providers raise similar questions; see AI data privacy.
Hypothetical example: the filled row below is illustrative, not a statement about any specific product.
| SDK | Data it collects | Linked to the user? | Privacy manifest present? | Data safety entry | App Privacy entry | Can collection be reduced? |
|---|---|---|---|---|---|---|
| Example crash reporter | Crash logs, device model, OS version | Linked if you attach a user ID | Check the SDK release notes | App info and performance: crash logs | Diagnostics: crash data | Do not attach user IDs unless needed |
| Your analytics SDK | ||||||
| Your advertising or attribution SDK | ||||||
| Your support or chat SDK |
Privacy vs security, and MASVS-PRIVACY
Security protects data from unauthorised access; it is covered in mobile app security. Privacy asks whether you should have the data at all, what users agreed to, and who else receives it. A perfectly secure app can still breach privacy by collecting too much or sharing it without consent.
If your team uses the OWASP Mobile Application Security Verification Standard, version 2.1.0 (January 2024) added a MASVS-PRIVACY group with four controls: the app minimises access to sensitive data and resources; prevents identification of the user; is transparent about data collection and usage; and offers user control over their data. They map neatly onto the rest of this page and give testers a shared vocabulary.
Personal data and what apps commonly collect
Personal data is information relating to an identifiable person. On mobile, that includes obvious items like names and emails, and less obvious ones like precise location, device identifiers, photos and contacts, and usage data tied to an account or device. Aggregated, genuinely anonymised data is generally treated differently, but anonymisation is harder than it looks.
| Data type | Typical purpose | Questions to ask |
|---|---|---|
| Account details | Sign-in, communication | Do we need a phone number and an email? |
| Location | Maps, delivery, local content | Is approximate location enough? Only while in use? |
| Contacts and photos | Sharing, uploads | Can we use a system picker instead of full access? |
| Device identifiers | Analytics, advertising, fraud | Is tracking consent required? |
| Usage analytics | Product improvement | Is it linked to identity? For how long? |
| Health or financial data | Core features | Which extra legal and store rules apply? |
| Crash and diagnostic data | Stability | Could logs contain personal data? |
Data minimisation and consent
Decide what data each feature needs before building it, prefer less precise data where it works, process on the device where possible, and set retention periods from the start. Privacy by design is cheaper than retrofitting consent and deletion into an app that collected everything by default. The onboarding guide covers when to ask for permissions.
Where consent is the legal basis for processing, it generally needs to be informed, specific and as easy to withdraw as to give; requirements vary by law. Keep a short in-app explanation at the point of collection and a clear, accurate privacy policy linked from the app and its store listings.
On iOS, App Tracking Transparency requires permission before tracking users across other companies' apps and websites or using the advertising identifier for that purpose. Android lets users reset or delete their advertising ID. Design analytics to work well without cross-app tracking, as described in mobile app analytics.
Retention, access and deletion requests
Store personal data securely on the device and server, restrict internal access, and define how long each type is kept. Delete or anonymise data when its purpose ends. Retention periods should also cover backups, logs and analytics exports, which are easy to forget.
Many privacy laws give users rights to access, correct, export and delete their data. These are separate from the store account deletion rules, but the same plumbing serves both: a way to find every record about a user across your systems and third-party services.
Regional notes
Store rules apply everywhere. Privacy law differs by market, and so do its timelines. The notes below are a starting point for a conversation with counsel, not a summary of obligations. The EU GDPR, California's CCPA as amended by the CPRA, Canada's PIPEDA and sector rules such as health or children's privacy laws may also apply.
| Market | Main law | What to check |
|---|---|---|
| India | Digital Personal Data Protection Act 2023 and the DPDP Rules 2025 | The Rules were notified in November 2025 and phase in; law-firm summaries put most obligations around May 2027. Confirm current dates against the official text. |
| UAE | Federal Decree-Law No. 45 of 2021 (PDPL), in effect since 2 January 2022 | Cross-border transfer requirements; whether Executive Regulations are in force (check with UAE counsel); the DIFC has its own data protection law. |
| UK | UK GDPR and the Data Protection Act 2018 | The ICO publishes guidance on privacy in the product design lifecycle, including launch. |
| Australia | Privacy Act 1988 and the Australian Privacy Principles | APP 1 (open management and a privacy policy), APP 8 (overseas disclosure), APP 11 (security). |
| Singapore | Personal Data Protection Act 2012 | The PDPC lists obligations including transfer limitation and data breach notification. |
Pre-launch privacy checklist
Work through this before the first submission and again before any update that adds an SDK, a permission or a new kind of data. For the rest of the release process, see the app launch checklist.
- Data inventory written: what is collected, why, where it goes, how long it is kept
- SDK audit worksheet filled in for every SDK, with collection reduced where possible
- SDKs updated to versions with privacy manifests; app-level manifest declares required-reason APIs
- Test upload to App Store Connect done early, with no missing-declaration warnings
- App Privacy details and Data safety answers match the worksheet
- Privacy policy accurate, and linked in the app and both listings
- Account deletion starts in the app, is not just deactivation, and reaches every system
- Web link for deletion requests published and added in Play Console
- Sign in with Apple tokens revoked on deletion, if you use it
- Photo picker used unless broad media access is core; permission declarations ready if not
- Notification, location and other permissions requested in context, with the app usable if denied
- Tracking consent requested before any cross-app tracking
- Retention periods enforced, including logs and backups
- Legal requirements confirmed with qualified counsel for each market
Common mistakes
- Filling in store declarations from memory instead of from an SDK audit
- Offering "deactivate account" and calling it deletion
- Making users email support to delete an account
- Requesting broad photo access for a profile picture upload
- Forgetting that an SDK update can change what is collected and what must be declared
- Deleting the user record but leaving their data in analytics, support and email tools
Conclusion
Privacy before launch comes down to knowing exactly what your app and its SDKs collect, declaring it accurately in both stores, building real account deletion, and asking for the least access at the right moment. Store rules set a baseline everywhere; local laws add requirements that vary by market, so confirm those with counsel. For protecting the data you do keep, read mobile app security. If you would like help building these flows, ZSpace Labs works on iOS and Android app development. For related guides, see ecommerce privacy and customer data and the mobile app development guide.
Want a privacy and store-compliance check before you submit?
ZSpace Labs is a remote-first technology studio that works with clients globally on mobile apps and permission and consent UX. If useful, we can go through your SDKs, declarations and deletion flow with you, alongside your legal advisers.
Sources
Apple: App Review Guidelines (5.1.1(v)); offering account deletion in your app; App Privacy details; third-party SDK requirements; describing use of required reason API; Apple Developer News, 7 December 2023: privacy manifests and required reasons.
Google: Play account deletion requirements; Data safety section; Photo and Video Permissions policy; Android photo picker; notification runtime permission.
Standards and industry: OWASP MASVS v2.1.0 release: MASVS-PRIVACY; Donny Wals: privacy manifests and required-reason APIs (ITMS-91053).
Law and regulation: UAE government: data protection laws; OAIC: Australian Privacy Principles quick reference; PDPC: data protection obligations; ICO: privacy in the product design lifecycle, launch; AZB & Partners: DPDP Act phased roll-out (law-firm commentary).
Accessed 14 October 2026. Store policies and privacy laws change, and dates may move; check the current pages. Nothing here is legal advice.
Common questions.
The practices that control what personal data an app collects, why, how it's used and shared, how long it's kept, and what control users have over it.
Broadly, any information relating to an identifiable person: names, emails, phone numbers, precise location, device identifiers, photos, health data, and behavioural data linked to an account or device. Definitions vary by law.
Collecting and keeping only the data needed for a clear purpose. It reduces risk, simplifies compliance and builds user trust.
Both the App Store and Google Play require a privacy policy for apps, and many privacy laws require one as well. It must accurately describe what the app does with data.
The "privacy nutrition label" developers complete in App Store Connect, describing data collected by the app and its third-party partners, including SDKs, and whether it's used for tracking. You can update the answers without submitting a new build.
A declaration in Play Console describing what data an app collects and shares, security practices and deletion options, displayed on the store listing. Every app on a closed, open or production track needs one, even if it collects no data.
The error developers report receiving from App Store Connect when a build uses one of Apple's required-reason APIs without declaring an approved reason in a privacy manifest. Since 1 May 2024, Apple does not accept such builds. The fix is to add the declaration to your app's manifest or update the SDK that uses the API.
No. Apple's guidance says that only offering to temporarily deactivate or disable an account is insufficient. You can offer deactivation as an extra option, but users must be able to start full deletion in the app.
Apple's framework requiring apps to ask permission before tracking users across other companies' apps and websites or accessing the advertising identifier for that purpose.
Apple and Google both require apps that allow account creation to let users request account deletion, and Google Play also requires a web-based deletion option.
It can apply to apps processing personal data of people in the EU, depending on circumstances, and the UK has its own version. Other regions have different laws. Get qualified legal advice for your specific situation.
No. It explains technical, product and store requirements. Privacy obligations depend on jurisdiction, industry and specifics, so confirm requirements with qualified legal counsel.