Security summary
- HTTPS/TLS on all hosted traffic
- Ephemeral token handling by default
- Persistent storage only with explicit consent
- AES-256-GCM encryption at rest for stored credentials
- No Slack message retention as product analytics
Security
Know what is stored, what stays transient, and how delivery is verified.
This buyer-facing trust surface covers token handling, encrypted storage, content-free workflow measurement, signed downstream delivery, analytics disclosure, and the route for deeper rollout review.
Token and storage model
- Ephemeral mode: default path, no durable credential write required
- Persistent mode: opt-in only when the operator explicitly consents
- Bearer keys: tenant-scoped API keys gate MCP access
- Account surface: reconnect and disconnect stay available through /account
Data boundary
- Slack requests proxy through the hosted worker and return directly to the MCP client
- Slack messages, files, and channel history are not stored as analytics payloads
- Workflow measurement tracks kind, outcome, bounded error code, plan, and duration — never Slack content, prompts, generated briefs, channel identifiers, or webhook URLs
- Full data-handling detail stays in privacy
Encrypted profiles and signed downstream delivery
- Saved profiles are tenant-scoped and contain only the configuration an operator explicitly submits
- Webhook URLs and P-256 private signing keys are AES-256-GCM encrypted at rest
- Public P-256 verification keys can verify each timestamped payload without exposing private signing material
- Webhook targets must be public HTTPS endpoints; private hosts, IP literals, embedded credentials, redirects, and nonstandard ports are rejected
Website measurement
- Cloudflare Web Analytics covers the hosted website only
- First-party funnel events cover pricing, deployment, checkout, setup, and account actions
- Neither layer changes Slack token handling or Slack message retention
- Use this page and privacy for procurement review, not GitHub issues
Support and incident envelope
- Solo: managed endpoint plus standard hosted support routing
- Team: adds shared workflow outcomes and higher usage ceilings
- Turnkey Team Launch: rollout and buyer review envelope
- Managed Reliability: ongoing operational support boundary when Slack context is business-critical
Procurement questions this page answers
- Where tokens live and how they are protected
- What data is and is not retained
- Which routes are public versus authenticated
- How support, rollout, and reliability expectations are scoped
Deployment review scope
Use deployment review when the team needs buyer review, rollout sequencing, support-envelope clarification, or premium fit guidance. That keeps the commercial and operational conversation on the hosted surface.
When self-host is the better answer
If procurement or operations require full runtime ownership, local transport control, and direct token handling under your own environment, the OSS/self-host path remains available with 21 tools.