The Short Version
Your passwords stay in your own password vault — we never keep a copy anywhere. When one of your automations needs to log in somewhere, we borrow the password for a split second, use it once, and erase it immediately. Nothing is ever saved on our end.
The Problem With Most Automation Tools
Most automation tools ask you to hand over your passwords and store them permanently inside the tool. That creates real risk:
- If that tool ever gets hacked, every account you connected to it is exposed at once
- One breach becomes a breach of everything
- Changing a password everywhere it's stored becomes a manual, easy-to-forget chore
How We Do It Differently
We don't store your passwords at all. Every time an automation needs to log in somewhere, we reach into your own vault, grab the password for that one moment, use it, and delete it right after.
The core idea: your password lives in exactly one place — your own vault. The only other time it exists anywhere is for a few seconds while a task is actually running, and then it's gone.
How It Actually Works
Your Automation→
Security Checkpoint→
Encrypted Connection→
Password Gateway→
Your 1Password Vault
In plain terms: your automation never talks to your password vault directly. Every request passes through a locked-down checkpoint first, travels over a connection encrypted the same way online banking is, and only then reaches your vault to retrieve the one password it needs.
- Your automation sends a request — using a harmless placeholder, never your real password
- We check that the request is legitimate before it goes any further
- The connection is encrypted the whole way, so nobody in between can read it
- We confirm which vault is yours, specifically — never anyone else's
- Your real password is pulled from your vault, used once to log in, and then
- immediately deleted from memory. Nothing is left behind.
What's Protecting It, Layer by Layer
| Layer | In plain terms |
|---|
| Getting to us | Every connection is encrypted in transit, the same standard banks use (TLS 1.3) — nobody snooping on the network can read it |
| Proving it's really you | Your systems are verified before they're ever allowed to ask for a password — random requests can't get in |
| Locking the door | A private key protects every request to our servers, so only authorized requests are processed |
| Keeping clients separate | Your business is mapped to your vault only — cross-client access isn't just against policy, it's not technically possible |
| Where it's stored | Your password itself lives in 1Password, protected with the same grade of encryption used for financial and government data (AES-256) |
A Few More Things Worth Knowing
- Never kept: your password only ever exists for a moment, while it's being used — never sitting in storage.
- Only asked for when needed: not ahead of time, not "just in case."
- Walled off from other clients: there's no shared pool of passwords anywhere.
- Logged every time: there's always a record of when and where your password was used.
- Two-factor codes too: if you use them, they're generated fresh each time — never stored either.
What We Will Never Do
- ✕Store your passwords on our servers
- ✕Reuse a saved password instead of asking your vault again
- ✕Mix your credentials with another client's
- ✕Expose any of this to the open internet
- ✕Put your real password inside the automation tool itself — only a harmless placeholder ever touches that
The Compliance Basics, If You Need Them
| While it's traveling | Encrypted the same way as online banking (TLS 1.3) |
| While it's sitting still | Stored with government-grade encryption (AES-256), inside 1Password |
| Who can get in | Verified systems only, locked behind private keys and per-client mapping |
| Is there a record | Yes — every access is logged |
| Where does it live | Your own 1Password vault, wherever you already keep it — cloud or your own servers |
Bottom Line
Your password never leaves your own vault except for the split second it's actually being used — and even then, we never see or keep a copy. Nothing stored, nothing shared, nothing left behind.
