Safety

It sits in a grey area. Google's Developer Distribution Agreement ties an account to one verified owner and restricts sharing or transferring account access. Publishing through someone else's account does not get an app removed by itself, but the listing legally lives under their verified identity, and Google can act on the account if its policies are broken.

A verified publisher is an established operator with a real track record, clear terms and a contract — not a stranger in a chat group. It matters because your app (and sometimes your identity) is exposed to their reliability. ConsoleMint runs a different model again — it is an app monetization company that builds, publishes and maintains its own Android apps and shares the ad revenue with the publishing partner whose account distributes them — but the same tests apply to anyone you deal with: written terms, scoped access and a track record you can check.

Not legitimately. Google has no feature to sell or transfer ownership of a developer account. A “sale” is really handing over the login to a personal Google identity — which you can never truly own, and which Google can freeze the moment re-verification does not match the person operating it. The supported route is Google’s official app transfer, which moves a listing rather than an account.

Because there's no clean way to do it. Selling means sharing a full Google login — Gmail, Photos, Contacts and more. Even deleted data can be recovered, and the original owner can reclaim the account at any time, taking your apps with them.

No. Google's account-recovery and data-retention systems mean traces can be recovered after deletion. Selling exposes your private life to a stranger and never fully transfers control. If you want the account to earn without giving it away, keep ownership and work with a publishing partner instead — see how Android app ad revenue sharing works.

It works in two halves. ConsoleMint designs, builds, publishes and maintains the Android apps and runs the ad stack that turns installs into revenue; the publishing partner — a developer or business whose Google Play account is in good standing — distributes them. The partner grants scoped Developer-role access only, never owner access and never a password, keeps ownership of the account permanently, and can revoke access with 30 days notice. A maximum of 10 apps go on any one partner account. See how ConsoleMint works.

Most suspensions come from policy violations — malware or deceptive behaviour, impersonation, repeated content-policy strikes, payments fraud, or breaking the Developer Distribution Agreement. A termination usually bans the underlying Google identity from Play for good, and every app on that account goes down with it. That shared-fate risk is why careful publishers prefer the live-and-transfer model over one shared account.

A policy strike is a formal warning Google issues when an app violates a Play policy, and strikes accumulate against the developer account. Enough strikes — or a single severe violation such as malware or fraud — leads to app removal and eventually account termination, which bans the underlying Google identity from Play permanently. Because every app on a terminated account goes down together, careful publishers isolate risk using the live-and-transfer model.

Yes, and it happens constantly — agencies, studios and publishers ship client apps under their own account every day. The account owner is the party Google holds responsible, so they carry the policy risk and their name appears as the developer on the listing. Do it with a written agreement covering who owns the package name, the signing key and the listing, and how the app gets transferred out if you part ways.

Buying an account is far riskier than publishing through one. A sold account still carries the seller’s verified identity, and because Google now requires ID verification tied to a real person, an account whose owner-of-record is someone else is one verification prompt away from being frozen — taking every app on it down with it. Marketplace accounts also often arrive with a hidden strike history. If you need Play access without your own verification, publishing on an established, verified account and transferring the app out leaves you with a clean account in your own name.

No — an “aged” account is the most dangerous thing to buy, because age is exactly what makes it attractive to resellers who sell the same account more than once. You inherit its invisible history: past strikes, prior rejections, and the original owner’s identity documents on file. Google can request re-verification at any time, and the moment the ID does not match the person operating the account, it is terminated permanently and every listing on it disappears together.

Freelancers generally use one of three routes: get added to the client’s console as a user with release permissions (best when the client already has an account), publish through a publisher or agency partner and transfer the app to the client at handover, or open their own account and keep client apps on it. The third is the trap — one client’s policy violation can strike an account carrying every other client’s app. Keep client work off a shared personal account.

Yes — use Users and permissions in Play Console to invite them by Google account and grant a scoped role such as Release manager (upload and roll out builds) or Store listing manager (edit the listing only). This is the sanctioned way to let a developer, agency or publisher work on your app, it leaves an audit trail, and access can be revoked instantly. Sharing your actual login is both a policy violation and how accounts get hijacked.