Blocks submissionBoth stores

The store name is short, plain, and free of emoji, shouting and special characters

What is checked This rule is decided by code from the built app and the listing: listing.text.

Applies to every app

Checked from built, not yet uploaded, on a test track, submitted and in review, published

The rule, in our words

• App Review Guidelines: All metadata, including privacy information, description, screenshots and previews, must accurately reflect the app's core experience and be kept current with each version. No hidden, dormant or undocumented features; every new feature and product change must be described specifically in Notes for Review (generic notes are rejected) and be reachable by reviewers. Misleading marketing, inside or outside the App Store, is grounds for removal and account termination. If there are in-app purchases, the description, screenshots and previews must say which items need extra payment. Screenshots should show the app in use, not just title art, login or splash; previews may only be video captures of the app itself. Pick the right category and answer age-rating questions honestly. App names are limited to 30 characters; do not stuff metadata with trademarks, other app names, prices or irrelevant terms. Icons, screenshots and previews must be suitable for a 4+ rating even if the app is rated higher; "For Kids" and "For Children" are reserved for the Kids Category. Secure rights to all assets and show fictional rather than real-person data. Do not show other mobile platforms' names, icons or imagery unless there is specific, approved interactive functionality. "What's New" must clearly describe significant changes; only simple fixes may use a generic note.
• User Data: Be transparent about all user data handling and comply with applicable privacy law; you are responsible for third-party SDKs and AI integrations in the app. Personal and sensitive data (including device location) must be limited to app functionality the user reasonably expects, transmitted with modern cryptography such as HTTPS, requested via runtime permissions, and never sold. Where collection may not be expected (for example background collection), show a prominent in-app disclosure in the normal flow (not only in a policy, not bundled with unrelated text) describing the data and its use, immediately before any consent or runtime permission request; consent must be a clear affirmative action obtained before collection, and backing out or auto-dismissing messages do not count. If Google asks, you must within 2 weeks show evidence that an SDK collecting data by default meets these rules. Persistent device identifiers may not be linked to other personal data or resettable IDs except for telephony or enterprise device management. Every app needs an accurate Data safety section consistent with its privacy policy, and a privacy policy linked in Play Console and in the app, at a public non-PDF URL, labelled as such, naming the developer or app with a contact, and covering data types, sharing, security, retention and deletion. Apps with account creation must offer account deletion in-app and via a web link entered in Play Console, deleting all associated data (freezing does not count), with any retention disclosed. App Set ID may not be used for ads. EU/UK/Swiss personal data from Google must be handled under the Data Privacy Framework terms, with immediate notice to Google if you cannot comply.

Okkok never stores the stores' text. Each item above is our paraphrase, and the link is the page it rests on, verified unchanged by fingerprint on every run.

The other store

• Google adds the web-link requirement; Apple adds the ban on call/email/support-only flows and explicitly covers auto-created guest accounts. "Freezing does not count" (Google) equals "deactivating is insufficient" (Apple). partial
• Apple reserves two exact phrases; Google judges imagery and wording generally. partial
• Google names transport encryption; Apple says only "appropriate security measures". google-stricter
• Title length is identical (30 characters). Google additionally bans emoji and repeated special characters in title/icon/developer name, all-caps outside a brand name, unattributed testimonials, misleading icon symbols and claims of ranking, price or a Play programme; Apple additionally requires screenshots that show real use (not splash or login), previews that are app captures only, fictional rather than real-person data, no other platforms' imagery, and a specific "What's New". partial

Check your app

pip install git+https://github.com/petresandu-cloud/okkok
okkok audit path/to/app

The report names this rule as both.listing-name-rules and says what to do, who does it, where, and how it knows.