Privacy

No tracking, and ReactPing never stores your messages. ReactPing is open source, so you can check everything below.

What we store

For each person who connects, in each workspace: the Slack workspace ID, user ID, workspace URL, encrypted access tokens, and when the connection was created and updated. That is what lets ReactPing recognize you and send your DMs.

We track when you connect and when you disconnect.

Feedback

Feedback goes through the form on this website. We store what you wrote, the name and email only if you give them, and whether you opened the form from ReactPing's link in Slack or from the website itself.

What we don't store

From Slack: message text, files, channel history, names, email addresses, or reaction history. Your DMs stay in Slack.

How we use it

Only to deliver reaction notifications and manage your connection. Notifications stay in the workspace where the reaction happened. No advertising, analytics, or sale of data.

Security and cookies

Access tokens are encrypted with AES-256-GCM. While you add ReactPing, one signed, HttpOnly cookie links Slack's approval to your browser; it expires after 10 minutes and is cleared when you return. This website runs no scripts.

Service providers

Vercel hosts the website and API. Supabase stores connection records. Slack sends reaction events and delivers DMs. They may keep operational logs such as IP addresses and request times. ReactPing's own logs contain workspace IDs and error codes, never tokens, authorization codes, or message content.

Disconnect and delete

Select Disconnect in ReactPing's Home tab in Slack. That deletes your connection record and asks Slack to revoke your user token; other people's connections are unaffected. Removing ReactPing from a workspace deletes all of that workspace's records when Slack notifies us.

To see, export, or delete your data, including feedback, send a request through the feedback form with your email address. We reply within 2 business days.

Delivery

Notifications are best effort. Missed reactions aren't replayed. The free-tier database may pause after about a week of low activity; notifications resume once it is restored.

Questions

Send feedback or open a GitHub issue. Report security issues privately as the security policy describes.

Send feedback Open a GitHub issue Security policy