Day one: confirm you really are owner

Log into Play Console on your own device and network, open Users and permissions, confirm you are owner and screenshot the full member list. If you see unknown members, ask where they came from; unexplained ones should be removed at a suitable time.

  • Compare account type, create date and apps with the written sheet
  • Confirm developer verification and the policy status page have no open items
  • Write every difference down and keep the chat history

Days one to two: recovery and two-step

Replace the Google account's recovery email and phone with yours and set up two-step verification again: bind your own device, save new backup codes and invalidate old ones. Then sign in from another device to confirm the flow is complete.

If the Google account on the developer profile is not dedicated to this business, consider moving to a dedicated account via the official owner flow to avoid mixing with personal mail and other services.

Also useful in this topic cluster:

Days two to three: payments and policy

Check the payments profile entity, status and payout method; confirm no restrictions or open tax or verification tasks. Then open the policy status page for past warnings or limits. For accounts with apps, check each app's status individually.

CheckWhereWarning sign
Payments profileSettings → Payments profileUnexpected entity or restricted status
Policy statusPolicy and programs → Policy statusUnresolved warnings
Developer verificationSettings → Developer accountPending verification tasks
App statusAll apps listRemoved, suspended or limited

Days three to five: keys and test upload

  1. For accounts with apps: confirm each app uses Play App Signing
  2. Reset or re-register the upload key via the official flow so only you hold it
  3. Upload a test AAB to the internal track to prove uploads work
  4. Check target API level and warnings; legacy apps are likely behind
  5. Back up the keystore and passwords in at least two secure places

Details are in the Play App Signing and upload key guide.

bash
# Compare your upload key fingerprint with the upload certificate shown on Play Console's App signing page
keytool -list -v -keystore upload.jks -alias upload | grep -E "SHA1|SHA256"

Days five to seven: store and compliance data

Update the listing's developer name, contact email and website to yours; check whether developer details in the privacy policy and data safety form need updating; recheck content rating and target audience for legacy apps.

For a fresh account start planning tests and releases now: personal new accounts schedule closed testing (see that guide); restricted categories verify category requirements first.

End-of-week acceptance

  • You control owner, members, recovery info and two-step verification
  • Payments and policy status have no unexplained anomalies
  • The upload key is confirmed and a test upload succeeded
  • Handover records, account sheet and screenshots are archived
  • Any leftover issues from the other side have a written resolution

Put this acceptance in your team docs so staff changes can repeat it.

Related reading:

Related

Related desks