// security
Your keys, your code and your app stay in your control.
Releasing an app needs keys from Apple and Google. They stay in your own GitHub, and Push200 keeps no copy. Here is exactly where they go, and what Push200 can and can't do.
No card needed. Expo, Capacitor, React Native and Flutter apps. Works with your existing GitHub repository. Your keys stay in your GitHub.
Where your store keys go
When you add a key from Apple or Google, we check it with them straight away, so you know it works. Then it's sealed and saved into your repository's encrypted GitHub secrets. A GitHub secret is a locked value that only your builds can use. It's hidden in build logs.
Your builds run on your own GitHub account, so your keys are used there, during your builds.
We don't keep your store keys
- Your Apple keys stay in your GitHub. When you connect another app, a short job in your own GitHub seals them for that app's repository. We only pass along a sealed copy that we can't read
- The date you added each key is all we keep, so your portal can show what's connected
- An Android key we create for you is not kept. You download the only copy, and it goes into your GitHub secrets
What Push200 can reach
Only the code you choose
When you connect GitHub, you choose Only select repositories and pick your app. Push200 can't see your other repositories. You can change this or remove access in your GitHub settings at any time.
Your main branch is never changed
Each build runs on its own separate branch, built from your latest code. Your main branch stays exactly as it is.
Nothing public until you choose
Builds stop at App Store Connect or a Google Play draft. On Google Play, you give Push200 access to testing tracks only, so it can't publish to the public.
Checked with Apple and Google
Every key is checked with Apple or Google when you add it. If something's wrong, we tell you what to fix.
Protecting your Push200 account
- Your password needs at least 12 characters, with 2 numbers and 2 symbols
- Your mobile number is confirmed with a code we text you
- You can turn on two-factor login under Account. You then also enter a code from an authenticator app on your phone when you log in
- Daily build limits protect your GitHub bill if someone gets into your account
If you leave
You can delete your account under Account in your portal. Removing an app or your account from Push200 doesn't remove anything from your own GitHub repository, including the secrets and the separate build branch. You can delete those in GitHub yourself.
To remove Push200's access to your code, open your GitHub installed apps, choose Push200 Builds, and change what it can see or uninstall it.
Your next release could be one click away.
Start free with no card. Set up your first app today.
Start free