Short answer: send it through an end-to-end encrypted link that works once and expires soon, and send any extra password through a different channel. Don't paste it into chat, email, or a ticket. If you and the recipient share a password manager, share it there instead.
Which method should you use?
Pick by who the recipient is and how long they need access.
| Method | Use it when | What stays behind |
|---|---|---|
| Shared vault in a password manager | The recipient is on your team or in your family account and needs ongoing access | The item, in a place built to hold it |
| Password manager share link | You already use 1Password or Bitwarden and the recipient is outside your account | A link that expires |
| One-time encrypted link | The recipient is a client, a contractor, a friend, or an AI agent, and needs the value once | A dead link |
| Read it out on a call | The secret is short and you can't trust any written channel | Nothing, unless someone writes it down |
| Chat, email, or a ticket | Never for the secret itself. Fine for the link | The secret, for as long as the archive lives |
Why is pasting a password into chat or email a problem?
The message outlives the need. The recipient uses the password once, and the copy stays in history, search, exports, and every connected app.
- Chat keeps it. Slack's retention docs say that on paid plans "data is kept for the lifetime of your workspace by default".
- Email has weak points of its own. NIST's digital identity guideline, SP 800-63B, bars email as a channel for authentication codes because it "may be vulnerable to" access using only a password, "interception in transit or at intermediate mail servers", and rerouting attacks. That rule is about login codes, but the reasons apply to any secret you email.
- Tickets, docs, and pull requests spread. GitHub's secret scanning docs say it scans the descriptions and comments of issues and pull requests for credentials. Editing the text later doesn't remove the old value from history.
What do NIST and CISA say about sharing passwords?
Both push you toward a password manager, and NIST says plainly that sharing happens anyway.
SP 800-63B states that people "are responsible for protecting their authentication secrets and not disclosing them to others". The same document admits the reality: "authenticator and password sharing occurs within some user groups and applications to allow individuals to share access to a digital account". It also requires services to allow password managers and says they "have been shown to increase the likelihood that subscribers will choose stronger passwords".
CISA's advice for the public is shorter: "use a password manager", which "generates, stores and even fills in all your passwords".
In practice, give each person their own login when the service allows it. When it doesn't, share through a tool built for it and change the password when the sharing ends.
How do you share a password securely, step by step?
1. If you both use a password manager, share through it
A shared vault is the best option for a teammate or family member. The secret stays in a place built to hold it, and you can take access away later.
Password managers reach outsiders too. 1Password's item sharing docs say you get "a unique link that you can send to others" for a copy of an item, and you choose "when the link expires and who it's available to: anyone with the link or only specific people". A recipient you named by email has to verify that address first. Bitwarden's Send docs describe "secure, temporary links" for text up to 1,000 characters or files up to 500 MB, and its encryption page says the key sits in the URL fragment, which "is not sent to the server".
2. Otherwise, send a one-time encrypted link
For everyone else, use a link that encrypts in your browser, keeps the key in the link, and deletes the note after it's read. With Evergist:
- Paste the password into the editor on the homepage.
- Leave the view limit at 1 view so the link works once.
- Pick a short expiry, like 1 hour or 1 day.
- Send the link.
Once the recipient opens it, the server deletes the note. How to send a private note shows what the recipient sees.
3. Split the secret across two channels
For anything important, add a password to the note and send it through a different channel than the link. Send the link by email and say the password on a call. An attacker needs both channels to read the note.
In Evergist, choose Generate one for me under Password. The password is mixed into the encryption key itself, so the link alone can't decrypt anything, and after 10 wrong guesses the note deletes itself.
4. Rotate after sharing, when you can
If the credential is for a shared account or a service key, change it once the person no longer needs it, or give them their own credential in the first place. Sharing securely limits exposure. Rotation ends it.
How do you share one from a terminal or an AI agent?
Run one command. The encryption happens on the machine that runs it, so the secret never reaches Evergist's servers in readable form.
# Share a .env file, readable once, gone in an hour
npx -y evergist create .env --views 1 --expires 1h
Pass the secret as a file or on stdin. A value typed into the command stays in shell history. How to share a .env file with a teammate has both sides of that handoff, and How AI agents can share secrets has the rules to give an agent so it doesn't print a secret into its transcript.
How can you tell if a sharing tool is private?
Check three things before you trust one. Plenty of "secure note" sites encrypt on their server, which means the operator can read your note.
- Is the key in the link after the
#? That part of a URL never reaches the server. If the link is only an ID, the server holds the key. - Does the site load third-party scripts? Analytics and ad scripts on a page that handles secrets are a bad sign.
- Is the design documented? A tool you can trust explains exactly what it stores and lets you check it. Ours is on the page that documents our encryption.
We compared eight tools, ours included, against these questions in Privnote alternatives compared.
The ten-second checklist
- Not pasted into chat, email, or a ticket
- Sent as an encrypted link, or through a shared password manager
- One view, short expiry
- Password added and sent through a different channel, for anything important
- Credential rotated when it's no longer needed
Questions
Is it safe to send a password by email?
No, not the password itself. The message sits in two mailboxes and their backups. Email is fine for a one-view link, because the link is useless after the first read.
Should you send the username and password together?
No. Send the password through the one-time link and the username or URL in the normal message. Someone who sees only one of them can't log in.
Do you need to change a password after sharing it?
Yes, when the sharing was temporary. Once the contractor finishes or the teammate has their own account, change it.
What about files, documents, or a whole set of credentials?
A one-time note holds text, up to 512 KiB on Evergist, so it covers a password, a key, or a .env file. For files and ongoing access, How to share sensitive information securely sorts the options by data type.