Launched this week
One Time Link

One Time Link

Securely share secrets in Slack with one-time links

126 followers

Visit website
One Time Link by Nurbak – Share Secrets for Slack lets teams securely share sensitive information inside Slack. Instead of sending passwords, API keys, or credentials in plain text, it creates one-time links that self-destruct after opening. Secrets are never stored in readable form, conversations stay clean, and teams reduce the risk of leaks — without changing their Slack workflows. Built for developers, DevOps, and growing teams who care about security, privacy, and simplicity.
One Time Link gallery image
One Time Link gallery image
One Time Link gallery image
One Time Link gallery image
Free
Launch tags:Slack•Developer Tools•Security
Launch Team / Built With
Anima - Vibe Coding for Product Teams
Build websites and apps with AI that understands design.
Promoted

What do you think? …

Fabián Delgado
Maker
📌
👋 Hi Product Hunt! I’m Fabián Delgado, founder of Nurbak. I built Share Secrets for Slack after repeatedly seeing passwords, API keys, and tokens being shared in plain Slack messages — and then living there forever. Nurbak lets teams share sensitive information using one-time links that automatically expire after being opened, so secrets don’t linger in channels or logs. It’s designed to be simple, secure, and easy to adopt without changing how teams already use Slack. I’d love your feedback: 👉 How do you currently share secrets in Slack, and what’s the biggest pain point for you?
Amit Sharma

This is neat... but I’m curious does the one-time links still work if someone previews it via Slack link unfurl/bots? Also any audit trail or admin controls for larger workspaces?

Fabián Delgado
Maker

@amitpsharma Slack previews / unfurling don’t expose or consume the secret — bots and link previews see nothing useful by design.

As for audit trails and admin controls: the web version already has a dashboard, and we’re exploring privacy-preserving, workspace-level metrics (counts and usage, not content or identities) for larger teams.

Happy to go deeper on the trade-offs — DM me if you want to chat.