Security

What CoffeeSlack can see, and what it keeps

The short version: we see who joins, who they were paired with, and how the chat went. We never read your messages — the app doesn’t have Slack’s permission to read any channel or conversation.

On install

Why Slack says “not approved by Slack”

Slack shows “This app is not approved by Slack” when you install an app that is not listed in the Slack Marketplace. CoffeeSlack is not listed yet, so you will see it. Slack still shows you every permission the app asks for before you approve — they are the seven below.

Slack permissions

What we ask Slack for, and why

commands
Adds the /coffee command, which is how people join a round.
chat:write
Sends the messages: each pair’s introduction, the welcome note to whoever installed the app, the reminders and check-ins, and an invite to join when an admin asks for one in a channel the app is in.
im:write
Opens a direct message with a person so those messages can reach them.
users:read
Reads a person’s name and time zone, and whether they are a workspace owner or admin, which decides who can change settings in the dashboard.
users:read.email
Reads the email on a person’s Slack profile. We use it to fill in the email on the /coffee sign-up form, to send one welcome email to whoever installed the app, and to add your match as a guest when you use the Google Calendar button in an introduction.
channels:read
Reads who is in the public channels you choose to pair from. Only used if you pick channels.
groups:read
The same for private channels you choose, and only ones the app has been added to.

When someone signs in to the dashboard, Slack separately asks them to share their name, email, and workspace with us. That is how we know who is signing in and which workspace they belong to.

Your data

What we store

  • The install

    Your workspace’s Slack ID and name, the token Slack gives the app, and the Slack ID of whoever installed it.

  • Sign-ups

    For each person who joins with /coffee: their Slack ID, name, email, and the month they joined.

  • Pairings

    Who was paired with whom, whether each introduction was delivered, and whether the calendar button was used.

  • Feedback

    The button each person pressed after a round: met, not yet, or didn’t meet.

  • Settings

    Your schedule, the channels you pair from, your own wording for the introduction, conversation starters, the Slack IDs of your bot admins, and any notification emails your admins add.

  • Reminder choices

    Who asked us to stop sending the sign-up reminder, and who has already had one this round.

  • Admin access requests

    Who used the dashboard to ask their admins for access, and when, so the request isn’t sent twice.

No message content and no files. We don’t sell any of it, and we don’t use it to train any model. The full detail is in our privacy policy.

Deletion

Removing the app, or one person

When you remove the app

We pause your workspace and delete the Slack token and install record straight away, so nothing more is sent. Sign-ups, pairings, feedback, and settings are kept, so reinstalling brings your history back. Email us and we erase the rest, then confirm when it is done.

For one person

An admin can erase someone who joined this month from the dashboard’s Participants page, or anyone can email us. We remove their sign-ups from every month, take them out of their pairs, and delete their feedback. One record stays on purpose: if they asked us to stop the sign-up reminder, we keep that request so the reminders can’t start again.

Who else handles it

The services we use

Google Cloud
Runs the app and holds the database. The app runs in the us-central1 region (Iowa, USA); the database is Firestore in Google’s United States multi-region.
Vercel
Hosts coffeeslack.com and the dashboard. Dashboard pages are built on the server, so names and emails pass through Vercel on the way to your browser; nothing is stored there.
Clerk
Handles dashboard sign-in, which only works through Slack. We never see or store a password.
Sentry
Collects error reports. Sign-in tokens, cookies, and secret parts of links are removed before a report leaves the app.
Resend
Sends the welcome email and messages from our contact form. Pair introductions by email are switched off today; introductions go out as Slack messages only.
Cloudflare
Runs DNS for coffeeslack.com and counts page views on the website without cookies.

Two more appear in our privacy policy but receive nothing today. Anthropic would write conversation starters on request, and that is not switched on. Stripe would take payments, and there is no billing yet.

Safeguards

How access is kept narrow

  • Only a Slack workspace owner or admin, or someone they add as a bot admin, can change settings. Someone deactivated in Slack loses that access.
  • Every message from Slack is checked against Slack’s signature before we act on it.
  • The app’s own keys are kept in Google’s secret store, never in our code. Each workspace’s Slack token is stored in our database, which only the app and its operator can read.
  • We don’t hold a SOC 2 or ISO 27001 certification. If your review needs a security questionnaire answered, email us and we will fill it in.

Contact

Questions, deletion, and reports

Email support@coffeeslack.com for help or a deletion request. We reply within two business days.

Found a security problem? Email security@coffeeslack.com instead. We acknowledge reports within three working days.