Privacy policy

CoffeeSlack (“we”, “us”) operates the Slack app and dashboard at coffeeslack.com. Who is responsible for the data depends on which data. For what we handle on a workspace’s instruction — participants, pairings, settings, the install record — the customer that installed CoffeeSlack is the data controller and we act as their processor. For admin sign-in, billing, and operational logs we decide the purposes ourselves, so there we are the controller.

We only collect what we need to pair teammates and send the resulting introductions. Specifically:

• Workspace install record — Slack team id and name, the OAuth bot token, and the Slack user id of whoever ran the install.
• Participants — for each teammate who opts in with /coffeeor the App Home button: their Slack user id, display name, and email (read from Slack’s user profile), plus the month they opted in for.
• Pairings — for each monthly round, which participants were paired with which, and whether the email / Slack DM was delivered.
• Workspace settings — your logo URL, custom email template (if any), trigger mode, the Slack user ids of your bot admins, and any notification email addresses your admins enter — including addresses outside your workspace.
• Admin sign-in — when an admin signs into the dashboard with Continue with Slack, Clerk creates a session. Clerk holds the Slack account link, the email, and session metadata; we never see a password. We receive the authenticated identity and the email to evaluate access.
• Billing — when a workspace upgrades to a paid plan, Stripe holds the payment method and billing history. We store the resulting Stripe customer id, subscription id, and plan status — we never see the card itself.
• Operational logs — request logs, error reports (via Sentry), and aggregated counts kept for up to 90 days for debugging. Credentials, signatures, and secret URL parameters are stripped before reporting.

• To generate the monthly pairings and notify participants.
• To deliver the introduction emails (subject, body, and your workspace’s logo).
• To gate the admin dashboard to authorized operators.
• To bill paid plans through Stripe.
• To debug failures, prevent abuse, and keep the service running.

We do not sell personal data, and we do not use participant data to train any model.

We use a small, fixed set of vendors to operate the service. Each one only sees the data it needs to do its job.

• Slack — the platform the app runs on. Reading workspace + user profile data; sending DMs and modal interactions.
• Google Cloud Platform— application hosting (Cloud Run), database (Firestore), and logo storage (Cloud Storage). Data is stored in Google’s United States multi-region by default.
• Resend — outbound transactional email delivery for the monthly introductions and contact-form acknowledgements.
• Clerk — admin authentication via Continue with Slack, and session management.
• Stripe— payment processing for paid plans. Stripe’s Customer Portal handles cancellations and invoices.
• Sentry — error reporting with sensitive request data redacted at source.
• Anthropic— generates the conversation-starter list, when your operator has configured a key. Two things are sent: your workspace name, and the optional tone hint your admin writes. Nothing is read from the participant list or the pairings — though whatever an admin types into that hint is sent as typed, so it is not the place for anyone’s details.
• Vercel — hosting for coffeeslack.com, including the admin dashboard. Dashboard pages are rendered on the server, so participant names and emails pass through Vercel in transit; nothing is stored there.
• Cloudflare — DNS for coffeeslack.com, plus Cloudflare Web Analytics for privacy-friendly, cookieless pageview counts on the marketing site and dashboard. No cookies; no long-term IP storage; no cross-site tracking. Cloudflare publishes the details at cloudflare.com/web-analytics.

We keep workspace install records, participants, pairings, and settings for as long as the workspace has CoffeeSlack installed. If a workspace uninstalls the app, we delete the install record and the stored Slack token straight away, and the workspace stops pairing. The rest is retained so that reinstalling restores your history, and we erase it on request — email us and we will confirm when it is done. Operational logs are retained for up to 90 days. Stripe retains billing records per its own legal obligations even after a subscription ends.

You can ask us to access, correct, export, or delete personal data we hold about you. We honor these requests even where the underlying law (GDPR, CCPA, UK GDPR, etc.) doesn’t strictly require it.

Email us to remove a teammate’s record, or ask your workspace admin to — we delete their monthly opt-ins, take them out of their pairs, and delete the feedback they left. Rounds run for a channel group your workspace has since removed from its settings are not reached automatically; ask us and we clear those by hand and confirm what came out. One record stays on purpose: if they asked us to stop sending reminder DMs, we keep that request so the reminders cannot resume — say the word and that goes too. For anything else, email support@coffeeslack.com from the address tied to your Slack account and we’ll handle it within 30 days.

The marketing site sets no analytics or advertising cookies. Cloudflare Web Analytics (see the third-party services section above) measures pageviews via a lightweight beacon that does not set cookies and does not fingerprint visitors. When you sign into the admin dashboard, Clerk sets the session cookies necessary to keep you signed in. Stripe sets cookies on the Checkout and Customer Portal pages it hosts. See Clerk’s privacy notice and Stripe’s privacy notice for details.

CoffeeSlack is a workplace tool and is not directed at children under 16. We don’t knowingly collect personal data from children. If you believe a child has provided us with personal data, contact us and we’ll delete it.

We may update this policy as the product evolves. When we do, we bump the effective date at the top. If a change meaningfully reduces your rights, we’ll notify workspace admins by email before it takes effect.

Email support@coffeeslack.com or use the contact form.