ShareSafeNote

How to share a password securely (and what never to do)

5 min read · updated October 4, 2026

Sooner or later, someone needs a password from you: a colleague covering your vacation, a family member who has to log into the electricity account, a technician setting up the office printer. Most people handle it in ten seconds with a text or an email. The problem is that the message outlives those ten seconds by years. This guide explains where shared passwords actually end up, which methods are worth using, and a simple routine to follow every time.

Why email, SMS, chat and sticky notes are a poor fit

The risk is rarely that someone is reading your messages live. It is that messaging is built to keep things: messages are copied, synchronized and indexed so you can find them again. Useful for a lunch invitation, a liability for a password.

  • Email: a copy in your Sent folder, another in the recipient's inbox, possibly more in backups and on every device where either of you reads mail. It is all searchable: typing "password" into a mailbox search often surfaces years of secrets, which anyone who later takes over the account inherits.
  • SMS: plain text messages are not end-to-end encrypted, often appear in full on the lock screen, and end up in phone backups.
  • Team chat (Slack, Teams and similar): history is searchable by the whole channel, exportable by administrators and reachable by connected apps. A password pasted three years ago is likely still there.
  • End-to-end encrypted messengers: they protect the trip, but the message stays in the history on both phones, and in their backups, unless you use disappearing messages.
  • Sticky notes: they show up on video calls, in photos and in plain view of passers-by.

The common thread: the secret outlives its purpose, in places you no longer control.

Inside a team or family: your password manager

If you and the other person both use a password manager, its sharing feature is the best option by a wide margin. Most mainstream password managers, such as Bitwarden or 1Password, as well as the shared groups in Apple's Passwords app, let you place an entry in a shared vault or group.

  • The password travels encrypted and never appears as plain text in a message.
  • When you change it, everyone with access gets the new version automatically.
  • You can revoke access when someone leaves the team or the project ends.
  • Autofill often means the recipient never even sees the password, and it protects them from fake login pages.

For credentials that several people need for months, this is the answer. The rest of this guide covers the cases where it isn't possible.

For a one-off: a one-time encrypted link

Often the other person doesn't use your password manager: a new hire, a relative, an outside consultant. Here a one-time encrypted link is a solid choice. With ShareSafeNote, the note is encrypted in your browser; the key goes into the part of the link after the # sign, which browsers never send to the server (see client-side encryption, explained without jargon). By default, the note is deleted from the database the moment it is read.

The result: once your colleague opens the note, the message in their inbox is just a dead link. And if they click and are told the note was already opened, someone got there first, and the password has to change. Our guide to one-time links covers this in detail.

Split the channels

Whoever holds the full link can read the note. You can, however, make an intercepted link far less useful by separating the pieces of information.

  • The link through one channel, the context through another: the link by email, and "it's for the supplier portal, the username is your work address" by text or on a call.
  • Avoid the channel you would normally have used for the secret. If someone is reading your work email, the link should not travel there alongside the account name.
  • For anything important, confirm by voice that the right person opened it.

Temporary access means a temporary password

When you give someone access for a limited time (a consultant, a house sitter, a colleague covering for you), plan the end before the beginning.

  • Prefer a separate account or guest access when the service offers it: guest Wi-Fi, mailbox delegation, a second user. You then remove the user instead of changing your own password.
  • Otherwise, change the password as soon as the access is no longer needed (set a calendar reminder the day you share it), then sign out any sessions you don't recognize.
  • Never share a password you reuse elsewhere: an attacker would try it on your other accounts.

Two-factor codes are never for sharing

The six-digit codes from an authenticator app or a text message prove that you are the one signing in, right now. Sharing one defeats their purpose. Your bank, support staff and your employer do not need it; "I sent you a code by mistake, can you read it back to me?" is a classic account-takeover scam (see how to recognize phishing links). If several people legitimately need the account, use the service's own mechanisms: multiple users, delegated access, or several registered security keys.

Remember: a password can be shared, a verification code never. Anyone asking you for one is, in all likelihood, trying to get into your account.

A safe routine

  1. Is sharing necessary at all? Would a personal account or guest access do?
  2. If you share a password manager, use it.
  3. Otherwise, create a one-time note with the shortest expiry that works.
  4. Send the link through one channel and the context through another.
  5. Confirm by voice that it arrived.
  6. "Already opened"? Change the password immediately.
  7. When temporary access ends, change the password or remove the user.

What ShareSafeNote does not protect against

A one-time encrypted link protects the password on its way and keeps it from lingering on a server. It does not:

  • verify who the recipient is: send the link to an impostor and the impostor reads it;
  • protect an infected device, or a browser extension that can read pages;
  • stop a screenshot, or the password being pasted somewhere else;
  • recover a lost link: the service never has the key.

Sharing a password well comes down to two habits: don't leave copies behind, and plan to change what you share. For a one-off handover, you can create a one-time encrypted note in a few seconds, with no account.

Share your next secret the safe way

Encrypted in your browser, read once, then gone. No account needed.

Create a secure note