Your employees send anonymous questions and choose where they go — straight to HR, or to a public channel where an expert can answer. Either way, no one knows who asked.
Anonymity in HushAsk is cryptographic — not a policy promise.
Every question starts the same way: your employee asks anonymously, then chooses the destination — HR for sensitive issues, or a public channel where your team can weigh in. If you want to share the answer with the whole team, it gets saved to Notion. The asker stays anonymous.
Your employees message HushAsk directly or use /ha from any channel. HushAsk hashes their identity and presents two routing options — Confidential or Open. Employees choose where it goes. Their name never appears. They can edit or retract their message any time before you reply.
When a public thread wraps up, it can be saved to Notion with a summary title. The Q&A becomes a searchable entry in your knowledge base — ready to surface the next time someone asks the same question.
For a full guide, visit the Help Center.
Clean enough for your IT department. Trusted enough for your most sensitive questions.
Sender identity is SHA-256 hashed before anything is sent or stored — not even admins can trace a message back to its author. What's hushed, stays hushed.
Your employees message HushAsk directly or use /ha from any channel. No new apps, no onboarding flows. Slack is already open — which means HushAsk is too.
Your employees choose where each question goes — HR for sensitive issues, or a public channel for general ones. Nothing is routed without their input.
When a public thread wraps up, it can be saved to Notion with a custom summary title. Do it consistently and your Q&A archive grows automatically.
Channel configuration, Notion connection, and routing settings are all managed from the App Home — visible only to admins. No dashboards. No engagement scores. No feature you didn't ask for.
Installs like any Slack app. Uses Slack's existing permission model for access control. Works in public channels, private channels, and messages to the app.
Anonymity in HushAsk is cryptographic — not a policy promise.
Your Slack user ID is passed through SHA-256 with a private per-deployment salt before anything touches the database. The original ID is discarded immediately. It cannot be recovered.
Routing data used to deliver admin replies is minimized and not linked to your identity in our database. No lingering link between message and sender.
Note: Slack's audit log (available on Enterprise Grid plans) contains messaging metadata separately from HushAsk. Full details in our privacy policy.
Message bodies are stored only in the database for delivery and optional Notion sync. They are never written to server-side log files or monitoring systems.
For a full technical explanation, see how identity hashing works.
Anonymous questions. Honest answers. Nothing traced back.
Add to Slack