Security, Privacy, and Data Handling

If your IT, security, or procurement team is reviewing CultureBot, this page answers the questions they usually ask: what CultureBot can see in Slack, how people sign in, where data lives, and which compliance documents are available. For the full legal terms, see our Privacy Policy.

What CultureBot Can and Can't See in Slack

CultureBot cannot read your channel conversations. It does not request Slack's permission to read channel history, so it never receives, stores, or archives the messages your team posts in channels. The only messages it reads are ones people send directly to CultureBot in a DM.

These are the Slack permissions CultureBot requests when you install it, and what each one is for:

  • users:read and users:read.email: Read names, emails, time zones, and profile photos to build your employee directory and send celebrations to the right people.
  • team:read: Read your workspace name and icon.
  • channels:read and groups:read: List channels so admins can choose where CultureBot posts. CultureBot only sees private channels it has been added to.
  • chat:write and chat:write.public: Post celebrations, shoutouts, and prompts to the channels your admins choose.
  • chat:write.customize: Post with a custom name and icon, for example when an admin sends an announcement as themselves.
  • im:write and mpim:write: Send direct messages and group DMs, such as survey invitations and employee intro pairings.
  • im:history: Read replies that people send to CultureBot in their DM with it. This does not include DMs between employees.
  • files:read: Read a file an admin sends to CultureBot, such as a spreadsheet of celebration dates.
  • reactions:read: Count emoji reactions on CultureBot's own posts for engagement reports.
  • commands: Respond to CultureBot slash commands.

Slack shows this same list on the install screen, so your Slack admin can review it before approving.

How People Sign In

CultureBot has no separate usernames or passwords. Employees use CultureBot inside Slack, and the CultureBot web app signs people in with a one-time link delivered through Slack. Your existing Slack sign-in, including any SSO your company already enforces on Slack, controls who can reach CultureBot. CultureBot does not currently offer a direct SAML connection to your identity provider.

What Data CultureBot Stores

  • From Slack: Name, work email, Slack user ID, time zone, and profile photo.
  • From your admins or HR system: Optional details such as birthday, start date, department, manager, and location.
  • From using CultureBot: Shoutouts, survey responses, points, and similar activity inside CultureBot.

Data Retention and Deletion

Uninstalling CultureBot from Slack stops all messages and deactivates your workspace, but it does not delete your data. To have your company's data deleted, email support@getculturebot.com. An individual employee can also ask us to delete their profile.

SOC 2, DPA, and Security Questionnaires

CultureBot does not currently hold a SOC 2 report. Data is handled under our Privacy Policy and processed in the United States. We're happy to complete your security questionnaire and / or Data Processing Addendum.

Send either one to support@getculturebot.com.

Using Microsoft Teams?

CultureBot on Teams uses Microsoft Graph permissions instead of Slack permissions. See Getting Started on Microsoft Teams for what CultureBot can and can't see there.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us