Gacha rate disclosure: store, ad and in-game screens
Analysis
By UA Ledger staff — 1 min read

Checklist aligning gacha probability claims across ads, store and client, with Japan CAA card-matching FAQ as a jurisdiction anchor.
Gacha rate claims must match across ad, store page and client. Japan’s Consumer Affairs Agency maintains a Q&A on card-matching (“カード合わせ”) mechanics under premiums/representation rules — including how complete-gacha style constructions are analysed. Apple 2.3 still requires accurate metadata globally. Other jurisdictions (KR, EU, CN outbound) need their own statute rows; this checklist does not claim a single global statute.
Operator checklist
- Jurisdiction list for the flight (JP/KR/EU/US/CN-outbound as applicable).
- In-game rates screen URL or build screenshot with capture date.
- Ad claim must quote the same rarity percentages as the in-game screen.
- Store description must not promise higher rates than the client.
- Pity / guarantee language only if the live pity counter exists.
- Kompu-style combinations: Review CAA card-matching Q&A before shipping JP combination rewards.
- Unknowns: Mark any market without a body-read statute as counsel required.
Facts vs limits
| Field | Evidence or limit |
|---|---|
| JP CAA card-matching Q&A | caa.go.jp FAQ |
| Apple accurate metadata | Guideline 2.3 |
| Full multi-country statute table | Incomplete in this draft |
Research checked 20 September 2026. Local draft; human editorial review pending. No CMS write performed.
Featured
Related posts
More from the Platforms desk
platforms
·Archive date: 4 min read
Roblox Everywhere: when a platform ships standalone apps, it competes for your installs
measurement
platforms
·2 min read
AppLovin Ad Review drops user-level journeys for aggregate-only reporting
measurement
platforms
·2 min read
Apple adds an EU alternative ATT prompt from iOS 27.2 — mandatory in five markets
platforms
·1 min read