Privacy Policy

1. Introduction

This Privacy Policy explains how Unified ("we", "us", or "our") collects, uses, and protects your information when you use our Slack application and related services (the "Service").

2. Information We Collect

When you install and use Unified, we collect the following information from your Slack workspace:

• Workspace Information: Workspace ID, workspace name, and domain.
• User Information: User IDs, display names, and email addresses of users who interact with the Service.
• Channel Data: The Slack channels the Service can see — their channel IDs and names — and the messages posted in the public channels the app has been added to: the message text, who posted it, which channel, and when. When Unified is installed we also read the last seven days of messages from those public channels, so a new workspace has analytics from its first day rather than an empty dashboard. We read this content to produce the aggregate reporting described in section 4 — sentiment trends, frequently used words, and topic clusters. We do not read direct messages between your members; the only direct message Unified has is its own conversation with a member, which is where a Pulse survey answer is submitted.
• Interaction Data: Kudos messages, survey responses, and raffle entries submitted through the Service.

3. How We Use Your Information

We use the collected information solely to:

• Provide, maintain, and improve the Service.
• Authenticate users and manage workspace access.
• Process kudos, surveys, and dashboard analytics.
• Communicate with you regarding service updates or support.
• Send you email about your workspace and your trial — for example that a trial is ending, or that the workspace needs attention — and decide which of those messages is relevant to you from your plan, billing status, seat count and how recently the workspace was used.

We send those lifecycle emails on the basis of our legitimate interests: helping the workspace you installed get value from the Service while it is on trial. We have weighed that against your interests and rights — the messages concern the workspace you set up, they are limited in number, and a product that says nothing while your trial runs out would serve you worse than it serves us. You can object to them at any time (see section 6).

4. Data Storage and Security

• Data Residency: All workspace data we store is processed and held in the United States — our application hosting, primary database and caching layer are all located in US regions. Analytics are processed by PostHog in the United States. Transactional and lifecycle email is handled by Brevo, whose hosting and data storage are located in the European Union; when we send you email, your email address and the following information about your workspace are sent to Brevo: its identifier, name and status; its plan, billing status, seat count and trial end date; and how the workspace has been used — when it first received kudos, and when it was last active. Some other third-party processors may process limited data in other regions.
• Hosting: Our infrastructure is hosted on secure, industry-standard cloud providers (AWS, Fly.io, PlanetScale and Upstash).
• Data Retention: The following are automatically and permanently deleted once 90 days have passed since your workspace closed or its subscription ended: your workspace's member records; kudos and the reactions on them; Pulse survey responses, answers and the generated write-up and summary; topic clusters and their per-period counts; raffle leaderboard entries; report history; and the analytics we derive from your channel messages — sentiment readings and word frequencies. The deletion is a hard delete, not anonymisation, and a daily job carries it out, so it lands on the 90th day or the day after. Slack access tokens are revoked when your workspace closes, not at the end of the retention window.

What is kept after that. Nothing else is deleted on that schedule. What remains is your workspace's own account, configuration and processing records — its billing and accounting records, our security audit trail, the channel directory, its role, survey and raffle setup, and the state its analytics jobs left behind — together with the records that identify members: roster snapshots, survey send records, and the links that say which accounts belong to the workspace.

Slack event archive. The Slack events our analytics pipeline reads are stored as compressed payloads in an encrypted object store operated by Cloudflare, and compacted into analytics tables in that same storage; the sentiment readings, word frequencies and topic clusters above are built from them. This archive is held separately from the product data, it is not covered by the 90-day deletion above, and it has no automatic expiry today — so this policy states no period for it. Because that reporting is derived from the archive, deleting the reporting does not delete the events behind it, and a re-run of the analysis would rebuild it. Section 6 explains how to ask us to delete it.

5. Third-Party Processors

We may use trusted third-party services to operate the Service, including:

• Hosting and infrastructure: Amazon Web Services (AWS) and Fly.io (application hosting), PlanetScale (database), Upstash (caching, queues and sessions) — all in United States regions
• Cloudflare: Cloudflare runs the path that receives Slack events (Workers) and the encrypted object storage and analytics tables that hold the raw Slack event archive described in section 4 (R2, in a United States region). Cloudflare's Workers AI also writes Pulse's generated summary and write-up: the free-text comments in a survey window are sent for theming after figures, links, email addresses and handles have been removed, and the scorecard's own figures are sent to be described in sentences.
• Email Delivery: Brevo (for transactional and lifecycle emails) — hosting and data storage in the European Union. The data sent is your email address and the workspace information described in section 4: workspace identifier, name and status; plan, billing status, seat count and trial end date; and when the workspace first received kudos and was last active.
• Analytics: PostHog (PostHog Cloud, United States), used for product analytics and feature flags. It runs only if you accept analytics cookies. Once you are signed in, the data sent includes your user ID, name, email address, role and workspace. No third-party tracking cookies are set on Slack interactions.

We do not sell your data to third parties.

6. Your Rights

You have the right to request access to, correction of, or deletion of your personal data. To exercise these rights, or to request a full data export prior to uninstallation, please contact us at support@getunified.io.

You also have the right to object at any time to direct marketing — that is, to our use of your personal data to send you marketing and lifecycle email. You can exercise it by using the unsubscribe link in any marketing or lifecycle email we send you, or by writing to support@getunified.io. If you object, we will stop sending you marketing and lifecycle email.

7. Cookies

Our landing page at getunified.io and the Unified app both use the same cookie consent banner, and share the choice you make in it:

• Necessary cookies (session, CSRF) are always active.
• Analytics cookies (PostHog — see section 5) are opt-in and off unless you turn them on. On our public pages this data is not tied to an identity. Once you are signed in to the app, it is linked to your account and carries your name, email address, role and workspace.
• No marketing cookies are currently deployed.

You can change your choice at any time: manage cookie preferences. If you're signed in, the same control is on your profile page.

8. Security

We take the security of Unified seriously. If you discover a vulnerability, please report it to security@getunified.io.

We follow responsible disclosure practices and request:

• Give us 90 days to address the issue before public disclosure.
• Do not access or modify user data without permission.
• Provide a detailed report with reproduction steps.

Our security policy is published at /.well-known/security.txt per RFC 9116.