Regional rules get sharper on both stores
Age ratings and content-disclosure policy both got more specific this cycle — regional and content-based carve-outs are doing more of the compliance work than blanket global rules.
This edition covers a Korea-specific age rating change on the App Store and a Google Play policy clarification narrowing what counts as a compliant listing.
Week at a glance
What changed
Apple lets Korean developers override its own App Store age rating
Apple now lets developers with an official GRAC (Game Rating and Administration Committee) classification override the age rating Apple's own questionnaire assigned, using their GRAC Rating Classification Number on their next version submission for the Korean App Store. A second change lands in October 2026, moving two mild content descriptors from "All" to "12+" in Korea.
Store changes
Confirmed platform, policy, and distribution changes.
Apple lets Korean developers override its own App Store age rating
Apple now lets developers with an official GRAC (Game Rating and Administration Committee) classification override the age rating Apple's own questionnaire assigned, using their GRAC Rating Classification Number on their next version submission for the Korean App Store. A second change lands in October 2026, moving two mild content descriptors from "All" to "12+" in Korea.
- Why it matters
- Regional rating logic is becoming a real distribution variable, not just a label — the rating shown determines who can even find an app in a given market.
- Who should care
- Games and Entertainment category developers publishing on the Korean App Store.
- Suggested action
- If you hold a GRAC classification, check whether overriding your Korean rating better matches your actual audience before your next version submission.
Google Play tightens content-rating and AI-data disclosure rules
Google Play clarified that unrated apps are not allowed on the store, added guidance on precise vs. approximate location disclosures in the Data Safety section, and confirmed that user-data requirements also apply to third-party AI integrations developers embed in their apps.
- Why it matters
- This closes a gap where a listing could look compliant on the surface while an embedded AI feature quietly handled user data without matching disclosure.
- Who should care
- Any Google Play developer using or planning to add a third-party AI integration, or displaying precise location data.
- Suggested action
- Audit your Data Safety section for any AI feature you did not build in-house, and confirm its data handling is disclosed, not just your own.