Store Audit
Getting rejected by an app store costs you days. You submit, wait, get a short message quoting a guideline number, guess at what it meant, fix something, and resubmit — and the clock starts again.
Store Audit skips that loop. It checks your app against the rules Google and Apple actually reject for, and tells you what’s wrong while you can still fix it in a minute.
Running an audit
Section titled “Running an audit”-
Open Workspace → Store Audit.
-
Pick Google Play or App Store. The two stores have different rules, so each gets its own audit and its own result — run one, or both.
-
Click Run audit, and give it a minute.
-
You get a verdict and a list of everything that was checked.
Run it again whenever you like — each run replaces the last result for that store.
What you get back
Section titled “What you get back”The verdict
Section titled “The verdict”| 🟢 No blocking issues found | Nothing we check for is wrong. |
| 🟡 Needs review before submitting | Something needs your attention, but it isn’t a certain rejection. |
| 🔴 Likely to be rejected | There’s a problem the store rejects apps for. Fix it first. |
The findings
Section titled “The findings”Every rule in that store’s list comes back with a result, so you always see the full picture — not just the problems. Anything you need to act on is listed first and opened up; the rest folds into groups you can expand.
| Blocking | This gets your app rejected. Fix before submitting. |
| Warning | This may get you rejected or sent a query by a reviewer. |
| Needs review | We couldn’t tell from your app alone — have a look yourself. |
| Passed | We checked this, and it’s fine. |
| Upcoming | A rule that only starts applying on a future date — the badge shows when. |
| Not applicable | Doesn’t apply to your app, so there was nothing to check. The row says why. |
Open any finding and it tells you what’s wrong, how to fix it, what in your app triggered it, and a link to the exact Google or Apple rule behind it.
The header reconciles to the total — “13 checks · 1 warning · 2 passed · 10 not applicable” — so you can always see what the verdict was based on. Each report also shows when it ran and which revision of your code it read, so you can tell when a result has gone stale after further changes.
Fixing what it finds
Section titled “Fixing what it finds”Where the fix is a code change, the finding has a Try to fix button — the same one a failed build offers. It hands the fix instructions to Primio and starts the work; re-run the audit afterwards to confirm. There’s a copy button too, if you’d rather paste them somewhere else.
Some findings have no button, and say why. Those are the ones no agent can decide for you: a privacy policy URL that doesn’t exist yet, or a call on what your app should do or be called. The fix instructions are still there, written for you to act on.
And some steps happen outside your code entirely — a declaration in the Play Console, a setting in App Store Connect. Those are listed separately under Do this in the store console, so they never get mixed into what the agent is asked to do.
What we check
Section titled “What we check”33 checks — 20 for Google Play, 13 for the App Store. They’re the rules apps most commonly get rejected for.
| Check | If it fails | What it means |
|---|---|---|
| Android version support | Rejected | Your app must be built for a recent enough Android version. Play requires Android 16 (API level 36) for new apps and updates submitted from 31 Aug 2026. |
| Accessibility features | Rejected | If your app uses Android’s accessibility system, it has to genuinely help users with disabilities. Play watches this one closely, because it’s a common route for misuse. Unless helping people with disabilities is its main purpose, your app must also explain what the service does and get the user’s consent before turning it on. |
| Seeing other installed apps | Rejected | Asking to see every app on someone’s phone is only allowed for a handful of app types, such as device search, antivirus apps, file managers and browsers — and never when a narrower check would do. |
| Contacts access | Rejected | If you read someone’s contacts, it has to be essential to what your app does — otherwise use the picker that lets them choose one. Applies from 27 Jan 2027 to apps built for Android 17 or newer. |
| Location access | Rejected | Background or precise location has to be core to your app and explained to the user, not just requested by default. |
| Explaining permissions | Rejected | Before Android asks for something sensitive, your app has to tell the user what it’s for and why. |
| Not someone else’s website | Rejected | An app that just shows a website you don’t own or have permission to show, or exists to send affiliate traffic, gets rejected under Play’s Spam policy. Wrapping your own working service is fine on Google Play — the App Store is stricter. |
| Content moderation | Rejected | If people can post things others see, or your app generates content with AI — AI chat replies included — users must be able to report offensive content and block abusive users, and the app must filter what’s objectionable (Play’s User Generated Content and AI-Generated Content policies). Anonymous or random chat with strangers must be for adults only. |
| Precise location | Rejected | Ask for the least location you need: approximate location where it’s enough, and Android’s location button for a one-off precise request. Ongoing precise location is for features like turn-by-turn navigation. Applies from 27 Jan 2027 to apps built for Android 17 or newer. |
| Call log for phone verification | Rejected | Reading the call log to verify an account by phone call is no longer allowed — use an SMS or credential-based check instead. Applies from 27 Jan 2027. |
| Student and eligibility discounts | Rejected | If a subscription discount depends on who someone is, like a student plan, the plan screen must show who qualifies, how it’s checked, and what changes when they no longer qualify. Applies from 27 Jan 2027. |
| Local network access | Rejected | Connecting to devices on someone’s Wi-Fi has to be core to your app. If the user just picks one device, or casts, the system device picker does the job. Applies from 25 Aug 2027 to apps built for Android 17 or newer. |
| Managing contacts | Rejected | Adding or editing contacts directly is for contact managers and similar apps. Saving one contact at a time should open the system contacts screen instead. Applies from 25 Aug 2027. |
| Real functionality | Risky | Demo-level or placeholder apps get rejected. Your app needs real features and real content. |
| Privacy policy | Risky | Every app needs a privacy policy — linked in Play Console and reachable from inside the app — even if it collects no data. |
| Ads consent | Risky | If you show ads, European and UK users must be asked for consent through an approved consent screen. |
| Sharing data with AI | Risky | If your app sends what people type, their photos, voice or other personal data to an AI provider, it has to say which provider gets what, and ask before the first message. |
| SMS and call log | Risky | Reading texts or the call log is only allowed for the default SMS or phone app, or a short list of uses such as spam blocking and backup. Reading a one-time passcode from a text isn’t one of them. |
| All files access | Risky | Access to every file on the phone is for file managers, backup, antivirus and document apps. Photos and files the user picks don’t need it. |
| Features for AI agents | Risky | If your app exposes features to AI assistants, they must do what they say and must never mislead the assistant or reach into other apps. Applies from 14 Apr 2027. |
| Check | If it fails | What it means |
|---|---|---|
| Deleting an account | Rejected | If people can create an account in your app, they must be able to delete it in your app too — not just by emailing you. |
| Sign-in options | Rejected | If you offer Google or Facebook login, you also need a privacy-respecting option. Sign in with Apple is the usual answer. |
| More than a website | Rejected | An app that just loads your website in a frame gets rejected under guideline 4.2. It needs to do something genuinely app-like. |
| Enough substance | Rejected | Apple rejects apps that are too simple or indistinguishable from hundreds of others — a single-screen utility is a hard sell. |
| Appropriate content | Rejected | Prank apps and content Apple considers objectionable don’t get through. |
| Explaining contacts access | Rejected | If your app reads contacts, Info.plist must carry a usage description explaining why — iOS rejects permission-gated APIs without a purpose string. |
| Content moderation | Rejected | Apps where people post content, and AI content creation apps — AI chat included — need a way to filter objectionable content, report it and block abusive users, plus published contact details (guideline 1.2). Apps built around random or anonymous chat aren’t allowed. |
| Sharing data with AI | Rejected | If your app shares personal data with a third-party AI, it has to say so, name who gets it, and get the user’s explicit permission first. A link to your privacy policy isn’t enough. |
| Original branding | Risky | Your app’s name, icon and description can’t look like an imitation of a well-known app. |
| Ad tracking consent | Risky | If your ads are personalized, iOS requires you to ask permission to track first. Non-personalized ads don’t need it. |
| Privacy declarations | Risky | Apple requires a privacy manifest declaring what data your app uses and why. Missing it triggers an automated rejection email. |
| Privacy policy | Risky | Every app needs a privacy policy users can reach from inside the app. |
| Tracking disclosure | Risky | If you say your app tracks users, you also have to list the tracking domains that data goes to. |
Deadlines matter: a rule that hasn’t taken effect yet won’t count against you, so an upcoming store requirement won’t turn your report red before it applies.
What it can’t tell you
Section titled “What it can’t tell you”Store Audit catches the problems that are visible in your app. It’s a strong safety net, not a guarantee.
- It can’t judge things that only happen at runtime, or on a server you control.
- It doesn’t check your store listing — your screenshots, description, age rating or data-safety answers.
- Reviewers are human, and they apply judgment no automated check reproduces.
A green verdict means nothing we check for is wrong. It isn’t a promise from Apple or Google.
Related
Section titled “Related”- Submission Checklist — the wider pre-submission pass
- Handling Rejections — what to do if you’re rejected anyway
- Google Play Guide and App Store Guide
- Store Assets — generate your store listing