Skip to content

How to send a password or API key to a client without leaving a trail

Freelancers and agencies hand over logins and keys all the time. Here is a simple way to do it that does not leave secrets sitting in email forever.

The KeyValt team2 min read
Share
A paper plane icon, representing a secure handoff

You've finished building a client's website. Now you need to hand over the hosting login, the admin password, the database details and a couple of API keys.

So you write an email. Subject: "Logins". And there they stay, in your Sent folder and their inbox, for years.

The problem with email and chat

Email and chat are made to keep things. Messages get backed up, synced to new devices and forwarded. If either mailbox is ever compromised, every secret you ever sent is sitting there, neatly labelled.

What a good handoff looks like

  • The secret is encrypted before it's sent.
  • The link expires, after a time limit, after a number of opens, or both.
  • Ideally, there's a second factor, like a password you share over a phone call.
  • Afterwards, there's nothing left sitting in an inbox.

How Secure Handoff works in KeyValt

KeyValt's Secure Handoff is built for this. You pick the items to send, like logins, notes or developer secrets, and KeyValt seals them into a bundle in your browser.

Then you choose how to protect it:

  • Link with the key inside. The decryption key is placed in the part of the link after the "#". Browsers never send that part to a server, so our servers store the encrypted bundle but never the key.
  • Password-protected. The bundle is locked with a password you choose, using the same slow, guess-resistant method we use for master passwords. Share the link one way (for example, by email) and the password another way (for example, a phone call).

You can also set the link to expire after a number of hours or after a number of opens, add an access code, and revoke it at any time. After too many wrong access codes, the link shuts itself off.

If you send the link by email from KeyValt, it must be password-protected, so the email alone is never enough to open it.

Good habits for handovers

  1. Send logins and keys separately from the "here's everything" project email.
  2. Ask the client to change passwords after they receive them, especially admin ones.
  3. Give the link a short expiry. A day is usually plenty.
  4. For API keys, create a new key for the client rather than sending yours.

Secrets should travel like cash in a sealed envelope: delivered, opened once and not lying around afterwards.

Found this useful? Share it with someone who needs it.

Share

Every portal. One click. Zero sticky notes.

Start free with up to 10 portals. Upgrade when you need more accounts, devices and your team.