A personal account belongs to one natural person, so start with that person
A Google Play personal account is registered to an individual. The legal name, address and identity verification submitted at sign-up stay attached to it, so the holder is the party the platform recognizes, not a label in a note field. Ask three things: who actually passed verification, whether that person can still cooperate if a re-verification or document request appears, and whether the login email, recovery email and recovery phone can all be handed over. If the seller cannot say who was verified, or the holder will not assist when a review comes, the real risk is not publishing but losing control of the account.
The payments profile must match the holder, or trouble appears at the first payout
The payments profile holds name and address, and for payouts it links a bank account and tax information. The usual snag is a bank account name that differs from the account holder, or tax details filed under someone other than the actual operator. For free apps without in-app purchases this stays quiet. Once you enable paid apps, in-app products or subscriptions, a mismatch can delay payouts, trigger fresh verification, or require replacing the profile. Ask the seller whether the profile is completed, whether payouts were ever linked, and what changing to your own bank account would involve, including whether the original holder must take part. Exact fields and steps depend on the Console pages at the time.
With existing apps, separate who owns the account from who owns the app
Several things need checking. The package name cannot change after publishing, so the app's public identity is fixed. On signing, see whether Play App Signing is enabled, who holds the upload key, and whether the platform's reset process is available if it is lost. Review the Users and permissions list for third-party developers or contractors still attached. If the app has in-app products or subscriptions, confirm that product setup, tester lists and order history move with the account. Also look at the privacy policy URL, contact email and developer website inside the app listing: if they still belong to the previous holder, you will need to replace them after the handover.
Older versus newer accounts: the difference is mainly the pre-production testing requirement
Personal accounts created after November 2023 must complete closed testing with a set number of testers over a set period before applying for production access. Accounts created earlier were generally not subject to the same rule. That is one practical reason people look for older accounts, but it should not be the only one. Tester counts, durations and scope have been adjusted before, so rely on the Play Console help page current at the time of purchase. What matters more is whether the account history is clean: policy warnings, removed apps, appeal records, and any restriction on the account status page. Ask the seller for screenshots of the status pages and check them yourself rather than accepting verbal assurances.
When to pause or choose an organization account instead
Some situations do not fit a personal account. The app is operated under a company and should show a company identity. Several people need long-term access and you do not want all control resting on one individual. You expect significant paid revenue that needs company banking and financial compliance. Account type generally cannot be switched between personal and organization, so a wrong choice may mean creating a new account and migrating apps, which costs far more than a few questions beforehand. A simple test: if the holder, the payout entity and the real operator of the app cannot be tied to the same party or a clear authorization, stop and sort that out before buying.