App Store and Google Play
Listing help, accepted against a checklist
We help submit your app to the App Store and Google Play: material pre-check, store listing, privacy labels, Data Safety, TestFlight and closed-testing notes. The account stays yours. No approval promise.
Guide library
Collaborate with member invites—not account passwords
Give Goee a identifiable member role. Revoke access when materials work ends. Do not send developer account passwords in chat.
Data Safety must match your SDK inventory
Selecting “no data collected” while ad or analytics SDKs are in the AAB is a common paperwork mismatch. List SDKs and what they actually read, then complete Data Safety.
Demo accounts must not expire during review
Test accounts, verification codes, and membership must last through review wait time. When accounts expire, reviewers only see the login screen.
Do not guess on iOS export compliance
Answer encryption questions from this build’s facts. If unsure, pause—do not pick the convenient option just to submit faster.
Do not submit machine-translated privacy labels as-is
Nutrition labels and Data Safety wording must match facts in your privacy policy. Machine translation that turns “device ID” into another data type is a different declaration.
Don’t mix What’s New with promo copy
What’s New covers this version’s changes. Promo text covers still-valid campaigns. Expired prices must not remain in screenshots or promo text.
Dual-store listing: one product story, two forms
Title and feature copy can share one set of facts. Privacy labels, Data Safety, screenshot specs, and rating questionnaires still differ on Apple and Google.
How to explain the paywall in Review Notes
When reviewers hit a paywall, notes must spell out how a demo account reaches purchased or unlocked state. “Full feature access” alone leaves them on the payment screen.
Service pages in Chinese carry the full checklist. English, Japanese, and Korean guides are the same library entries as on the source site.