Workspace isolation
- Each workspace's data is stored as its own encrypted record under its own key.
- Every request is tied to the workspace Slack says it came from, so one workspace can never read or change another's data.
- Inside a workspace, members can only see and edit their own dates. Only workspace admins and the person who installed the app can change settings, import dates or manage billing.
Minimal data, real deletion
- Birthdays are stored as month and day only, never the year. Email addresses used for an import are not stored.
- Uninstalling the app removes the workspace's data from the service immediately. An encrypted copy is kept for 7 days so a reinstall can restore it, then deleted. Encrypted backups expire within 30 days.
- Technical logs are kept for 14 days. They contain workspace and member IDs, never birthdays or message content.
No long-running infrastructure
- There are no servers, virtual machines or containers to break into or patch. The app runs as short-lived functions that start when Slack sends a request (or periodically to post celebrations) and stop when the work is done.
- All infrastructure is professionally defined, so every change is versioned and repeatable. Nothing is configured by hand in a console.
Encryption
| Layer | How |
|---|---|
| In transit | All traffic uses HTTPS/TLS: Slack ↔ the app, the app ↔ AWS, and this website. |
| At rest, per workspace | Each workspace's private data is encrypted by the app with AES-256-GCM using an encryption key unique to that workspace. |
Least privilege
- The app cannot access your channel or private messages. It uses minimal Slack permissions:
- Post messages (
chat:write,chat:write.public) - Send DMs when you enable them (
im:write) - The
/celebratecommand (commands) - List members and match import emails (
users:read,users:read.email) - Read a CSV file an admin uploads for importing users (
files:read)
- Post messages (
Payments
Payments are handled by Paddle, a PCI DSS compliant merchant of record. Card details go straight to Paddle; we never see or store them.
Certifications
We're a small, independent product and don't currently hold certifications such as SOC 2 or ISO 27001. Our hosting provider, AWS, maintains a wide range of certifications for the underlying infrastructure.
Reporting a vulnerability
If you believe you've found a security issue, please email security@letscelebrate.day. We'll acknowledge it promptly and keep you updated. Please don't access other customers' data or disrupt the service while testing.