Slack distribution and respondent anonymity
Heads up — Slack is transport only—same encryption and access-code rules as other channels. Connect under Settings → Workspace → Slack; see Slack integration.
How Slack distribution preserves anonymity
InviziPoll's Slack integration delivers polls to respondents but is carefully designed to preserve the same anonymity guarantees as email distribution. This page explains how.
The access code boundary
When you distribute access-code-protected polls via Slack DM, each recipient receives a unique access code. The system stores a one-way hash of each code, not the code itself. When a respondent submits their answers, the submitted code is hashed and checked against the stored hashes to confirm validity — but the response record contains only the hash, not the original code, and no link back to the Slack user who received it.
This is identical to how email-distributed access codes work. The transport changes (Slack DM instead of email), but the cryptographic boundary is the same.
What InviziPoll cannot determine
After distributing a poll via Slack DM, InviziPoll cannot determine:
- Which specific Slack user submitted which response
- Whether a specific Slack user has responded or not
- Any correlation between a Slack user's identity and their poll answers
This is by design. The access code hash stored with a response cannot be reversed to recover the original code, and the original code cannot be traced back to the Slack user it was sent to — the system does not maintain that mapping after delivery.
Why reminders go to everyone
Because the system cannot determine who has responded, Slack reminders for DM-distributed polls are sent to all recipients in the original cohort. The in-product reminder flow explains that everyone in that audience is included — InviziPoll cannot filter to “only people who have not responded” without breaking the intentional separation between access codes and stored responses.
This is intentional: a system that could selectively remind only non-responders would, by definition, be tracking per-respondent completion status — which would weaken the anonymity model.
Channel announcements
Polls shared via Slack channel posts use a public response link with no per-user access codes. Anyone with the link can respond (subject to the poll's other access controls). Since there are no individualized codes, there is nothing to correlate with responses.
No response collection through Slack
InviziPoll does not use Slack to collect poll answers. There are no Slack interactive components (buttons, modals, message actions) that submit response data. Respondents always answer through the InviziPoll response page, where the standard end-to-end encryption applies.
Slack is a delivery mechanism — it puts the poll in front of people. The response path is entirely separate.
Audit trail
Slack integration events are recorded in the workspace audit log with metadata only (for example, that Slack was connected or disconnected, that a channel post or batch send completed, and counts). They do not include who received a DM or the contents of poll responses. These events help owners verify the integration is used as expected without exposing data that would weaken respondent privacy.