Stop Sending Passwords Over Slack: Here's What I Built Instead

We've all done it. A contractor needs access to the staging database. You open Slack, type the password, hit send. Maybe you add "delete this after" — as if that means anything. I ran into this problem on my own team. We needed to send tokens, API keys, and database credentials to contractors. Regularly. And every time, the same awkward dance: a Slack DM, an email, or — worst case — a shared Google Doc called "Credentials (DO NOT SHARE)." One day I searched our Slack history for "password" and found credentials from six months ago sitting in plaintext. Anyone with workspace access could read them. That was the moment I decided to build something. The Problem Nobody Talks About If your team uses a password manager like Bitwarden or 1Password, you're covered internally . You share a vault, everyone has access, life is good. But what about the contractor who's not in your password manager? The client's developer who needs an API key for a week? The new hire on day one, before they even ha