Skip to content

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.

  1. Open Workspace → Store Audit.

  2. 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.

  3. Click Run audit, and give it a minute.

  4. 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.

🟢 No blocking issues foundNothing we check for is wrong.
🟡 Needs review before submittingSomething needs your attention, but it isn’t a certain rejection.
🔴 Likely to be rejectedThere’s a problem the store rejects apps for. Fix it first.

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.

BlockingThis gets your app rejected. Fix before submitting.
WarningThis may get you rejected or sent a query by a reviewer.
Needs reviewWe couldn’t tell from your app alone — have a look yourself.
PassedWe checked this, and it’s fine.
UpcomingA rule that only starts applying on a future date — the badge shows when.
Not applicableDoesn’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.

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.

33 checks — 20 for Google Play, 13 for the App Store. They’re the rules apps most commonly get rejected for.

CheckIf it failsWhat it means
Android version supportRejectedYour 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 featuresRejectedIf 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 appsRejectedAsking 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 accessRejectedIf 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 accessRejectedBackground or precise location has to be core to your app and explained to the user, not just requested by default.
Explaining permissionsRejectedBefore Android asks for something sensitive, your app has to tell the user what it’s for and why.
Not someone else’s websiteRejectedAn 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 moderationRejectedIf 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 locationRejectedAsk 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 verificationRejectedReading 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 discountsRejectedIf 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 accessRejectedConnecting 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 contactsRejectedAdding 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 functionalityRiskyDemo-level or placeholder apps get rejected. Your app needs real features and real content.
Privacy policyRiskyEvery app needs a privacy policy — linked in Play Console and reachable from inside the app — even if it collects no data.
Ads consentRiskyIf you show ads, European and UK users must be asked for consent through an approved consent screen.
Sharing data with AIRiskyIf 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 logRiskyReading 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 accessRiskyAccess 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 agentsRiskyIf 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.

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.

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.