Branded app

Taking a Kajabi Branded App to the App Store and Google Play

The deployment path used for a multiplatform retail app submitted to both stores this summer, applied to a Kajabi Branded App build. Each step is the client-facing checklist; the declarations table is prepared before the build lands so review starts the same day.

Accounts — Apple Developer Program (organization, D-U-N-S on file) and Google Play Console (organization, verified identity); Branded App enabled on the Kajabi plan.
Identity — App name, bundle identifier and package name, icon set, splash, store screenshots per device class, privacy policy URL on the site.
App Store Connect — Upload build, age rating questionnaire, App Privacy labels, sign-in and demo account for review, export compliance, review notes.
Play Console — App signing, Data safety form, content rating questionnaire, target audience, ads declaration, listing, closed testing track before production.
Submit and monitor — Both reviews submitted the same day; rejection reasons answered with evidence rather than blind resubmission.
Handover — Client owns both developer accounts; credentials, certificates and listing copy documented in their account.

Store declarations prepared in advance

App Privacy (Apple)	Contact info (email), user content (course progress, community posts), identifiers (user ID); none used for tracking
Data safety (Google)	Personal info and app activity collected; encrypted in transit; deletion available on request
Age rating	4+ / Everyone unless course content sets otherwise
Sign-in for review	Demo student account with one enrolled course and one community post
Export compliance	Standard encryption only (HTTPS); no custom crypto
Content rating (Google)	IARC questionnaire completed from the course content inventory

Declarations mirror the ones filed for a multiplatform retail app (App Store Connect upload, age rating, App Privacy, review submission; Play Console signing, data safety, content rating, listing, release).