// tool reference · Platform & Learning
Quantum Vault Free
Zero-knowledge AES-256-GCM text encryption in your browser.
What it does
Client-side cryptographic utilities for encrypting a value you need to move safely.
When to use it
- Sharing a secret out-of-band; demonstrating encryption mechanics.
Inputs
Field names are the actual form parameters, verified against source.
| Field | Type | Required | Notes |
|---|---|---|---|
| data | textarea | required | The data. |
| passphrase | password | required | Passphrase. |
| mode | select | optional | Encrypt or decrypt. |
What you get back
Ciphertext or plaintext.
Worked example
Input
data = API_KEY=sk_live_abc123 passphrase = ****** mode = encrypt
Output (abridged)
ENCRYPTED gAAAAABm...[ciphertext]...9tQ== Authenticated encryption: tampering is DETECTED on decrypt rather than silently producing wrong plaintext. Send the ciphertext and the passphrase through DIFFERENT channels. Both in one Slack message is the same as sending plaintext. There is no recovery. Lose the passphrase and the data is gone -- that is the guarantee, not a limitation.
How it works
Authenticated encryption. Lose the passphrase and the data is unrecoverable — that is the point.
Limits
Read live from the platform configuration.
| Rate limit | 20 requests / 10 minutes |
Limitations — what it does not do
Not key management. For anything long-lived or shared across a team, use a real secrets manager -- this is for moving one value safely, once.
Privacy
Nothing is stored.
Standards
AES-GCM