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

Who Should Control Your Android App Signing Keys?

TB
ThynkBlox Apps Team
App Engineering

Your business should control the publishing account, signing decisions and recovery arrangements for its Android app. With Play App Signing, Google holds the app signing key used for distribution, while your release team uses an upload key to submit builds. Give developers the access needed to deliver updates, with business-controlled records and recovery arrangements so another team can take over. The distinction between the keys is explained in the official Android app signing guide.

What is the difference between an app signing key and an upload key?

The app signing key signs the app installed on users' devices. The upload key signs the build submitted to Google Play; under managed signing, Google checks that submission and signs the distributed app with the app signing key. They serve separate purposes even when an existing setup uses the same key for both. See the official Play App Signing explanation.

ItemJobRecommended control
App signing keySigns the app distributed to usersGoogle under managed signing, or business-controlled custody where self-managed
Upload keySigns builds submitted to Google PlayBusiness-controlled storage, with access for authorised release work
Publishing accountControls access and publishing permissionsThe business, with individual developer invitations
Recovery recordsExplain how to restore release capabilityThe business, accessible to an authorised backup person

Treat these recommendations as an operating arrangement, not a statement about legal ownership. Your development agreement should separately describe ownership of the app, responsibility for publishing and obligations when the engagement ends.

Before assigning custody, ask the developer to identify which signing arrangement the app actually uses.

Does managed signing mean you no longer control your app?

Managed signing separates custody of the signing key from responsibility for the app.

With Play App Signing, Google protects and uses the app signing key. You cannot retrieve that private key from the service after configuration, whether Google generated it or you supplied it. A business that supplied its own key may already hold a separate retained copy. The official signing guide describes this restriction.

For a founder, the practical questions are:

  • Does the business control the publishing account?
  • Can it invite a replacement developer?
  • Can an authorised person find the upload-key records?
  • Does anyone besides the current developer understand the recovery plan?
  • Were distribution plans considered before choosing the signing arrangement?

Do not make “send me every key” the acceptance condition for managed signing. Ask for evidence of the configuration, the relevant certificates and a workable handover instead.

Include that review in your Google Play release checklist.

Who should have access to release the app?

Our recommended default is a business-controlled publishing account with named users and limited permissions.

Play Console supports access for individual apps and distinguishes testing releases from production releases. Its official permissions documentation explains which permissions allow each action.

Start with the work a person needs to perform. Someone preparing test builds may not need production publishing access. A developer maintaining one app should not automatically receive access to every app in the account.

Keep approval responsibility explicit. Decide who may prepare a release, who approves it and who publishes it. A small business may assign several responsibilities to one person, but should still record them.

Avoid sharing the owner's login as the normal working arrangement. Prefer individual invitations, review access when responsibilities change and remove access that is no longer needed.

For continuity, nominate a business-side backup person and document how they can obtain authorised access if the usual owner is unavailable.

What backup records should the business keep?

Keep a short signing register that another authorised developer can understand without contacting the original developer.

Record:

  • App identity: the app name, package name and publishing account.
  • Signing arrangement: whether Play App Signing is enabled and who configured it.
  • Key identification: clearly labelled signing and upload certificates, including their fingerprints.
  • Upload-key custody: where the protected keystore is held, its key alias and how authorised people obtain its passwords.
  • Retained signing keys: whether the business holds an original private signing key supplied during enrolment.
  • Access responsibility: who administers publishing access and who acts as backup.
  • Recovery instructions: who handles a lost key, suspected exposure or unavailable account owner.

A certificate contains public information; it is not a backup of the private key needed to sign a build. The official Android signing guide distinguishes private keys from their public certificates.

Keep secrets in protected storage. In the register, record how to access them rather than pasting passwords into an ordinary handover document.

Test the backup arrangement: ask another authorised person to locate the records and have the release developer verify that the stored upload key is usable.

What can you recover if a key is lost or exposed?

Identify the affected item before choosing a response.

Lost or exposed upload key: with Play App Signing, the documented recovery route is to generate a replacement key and request an upload-key reset through Play Console. This does not replace the app signing key. Follow the current upload-key reset instructions.

Lost self-managed app signing key: without Play App Signing, losing that private key can prevent updates to the existing app. Google explicitly distinguishes this from a recoverable upload-key loss in its signing guidance.

App signing key requiring replacement: Play App Signing supports signing-key upgrades, subject to the applicable upgrade route and device compatibility rules. Treat this as a planned change, not an ordinary upload-key reset. Check the current options for the app in the official key upgrade guidance.

Unavailable publishing account: handle account access separately. An upload-key backup is not an account recovery plan.

Name a person responsible for each scenario. Do not promise an immediate recovery or a fixed turnaround in the maintenance agreement.

What should happen during a developer handover?

Make release continuity part of the handover acceptance criteria.

  1. Confirm account control. Have the business representative sign in and review authorised users.
  2. Review the signing register. Identify each key and certificate without relying on filenames alone.
  3. Verify protected storage. Confirm the incoming team can obtain the upload key through the agreed process.
  4. Prepare a test update. Have the incoming team submit an authorised build to a testing track.
  5. Check the result. Verify the update on a device and test the app's main functions.
  6. Close outgoing access. Remove permissions and shared access that the former team no longer needs.

If custody is uncertain, consider replacing the upload key through the documented reset process. Do not replace it automatically just because a developer changes.

Record who owns the next release and who handles urgent fixes. Our guide to what app maintenance involves after launch helps define that continuing responsibility.

Which common mistakes should founders avoid?

Asking only who has “the key”. Ask which key, what it does and how its identity was verified.

Treating a downloaded certificate as a private-key backup. Request a clearly labelled inventory and evidence that the necessary private key is usable.

Accepting source code as the entire handover. Include publishing access, signing records and a demonstrated test release.

Leaving all knowledge with one developer. Require instructions another authorised person can follow.

Assuming every signing key has a reset button. Establish the recovery route before there is an incident.

What questions do founders ask about signing-key ownership?

Should the founder personally store the upload key?

The founder should ensure business-controlled custody. Our recommendation is protected storage with documented access, rather than depending on a file on one person's laptop.

Does a new developer need a new app signing key?

A developer change alone is not a reason to change the app's signing identity. Begin with access, custody and a test release; assess key changes separately.

What if the app is distributed outside Google Play?

Review the signing arrangement before committing to another distribution channel. Ask the developer to explain how signing and future updates will work across every intended channel, using the official distribution guidance.

What should the development agreement require?

Specify business control of publishing, protected key custody, a maintained signing register, recovery responsibilities and a demonstrated handover. Make those deliverables part of acceptance.


Need help reviewing release ownership before a launch or handover? Our app development services can include publishing setup and maintenance planning.

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.