A linter for store metadata.
Deterministic rule matching pairs with contextual analysis to tell the adjective from the brand, the word swift from Swift the framework, spark the energy noun from Spark Mail.
TRUST & SAFETY
Policy Checker
A two-phase compliance scan, static rules for prohibited terms and misleading-claim patterns plus contextual competitor-trademark detection, with field-aware severity calibrated per platform.
Get a free quick audit for your app.
Moves visibility + conversionTrust
What's distinctive.
Severity calibrated per platform.
The matrix is field-aware: titles block harder than descriptions, and the App Store enforces stricter than Google Play, so a term that warns in one field can block in another.
Catches rejections before review.
A rejected listing surfaces in no search and converts no one, so the engine flags violations before Apple or Google does and protects both inputs to organic install growth.
The methodology.
"Catch store policy violations before Apple and Google do."
- 1
Deterministic rule matching
Phase one runs per-platform prohibited-term lists and pattern matching for unsupported superlatives and claims. Enforcement is field-aware:
- Per-platform prohibited-term lists, such as price terms used in fields that disallow them.
- Pattern matching for unsupported superlatives and unsupported claims.
- Field-aware gradient: a term that warns in a description may block in a title.
- 2
Contextual brand detection
Phase two adds multilingual competitor-brand detection that reads context, distinguishing a common word used as an adjective from the same word used as a competitor brand name.
- 3
Severity matrix
Each finding is scored on a per-platform, per-field severity matrix that resolves to block, warn, or info. Block-severity findings are the ones that would trigger a review rejection.
- 4
Gate the publish path
Findings attach to live listing text and to newly generated metadata from Content Generation. Block-severity findings on a draft halt it before it enters the Weekly Revision Plan.
Data sources
Live listing text plus newly generated metadata from Content Generation; Apptonomy-maintained prohibited-term lists and misleading-claim pattern library, updated as Apple and Google publish guideline changes.
AI's role
AI handles the multilingual competitor-brand identification, reading context to tell a brand name from an ordinary word. The static rule library, the severity matrix, and the field-aware enforcement gradient are the human-authored framework, kept current weekly as Apple and Google update their guidelines.
A real recommendation, end to end.
This is the shape of a recommendation row in the Weekly Revision Plan. The reasoning, the sources, and the projected impact are part of the row — not buried in a tooltip.
Policy Checker
Prevents a review rejection and protects the Discoverability pillar; a rejected listing does not surface in search at all.Remove '#1 fitness tracker' from your title and '100% free' from your subtitle.
- Why
- '#1' matches the superlative-claim pattern, which is block severity in an App Store title; 'free' is a prohibited price term on both platforms, block severity in title and subtitle. Either flag on its own is enough to delay an update by 3 to 7 days while you re-submit.
- Sources
- Live App Store listing fields, Apptonomy prohibited-term and misleading-claim library, AI brand-context check.
- Expected impact
- Prevents a review rejection and protects the Discoverability pillar; a rejected listing does not surface in search at all.
What you get.
- Findings list, each violation flagged with platform, field, severity (block, warn, or info), and rule reference.
- Suggested fix per finding, such as remove '#1 fitness tracker' from the title with an alternative of 'top-rated fitness tracker'.
- Gate status for any Content Generation draft, where block-severity findings halt the draft from entering the Weekly Revision Plan.
How you act on it.
- Apply the suggested fix in the Weekly Revision Plan, or directly in the Listing Editor.
- Resolve every block-severity finding before publishing; these are the ones that would trigger a rejection.
- Review warn-severity findings, which surface in audit reports but do not block the update.
Policy Checker runs on every audit and gates every Content Generation draft, on all plans.
See plans →Catch store policy violations before Apple and Google do.
Paste any App Store or Google Play URL. The first audit is free.
Get a free quick audit for your app.