Integration

Google Play is how an Android build reaches testers and production. You paste a service-account key, and the agent prepares the release.

What it does

• Uploads a build to the track you chose.
• Rolls a release out in stages, from internal testing to production.
• Reads release status back into Selfbase.
• Rolls out only when you approve it. The agent never ships on its own.

Connecting

Open Workspace settings, then Connections, and choose Google Play. Paste a service-account JSON key from Play Console, then Users and permissions, then API access.

What each permission is for

• A service-account JSON key Acts on Play as that service account, with exactly the permissions you granted it in the Play Console.
• https://www.googleapis.com/auth/androidpublisher The scope the key is exchanged for: uploading builds and managing releases for your own apps, and nothing else in your Google account.

We do not ask for your Google account sign-in or your Play Console password.

How your credentials are held

Your credential is encrypted with a key that belongs to your workspace and stored as ciphertext. It is decrypted only at the moment it is used, and never inside a sandbox where code runs. We never log it.

Removing it

Disconnect under Workspace settings, then Connections, which deletes our copy. Delete the service-account key in the Google Cloud console to end our access immediately.

To have everything Selfbase holds about you deleted, see data deletion.

Support

Email hello@selfbase.com. Our privacy policy and terms cover every integration.