slack

What Deemerge does

Deemerge reads messages from the Slack channels you explicitly select and identifies the business situations inside them — a request waiting for a reply, a deadline someone committed to, a decision that's stalled, a question that didn't get answered. Each situation becomes a JOB on the dashboard of the person who needs to act on it.

A JOB is a specific, named item with an owner, a link to the source Slack message, and a suggested next action. It is not a sentiment score and not a vague "insight." Each person sees only the JOBs assigned to them.

How Deemerge behaves in your workspace

After install, a workspace admin chooses which channels Deemerge tracks. Until a channel is selected, nothing is read. After selection, the admin invites the Deemerge bot using /invite @deemerge.

When Deemerge processes a message it runs in the background. It does not post in the channel. It does not @-mention anyone. The only signal is JOBs appearing on the relevant user's dashboard.

Deemerge posts in a channel only when a user explicitly clicks "Reply in Slack" from their dashboard. The message posts as the Deemerge bot, with attribution to the user who triggered it — e.g., "Posted by Deemerge on behalf of Sarah Chen." Deemerge never impersonates a user.

What permissions Deemerge asks for, in plain language

When a workspace admin installs Deemerge, Slack shows the standard authorization screen. Here's what each permission means and why we need it.

Slack permission

What it means

Why Deemerge needs it

channels:history

groups:history

Read message content in public and private channels

The core function. Deemerge reads messages only in channels you have explicitly selected and invited the bot to.

channels:read

groups:read

See the list of channels in your workspace

So you can choose which channels to track. We see names; we read no content until you select and invite.

chat:write

Send messages as the Deemerge bot

Used only when a user clicks "Reply in Slack" from their dashboard. Posts as the bot with user attribution.

users:read

users.profile:read

See names, emails, profile info for workspace members

So Deemerge knows who sent each message and who it's addressed to — how JOBs get routed.

Deemerge does not request: files:read, im:history, mpim:history, admin.*, or any user-token scopes.

Installing Deemerge

Click Add to Slack

A workspace admin clicks the button above. Slack shows the authorization screen with the permissions listed.

Sign in to Deemerge

After authorization, you're redirected to deemerge.ai. If you don't have a Deemerge account yet, you'll be prompted to create one. Auth is handled by Clerk — email, phone, or passkeys.

Select channels to track

From the dashboard, choose which channels Deemerge should track. Everything is unselected by default.

Invite the bot to each selected channel

In each selected channel, run /invite @deemerge. Until the bot is invited, Slack delivers nothing.

Wait for initial processing

JOBs appear on each user's dashboard within a few minutes.

The privacy boundary

We get asked this a lot, so we'll be explicit.

Deemerge can see

Messages in channels you selected and invited the bot to
Names and profile info of workspace members
The list of channels in your workspace

Deemerge cannot see

Direct messages between any users
Group DMs (multi-party IMs)
Channels not selected on the dashboard
Channels the bot has not been invited to
Files (we don't request files:read)

Deemerge will not

Post in a channel unless a user clicks an explicit action from their dashboard
@-mention users in channels
Auto-join channels — a channel admin must /invite the bot
Impersonate users — Deemerge posts as itself, with attribution

How AI is used, and what we send

Providers

Primary processing on Google Gemini. Fallback on additional US-based providers including Hugging Face. All inference endpoints are US-hosted.

Anonymization before AI

Names, emails, and phone numbers are replaced with tokens before any content reaches an AI provider. The AI sees the structure and substance — not the identities.

No training on your data

We use API endpoints that contractually prohibit training on submitted data. We do not train any in-house model on customer Slack content.

Accuracy

Like any LLM-driven system, Deemerge can occasionally generate inaccurate summaries. Every JOB links back to the source Slack message so the user can verify before acting.

Where data lives and how long we keep it

Infrastructure

AWS, United States. Encrypted at rest and in transit (TLS 1.2+).

Raw Slack content

Retained 24 hours, then deleted.

Derived insights (JOBs)

Retained per your tenant's retention policy, configurable from the dashboard.

On uninstall

Ingestion stops immediately. All derived data deleted within 30 days.

Individual deletion requests

Completed within 30 days via deemerge.ai/contact · GDPR Article 17.

Full privacy policy: deemerge.ai/privacy-policy

For Slack workspaces

Turn Slack conversations into a clear list of what each person needs to act on.