Why keys in chat history are a real risk
Leaked chat exports and compromised workspace accounts are a common source of cloud breaches. Attackers search message history for strings like sk_live_, AKIA and BEGIN OPENSSH PRIVATE KEY. A one-time link means the key never sits in searchable history.
Even better: create a separate key per person or contractor with the smallest permissions they need, so you can revoke it alone when the work is done.
Frequently asked questions
Can I share a multi-line key like a private SSH key?
Yes. Line breaks are kept exactly, up to 20,000 characters.
Is this safe for production secrets?
The design is end-to-end encrypted and we never hold the key. Still, rotate any secret that was shared after the work it was shared for is done. That is good practice no matter how it was sent.