How Key Robot keeps your keys safe

Updated October 2026

Key Robot never stores your API keys. Your browser locks each key and saves it straight into your own GitHub, so our server has nothing to steal.

This page explains what that means, step by step.

Where your keys live

Your keys live in two places you already control. One is the encrypted GitHub Actions secrets of your own private robot repo. The other is where your app reads them, like your Netlify site settings.

When you connect a service, your browser encrypts the key with your robot repo's own public key before it leaves the page. Only GitHub can open it, and only inside your robot's run.

What our server keeps

Our server keeps key names, like RESEND_API_KEY, plus dates and whether each change worked. It never keeps a key value. Sign-in codes, sessions and AI tool access are stored only as one-way hashes, so a copy of our database could not sign anyone in.

The full list is in our privacy policy.

How the robot stays safe

• It runs as a GitHub Action in your own account, with the smallest permissions it needs.
• The outside code it uses is locked to exact versions, so a changed update cannot slip in.
• Before it deletes an old key, it checks that your app still works with the new one.
• It only deletes keys it made itself, in the account it manages. It never touches a key another app of yours still uses, unless you press Kill it now.

We test this with 8 checks on every service. Those checks caught a bug in our own code where Kill it now kept a leaked secret working as a backup value. We fixed it before launch.

If a key leaks

Press Kill it now. The robot makes a new key, puts it in your app, and deletes the leaked one, even if the app check fails. We timed it on our own demo app on October 23, 2026: 82 seconds from pressing the button to the old key being dead.

Read what to do right after a leak.

AI tools and the hosted MCP server

AI coding tools can connect to Key Robot to check your robot and start it. Each tool must sign in with your email code and ask before it changes a key. You can see every connected tool on your dashboard and disconnect it at any time. No tool can ever read a key, because our server does not have one.

If we shut down

Your robot keeps running. It lives in your GitHub account and does not need our server to change your keys.

Report a problem

Email hello@rotatekeys.app. We aim to reply within 2 business days, we fix confirmed problems first, and we credit you if you want.