Loading...
Loading...
Safely send AWS, Stripe, or Google Cloud API keys. The link deletes immediately after viewing.
API keys are bearer tokens — anyone holding the string can act as you. A leaked Stripe live key can drain a balance, a leaked AWS key can spin up six-figure crypto-mining bills inside an hour, and a leaked Google Cloud key can exfiltrate every BigQuery dataset the project can reach. Treat the string in your clipboard the same way you would treat a wallet seed phrase.
The everyday practice of pasting keys into Slack, Microsoft Teams, or email is the single most common source of these leaks. Slack DMs are searchable forever, exported on offboarding, and routinely scraped by automated bots that watch for patterns like 'sk_live_' or 'AKIA' in public and private channels. Email is worse — most enterprise mail providers retain a copy on backup tape for years even after the user deletes the message.
PasteOnce is built for the moment when a key has to leave one machine and arrive at another. You paste, you get a one-time link, you send the link on whatever channel your recipient uses, and the moment they read it the ciphertext is destroyed on our server. Combine it with key rotation immediately after handoff, and the window of exposure collapses to minutes.
Client-side encrypted. We can't see your data.
Your data is encrypted in your browser before it leaves your device.
Messages are automatically deleted after being read once.
We never see your data. Only encrypted blobs pass through our servers.
Links work exactly once. Refresh the page and it's gone forever.
Your sensitive data is encrypted in your browser using AES-256-GCM. The encryption key is generated randomly and never sent to our servers.
Only the encrypted blob is stored in our database, with an automatic expiration time. We literally cannot read your data.
When your recipient opens the link, the encrypted data is fetched and immediately deleted from our servers using an atomic Redis GETDEL. The key in the URL hash decrypts the message in their browser.
Treat the moment you share a key as the moment its lifetime starts ticking. Rotate within 24 hours of the recipient confirming receipt, regardless of whether you trust the recipient — this makes any leak time-bounded by default.
Stripe restricted keys, AWS IAM policies with least-privilege, and Google Cloud service accounts with limited scopes mean a leaked key can only do a fraction of what a root key can do. Scope is the cheapest insurance available.
PasteOnce is for the one-time handoff. For long-lived access, sync the key into Doppler, Infisical, AWS Secrets Manager, or 1Password — never leave it pasted into another developer's notes or local .env file.
If your recipient is online and ready, choose the 1-hour expiration. The 7-day option exists for asynchronous handoffs across time zones — do not pick it as a default just because it is the longest available.
You hire a freelancer for a two-week integration. PasteOnce a restricted test-mode key with the smallest scope they need. When the contract ends, rotate. No record exists in any chat tool, no key sits in their email.
An on-call engineer needs a service-account key to deploy a fix. The senior engineer pastes the key, sends the link via SMS (out-of-band from Slack), the on-call reads, fixes the bug, and the key is rotated by morning standup.
A SaaS vendor needs your API key to configure their webhook. Send via PasteOnce, restrict the key to their IP range in your provider's console, and revoke if the integration ever gets terminated.
For long-lived access, always prefer a shared secret manager — the recipient pulls the key from the vault directly. Use PasteOnce only when there is no shared vault in place yet, or for the one-time handoff that bootstraps that vault.
Yes — PasteOnce is a free-form text container, so multiple keys, environment lines, or labeled fields all work. The encrypted blob is opaque to us. Just keep the total under 500,000 characters.
We do not store any log that ties your IP to a note ID. The rate-limit map is in-memory and per-instance only — it resets on cold starts and does not persist anywhere.
No — the link is single-use by design. If three people need the same key, create three separate links. This also gives you per-recipient revocation if one link goes unused.