Privacy Policy

Last updated: September 2026. This policy describes how Pollify handles data when you install and use it in your Slack workspace. Pollify is designed to keep very little data — if anything can live inside Slack, it stays there.

What we store

When you install Pollify, Slack runs an OAuth handshake and we persist a minimal installation record so the app can act on your behalf later. That record is stored in the MongoDB database the self-hosted server connects to and includes only what Slack provides in the OAuth response:

• Your workspace (team) and enterprise identifiers
• The app's Slack identifiers
• A bot access token and its scopes, used only to open the /poll modal and post polls to the channels you pick
• Timestamps from Slack's installation metadata

There is no account, no profile, and no billing data. We never ask for your email and we never combine installation data with anything else.

What we do not store

Poll questions, choices, and votes are never sent to or stored on our servers. Poll content is written by the bot directly into your Slack message history, and votes are tracked by appending voter mentions to the poll's blocks. All of it lives in Slack's own infrastructure and is governed by Slack's privacy policy and your workspace's data controls.

How we use what we keep

The only use of stored data is making the app work: recognising who is running /poll, authenticating the request with Slack, and posting the finished poll to the channels you selected. We do not read, aggregate, or analyse your polls.

Sharing

We do not sell, rent, or trade data to anyone. Data is only transmitted to Slack in order to respond to commands and deliver messages — that's the operation of the service itself, not sharing.

Retention and deletion

Installation records stay only as long as the app is installed. If you remove Pollify from your workspace, the installation record can be deleted, and any of our requests to Slack will stop immediately. To have your workspace's record removed, reach out through the support page or open a GitHub issue — we'll delete it promptly.

Security

Bot tokens are the keys that let Pollify post on behalf of the workspace. They are stored in the MongoDB database configured by the operator, and access to that database should be restricted to authorised administrators. Because Pollify is self-hostable, you control exactly where this data lives.

Changes to this policy

If this policy changes materially, the "last updated" date above will be revised and the homepage and install page will note it.

Contact

Questions about this policy or your data? Open a GitHub issue and we'll help.