How to get approved on the first submission to the App Store and Google Play
Store rejection usually comes from a missing declaration, not from your code. Here is our pre-release checklist.
When people talk about app rejection they think of technical faults. In practice, the majority of rejected submissions have nothing to do with the app itself and everything to do with the declarations that describe it. If the privacy labels, the data safety form, the account deletion flow or the support links are missing, even a flawlessly working app comes back at review.
What has to be ready before release
- A privacy policy published at an accessible URL
- App Store privacy labels and the Google Play data safety form
- An account deletion flow reachable from inside the app
- A working support address and a contact page
- Copy that explains the reason behind each permission request
What every item on this list has in common is that it can be handled in the first week of the project rather than in release week. Writing the privacy policy at the start is both cheaper and faster than writing it at the end — because you are already making the decisions about what data you collect and why at that stage.
Where should the privacy policy live?
Both stores require the policy to sit at a public, permanent and directly accessible address. Text embedded in the app, or a page behind a login, is not accepted. A fixed path on your corporate website (for example /gizlilik-politikasi) is the most reliable option for this.
The content of the policy also has to match what the app actually does. Saying "we do not collect location data" on the form while the app requests location permission is exactly the kind of inconsistency reviewers catch, and it leads straight to rejection.
