Decide whether you are buying the account or the app
For an account that comes with an app, most of the value sits in the app: its package name, install history and ratings. So settle your purpose first. If you plan to keep running the app, every property of that app matters. If you mainly want an aged account and the app is incidental, the question flips: make sure the app is not a liability, for example by carrying open policy warnings. The same checklist carries very different weight depending on which case you are in.
Package name controls update continuity: check three things
A package name (application ID) cannot be changed after publishing, and the update path for existing users depends on it. First, confirm it fits your brand and codebase; if not, you either keep it or publish a new app, and ratings will not transfer. Second, check the signing setup. With Play App Signing, a lost upload key can be reset through the platform's process, but that requires control of the account. With a legacy self-managed key, you need the keystore and passwords delivered. Third, confirm source code and build artifacts are included. Login access alone does not let you ship a new version without them.
Read ratings by distribution and timing, not the average
The average score hides most of what matters. Look at how many ratings there are, which versions and dates attract the low scores, and whether the developer ever replied. Low scores clustered around one release suggest a fixed problem and room to recover. Low scores that persist around intrusive ads, excessive permissions or misleading descriptions often point to policy risk as well. If ratings and install counts look badly mismatched, ask the seller to explain the source, and walk away if the answer is thin, since inflated metrics can tie into manipulation violations.
Verify violation history in the policy status page and in email
Ask to view the console's policy status page together, and cross-check the developer mailbox for platform notices. You need to know whether any issue is currently unresolved, whether the app or account ever received a removal, suspension or warning, and whether appeals succeeded. A single warning that was appealed and cleared is a different risk from repeated violations of the same type. Any account-level termination or restriction record is a reason to decline regardless of how good the app data looks, because it can affect every future app. Policies change, so rely on the platform's current pages rather than the seller's summary.
Account type and verification limit what you can do with the app
Personal and organization accounts behave differently once an app is attached. Confirm the account type, whether verification is complete, how payment profile and payout details will be handed over, and whether recent testing requirements for newer personal accounts affect releases. These requirements change, so check the platform's current help pages. If the app has paid features or in-app purchases, treat merchant profile and payout ownership as a separate item to settle.
A decision rule for proceeding, conditioning or stopping
Sort findings into three tiers. Proceed: package name, signing and source are deliverable, ratings look organic, and policy status is clean. Condition: missing keystore or source, or a cleared historical warning; write the missing deliverables into the agreement before paying. Stop: account-level restrictions, abnormal rating or install data, or a seller who cannot provide read-only verification. Hand over in steps, verify first, then transfer credentials and recovery options, and re-check every console status right after handover to confirm nothing changed.
FAQ
Can I replace the app's content with my own after buying?
You can ship updates, but large changes to purpose, name or functionality may trigger review, and existing ratings will still reflect the old experience. The bigger the change, the more you should check that the store listing still matches what the app does.
Can I keep updating the app without the signing key?
If the app uses Play App Signing, a lost upload key can be reset through the platform's process, which needs full account control. With a self-managed key that is lost, you cannot update under the original package name, so weigh that carefully.