Scope the login, send it once through a link that burns, and rotate it when the work is done.
Give the client or contractor their own login where the system allows it, with the least access that gets the work done. A credential you can revoke on its own is far easier to retire than a shared admin password.
Send the username in the email or ticket where the conversation already lives. Keep the password for the secret link, so a message on its own is not a working login.
Paste it into the creator below. The link is encrypted in your browser and burns after the first view, so nothing usable is left in the thread.
The link works once. If they report it was already burned, someone else opened it first: rotate the credential and send a new link.
When the engagement ends, change or disable the credential. On Pro, the audit timeline shows when each link was opened, which helps when you need to say who had access and when.
No account needed. Free forever plan.
Encrypted in your browser before anything is sent. Burn after read is on for every anonymous secret.
One URL. The key after the # stays in the browser and never reaches our servers.
The first open burns the ciphertext. A second visit, by anyone, meets the destroyed page.
Browser-side encryption shipped on 29 September 2026. Secrets created before that date were stored as plaintext until they expired, and a file's name, size and type are still visible to us. Read the full security model.
The steps above cover the common case: an agency handing a client their new site's admin login, a firm giving a contractor a database or VPN credential, or an IT team onboarding a vendor. The principle is the same each time. The message in the inbox should never be a complete login, and the password should exist in only one place after it has been read: the recipient's password manager.
Email is forwarded, searched and backed up. Chat history is exported. A shared document keeps every version. A one-time link is different in kind: it carries ciphertext that only the key in the link can open, the first reveal destroys the stored copy, and a link found later leads to a burned page. With a free account you can also revoke it before it is opened, which no email can do.
Connection strings, SSH keys and .env files are credentials too. Text of any kind fits in the creator. With a free account you can attach a file, encrypted the same way, so a key file or a config travels behind the same burn and expiry controls. For keys specifically, see how to share API keys securely.
Pro, $29 a month, adds a passphrase on every secret, a custom expiry date and time, and the audit timeline that records each view, burn and revoke. See plans.