Snapshot 231912

Document
Security page
URL
https://getsched.dev/security
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
static
Size
23226 bytes
SHA-256 (raw)
b631e519120993faf07ec21ba7d0b5da86f1a745f973afbd75f0b1c589deabb3
SHA-256 (normalized text)
4697c316e963d658801cf2f71a55a0bc7e759bbede89d100276052acd043696e

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Security
Sched is a small product. This page explains exactly what we access, what we store, and how we protect it — without marketing language.
What Sched never accesses
✓No message content. We don't request or call Slack message history APIs. We cannot read your channels or DMs.
✓No passwords. Authentication is Slack OAuth only — we never see or store a password.
✓No profile data beyond what's necessary. We store Slack user IDs to map rotation assignments. We don't store names, emails, or profile photos.
What we store
Only what's needed to run rotations: rotation schedules, assignment mappings (Slack user IDs ↔ user group IDs), and basic workspace metadata (workspace ID and name).
How we protect it
—Token storage. Slack bot tokens are encrypted with AES-256-GCM before they are stored in our database. The key is kept in our hosting provider's secret store, apart from the database. We are moving tokens off Nango, which holds them until that move is finished.
—Encryption in transit and at rest. All traffic uses TLS. Data at rest is encrypted by MongoDB Atlas and Upstash (AES-256).
—Workspace isolation. Each workspace's data is strictly separated. One tenant cannot access another's data.
—Least-privilege Slack scopes. We request only the permissions needed: user group lookups, membership updates, and optionally sending notifications.
—Revoke anytime. Remove the integration from Slack (Settings → Manage Apps → Remove) to immediately stop all access. Email security@getsched.dev to request deletion of stored workspace data.
Sub-processors
Provider	Purpose	Region
Vercel	Application hosting	US
MongoDB Atlas	Primary database	US
Upstash Redis	Caching & rate limiting	US
Nango	OAuth token management	US
Inngest	Scheduled job execution	US
Common questions
Report a vulnerability
Email security@getsched.dev. We aim to respond within 48 hours.