You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Legal standing on every requirement. in_force, in_force_later (with the date it starts), store_policy, proposed, or guidance. Only verified law or store policy that is in force today can block a release. A proposed law or a guidance note never can.
How it is proven. automated (a check can see it), owner_attested (only you can confirm it), or mixed (both). An owner-attested requirement asks for your signed attestation, because a scan finding nothing proves nothing here.
A quoted source for every premise. Each source carries the URL, the date it was checked, a verbatim quote, and supports, which says whether it proves the obligation, the start date, or both. A rule blocks only when quoted sources cover the obligation and, if it has one, the start date. A source that could not be re-read is marked unverified with the reason, and a rule missing a quoted premise is listed as "confirm the source" and never blocks.
Applies only where it should. Each entry names its jurisdiction (an ISO country code, EU, or GLOBAL), an optional store, and the app features it covers (lending, crypto, medical, generative_ai, personal_data, subscriptions, social, marketplace, children). A rule with no features applies to every app in that place.
Built into Fleet Sweep. Every app declares its platforms, regions and features, and leaving one out is an error, because an unknown scope would silently drop rules. Any verified, in-force rule that applies and has no valid attestation makes the app BLOCKED.
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
in_force,in_force_later(with the date it starts),store_policy,proposed, orguidance. Only verified law or store policy that is in force today can block a release. A proposed law or a guidance note never can.automated(a check can see it),owner_attested(only you can confirm it), ormixed(both). An owner-attested requirement asks for your signed attestation, because a scan finding nothing proves nothing here.supports, which says whether it proves the obligation, the start date, or both. A rule blocks only when quoted sources cover the obligation and, if it has one, the start date. A source that could not be re-read is markedunverifiedwith the reason, and a rule missing a quoted premise is listed as "confirm the source" and never blocks.EU, orGLOBAL), an optional store, and the app features it covers (lending,crypto,medical,generative_ai,personal_data,subscriptions,social,marketplace,children). A rule with no features applies to every app in that place.platforms,regionsandfeatures, and leaving one out is an error, because an unknown scope would silently drop rules. Any verified, in-force rule that applies and has no valid attestation makes the appBLOCKED.Source section. RULING-REGISTER.md, What you get.
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run
bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.All reactions