How the ConsoleMint publishing partnership works

Updated 13 August 2026 · ConsoleMint Team

Does ConsoleMint need Admin access?

Yes. ConsoleMint asks for Admin access to your Google Play developer account, granted by you from your own console under Users & permissions. We say that plainly instead of dressing it up, because Admin is the level that lets us create releases, manage store listings, answer policy notices and run the ad stack on the apps we build for you. Anyone offering to publish and monetize apps on your account while claiming they need less than that is either misinformed or not telling you the whole truth.

What Admin is not is ownership. There is no such thing as “owner access” in Google Play Console. Ownership is fixed to the Google account that registered the developer account, and there is no permission checkbox, role or invitation anywhere in Play Console that transfers it. An Admin cannot remove the owner, cannot transfer the account, and cannot change who it is registered to.

Do not take our word for it — test it yourself in five minutes. Open Users & permissions, invite a second Gmail address that you own, give it the Admin role, then sign in as that account and try to remove the owner. Play Console will not let you. That is the entire safety argument, and you can verify it before granting anything to us or to anybody else.

And it stays revocable for the entire life of the partnership. The button that removes us sits in your console, not ours — it takes about ten seconds and needs no cooperation from ConsoleMint. The exact clicks are in how to add and remove a user in Play Console, and the risk side is spelled out in is a publishing partnership safe for the account owner.

What does ConsoleMint actually do?

ConsoleMint does both halves of app monetization. We design and build Android apps, write the store listings, publish them, ship updates, keep them compliant with Google Play policy, and run the advertising stack — mediation, fill and eCPM optimisation — that turns installs into revenue. The publishing partner supplies the developer account that distributes them.

What are the four stages of a publishing partnership?

Four stages, in order: review, plan, access and build, then payouts. Stage one takes 24–48 hours. Stages two and three are a single onboarding conversation plus a few clicks inside your own Play Console. Stage four repeats every month for as long as the partnership runs.

1. Apply, and we review the developer account. Send us the account details through the application form. We check its standing, age and history so we can size the app plan realistically. The review takes 24–48 hours, and there is no obligation at the end of it.
2. We scope the app plan and the terms. You get a written plan: which apps we intend to publish and in what order, the payout structure, the fixed ramp-up figure and when it is paid, and the performance schedule that converts it into a revenue share. Nothing is granted until you accept it.
3. You grant Admin access, and we build and publish. Inside Play Console you invite ConsoleMint through Users & permissions and grant the Admin role — the level needed to create releases, manage store listings and run the ad stack. No password changes hands, and ownership does not move, because Play Console has no owner access to move. The role is revocable by you at any moment. From there we own the product work end to end: code, store listing, releases, updates, data-safety declarations, policy compliance and the ad stack.
4. Payouts land between the 1st and the 5th. Paid by UPI or bank transfer with an earnings statement each cycle. The payout is fixed during ramp-up and steps up onto a revenue share as installs and ad revenue become real.

What does the partner actually have to do?

Nothing technical. Partners do not write code, design screens, write listings, upload releases, answer support tickets, buy installs or manage ad networks. The only actions asked of a publishing partner are granting Admin access at the start, keeping the developer account itself in good standing, and confirming payout details.

• No development work. The apps are built and maintained entirely by ConsoleMint.
• No marketing spend. Partners are never asked to fund installs, ads or anything else.
• No support load. User reviews, crash reports and policy correspondence are handled on our side.
• No account fees. Your existing Google Play developer registration is all that is required.

What can a partner see and control?

Everything. It remains your developer account, so you can open Play Console at any time and see every app, every release, every store listing, every policy notice and every review. Account ownership stays with you permanently, the permissions you granted can be edited or withdrawn by you, and you never hand over a password. Admin access changes none of that — an Admin cannot remove the owner, cannot transfer the account, and cannot change who it is registered to.

How many apps get published on one account?

A maximum of 10 apps per partner account. That ceiling is deliberate — it keeps publishing volume on any single account at a healthy, normal level rather than the bulk-publishing pattern Google enforces against. As an account matures we either publish additional apps up to that ceiling or transfer existing apps across, so total revenue keeps compounding without breaching it.

How and when do partners get paid?

Payouts run on a fixed monthly cycle, processed between the 1st and the 5th, by UPI or bank transfer, with an earnings statement each cycle so you can see what the apps generated. The first payout begins from the month the first app goes live on your account.

Why is the payout fixed at first and a revenue share later?

Because a brand-new app earns close to nothing on day one. Installs, ad impressions and eCPM all take months to build. Rather than make the partner wait through that, ConsoleMint carries the ramp-up risk and pays a fixed monthly amount from go-live. Once the apps genuinely earn, the payout converts into a share of that revenue.

For a newer personal developer account, the staged structure looks like this. The first phase is the fixed guarantee; every stage after it is performance-driven and depends on installs and ad revenue, not on a promise.

Established and organization accounts are structured differently: because they reach install scale faster, they are paid per app on a per-year basis, in the region of ₹5,000–7,000 per app, per year, with a publishing cadence of roughly 3–5 apps a week. You can model your own case with the earnings calculator, or read the detail in how the ad revenue share works.

How do you end the partnership?

You remove ConsoleMint’s Admin access from Users & permissions in your own Play Console — the technical control never leaves you. The written agreement asks for 30 days notice so live apps can be transitioned or transferred off cleanly rather than abandoned mid-release. Your account, and its ownership, stay yours throughout and afterwards.

If you want the risk side spelled out before you decide, read is a publishing partnership safe for the account owner and where this sits with Google Play policy.