Security
We post to your Slack. We never read it.
The app has no scope that reads channel history or files. It sees a message only when someone @mentions it. Here is every permission it asks for and why.
| Scope | Why |
|---|---|
| chat:write | Post drops in channels the app is a member of. |
| chat:write.public | Post in public channels you pick without inviting the app first. |
| channels:read | List public channels so you can pick them in the dashboard. |
| groups:read | List private channels the app has been invited to. |
| commands | Respond to the /drops command. |
| team:read | Read the workspace name and icon to label it in the dashboard. |
| app_mentions:read | Receive only the messages that @mention AI Drops, to answer questions. It cannot read other messages. |
Tokens
Slack bot tokens and webhook secrets are encrypted with AES-256-GCM before they are stored, using a key held as a server secret and never in the database. Uninstalling the app from Slack revokes the token.
What we store
- Workspace and channel ids and names you select
- Your channel rules, the delivery log (which drop went where) and the team description, if you write one
- Webhook URLs and secrets, and hashed API keys, on Business
- Admin email addresses for sign-in and billing notices
Release summaries are generated from public changelogs. Your workspace data is not sent to an AI model, with two exceptions: the text of a question you send to Ask in Slack, and the team description you save in Settings, which goes with each What changed for us? request.
Infrastructure
The app runs on Cloudflare Workers with a Neon Postgres database, over TLS. Payments go through Stripe; we never see card numbers. The full list is on the subprocessors page.
Report an issue
Email support@getaidrops.com with "Security" in the subject.