Back to all posts
App Ownership7 min read·October 25, 2026

Who Should Own Your Google Play Developer Account?

TB
ThynkBlox Apps Team
App Engineering

Your business should normally own and control the Google Play developer account used to publish its app. Give your agency or developers individual access for the work they need to do, while keeping account identity, recovery and key decisions with the business. Agree on this before publishing: account control should survive a change of developer.

What does owning the developer account mean?

For this decision, ownership means practical control of the publishing account: who establishes its identity, controls its main sign-in and recovery methods, receives important notices, and decides who gets access.

That is separate from ownership of the source code, designs, brand and customer data. Put those rights in your development agreement. Access to a publishing account should not be treated as a substitute for an agreement about the app itself.

Aim for a clear arrangement: the business controls the publishing account; the agency supplies development and release services. Neither side should need to guess who can authorise a release or restore access.

Make account setup part of your Google Play release checklist, alongside testing, store content and release approval.

Whose identity should the account use?

Use the identity of the person or organisation that will actually publish and take responsibility for the app. Avoid using an agency's details simply because its team is completing the setup.

Google Play distinguishes personal and organisation developer accounts, with verification requirements that depend on the account type. See the official account information requirements.

Choose the type that matches your circumstances and check the current requirements before registering. Do not assume that a brand name alone establishes an organisation's identity.

For a business-owned app, nominate someone within the business to oversee registration and retain the records. The agency can guide the process, but the business should understand what it is submitting and which details will identify the publisher.

If you are an individual founder, plan how account control will be handled if you later form a company, sell the product or appoint someone else to run it. Check the available process before promising that a change will be straightforward.

What access should an agency receive?

Start with the work the agency must perform, then grant the narrowest permissions that support it.

Google Play provides permissions for invited users, including access scoped to particular apps and broader account access. Check the current permission descriptions before assigning them. See the official user and permissions guidance.

The following table is a recommended division of responsibility, rather than a list of platform role names.

ResponsibilityRecommended business roleRecommended agency role
Account identity and recoveryControl and maintainHelp with setup
App builds and release preparationSet acceptance criteriaPrepare and upload
Production releaseName the final approverPublish when authorised
Store listing contentApprove claims and brand detailsDraft and maintain
Policy declarationsConfirm business factsExplain and prepare responses
Financial informationRetain oversightAccess only when necessary
Adding or removing usersApprove accessRequest access for named people

An agency maintaining several apps should receive access only to the apps it manages. A developer preparing builds may need different permissions from someone handling store copy.

How should recovery access be organised?

Treat recovery as a business continuity task. Decide how the business would regain access if the person managing the account became unavailable.

Use a business-controlled sign-in where appropriate, keep recovery details current, and document who is responsible for maintaining them. Avoid making a departing employee's personal phone or an agency-controlled inbox your only recovery route.

Enable the account's available security protections and store recovery material securely. Do not circulate passwords or recovery codes in project messages.

Keep a short account register covering:

  • Who controls the primary sign-in.
  • Who maintains recovery email and phone details.
  • Who receives account and policy notices.
  • Who can manage invited users.
  • Where registration and verification records are stored.
  • Who takes responsibility when the usual account contact is unavailable.

Invited access and account recovery serve different purposes. Confirm which actions another authorised person can actually perform before relying on them as your backup.

What should happen when the agency leaves?

Define the departure process in the original agreement. A useful handover should leave the next team able to maintain and release the app.

Ask for the source code, build instructions, release history, store assets and an inventory of services the app depends on. Record how signing is managed and who controls the relevant credentials.

Publishing access alone is not a complete handover. The next team also needs enough information to understand the current release and prepare an update.

Use this departure checklist:

  • Confirm that the business can access the publishing account.
  • Give the incoming team the permissions it needs.
  • Have that team prepare and validate a build.
  • Transfer agreed documentation, assets and service access.
  • Resolve outstanding releases and policy notices.
  • Remove outgoing users when their work ends.
  • Rotate shared credentials and secrets where appropriate.

Our guide to what app maintenance involves after launch helps define the work that needs a new owner after handover.

What if the app is already in the agency's account?

First establish the facts. Confirm which account publishes the app, what access the business has, and what your agreement says about control and handover.

Then check whether an app transfer is available for your situation. Google Play has an app transfer process with eligibility requirements and preparation steps; a transfer should not be assumed to be available for every app or account. See the official app transfer guidance.

Before agreeing on a transfer plan, review the source and destination accounts, signing arrangements, connected services and any unresolved account issues. Check separately what happens to reports, payment arrangements and service integrations. The same guidance notes that some reports do not transfer and that integrated services must be reconfigured. Our guide on transferring an app to another Google Play account covers the preparation in more detail.

Do not promise a completion date until the requirements are understood. If a transfer is unavailable, investigate the supported options before making changes that could affect existing users.

What common mistakes should you avoid?

Letting convenience decide ownership. Publishing through an agency's existing account may feel quicker. Decide whether that arrangement supports your long-term control before accepting it.

Sharing one login. Prefer individual access so permissions can be reviewed and removed person by person.

Giving everyone broad access. Match access to responsibilities, including temporary contributors.

Ignoring notices after launch. Name someone in the business to monitor publishing communications even when an agency handles maintenance.

Treating transfer as a guaranteed exit. Check eligibility before making transfer a contractual promise.

Assuming the account proves ownership of everything. Cover code, designs, data, service accounts and handover obligations separately.

When might a different arrangement make sense?

The client-owned account recommendation assumes the client business is the intended publisher.

A different arrangement may fit when an agency owns and operates its own product, or when a partnership explicitly appoints another party as publisher. In that case, document who controls releases, handles notices, manages customer obligations and decides what happens when the relationship ends.

The important point is deliberate agreement. The publishing identity and control arrangement should reflect the product's ownership and operating model.

What questions do founders ask most often?

Can my agency publish updates while I keep control?

That should be the intended arrangement. Give named agency users the permissions needed for release work, check those permissions against current platform guidance, and agree who authorises production releases.

Should I give the agency my main account password?

Use invited access for routine work. Keep primary sign-in and recovery control with the business, and agree on a secure process for any action requiring the account controller.

Does owning the account mean I own the source code?

Do not rely on that assumption. Your agreement should expressly cover source code, designs, assets, data and the right to appoint another developer.

What should we agree before development starts?

Name the publisher, account controller, release approver and recovery contact. Record the agency's access and departure obligations. Resolve these points alongside your app MVP scope, while responsibilities are still being defined.

Ready when you are

Planning an app of your own?

Tell us where your project is today. We will help you work out the scope before you commit to a budget.