Developer resources

What to prepare before applications open.

The best audit is the one made boring by clear architecture, direct pricing, minimized data, and complete evidence.

The six Clean Play Standards documentsA fanned stack of six PDF documents: the Legal and Governance Pack, the Brand and Certification Mark Guide, the Badge and Certification System Spec, the Developer Implementation Guide, the Audit Manual, and Standard 1.0 for Mobile Games on top.PDF · REFERENCELegal & Governance PackPDF · REFERENCEBrand & Certification Mark GuidePDF · INTEGRATIONBadge & Certification System SpecPDF · INTEGRATIONDeveloper Implementation GuidePDF · REVIEW METHODAudit ManualPDF · NORMATIVEStandard 1.0 — Mobile Games9

Prepare these first

Complete inventories prevent surprises.

  • SDK and service inventory with versions, data, purpose, retention, and subprocessors
  • Data flow, permissions, accounts, and deletion
  • Purchase catalog, currencies, random rewards, competition, timers, and events
  • Notification catalog and subscription flow
  • Remote flags, experiments, regions, server states, and test access

Never send casually

Minimize sensitive evidence.

  • private signing keys or passwords
  • production credentials or database exports
  • player/customer records or child data
  • unredacted support conversations
  • third-party confidential material without authority