What this policy covers
This policy covers the two places Expedition Labs handles data: this website, expeditionlabs.co, and Meeting Mouse, the availability poll app for Slack that we run at app.meetingmouse.net. Work we do for a client is covered by the written agreement for that engagement.
What Meeting Mouse stores
Meeting Mouse stores what it needs to run availability polls in a Slack workspace.
- Slack ids for the workspace, the channel a poll was posted in, and the people who organize or answer a poll.
- Each poll: its title, the times it offers, its status and its final time.
- Each answer: the times a person marked, with that person's display name and time zone.
- A stored copy of a person's display name and time zone, so the app does not ask Slack for them on every click.
- For each workspace that installed the app: its name, the permissions it granted, the id of the person who installed it, and the app's access token in encrypted form.
It does not store messages, files, channel names, channel member lists, email addresses, phone numbers, profile pictures or calendar data.
Where it is stored
| Provider | Role | Location |
|---|---|---|
| Neon | Hosts the one database that holds all Meeting Mouse data | United States |
| Vercel | Hosts the app and this website, and keeps request logs | United States |
| Slack | Delivers commands and clicks to the app and shows the poll messages it posts | As Slack provides |
No other service or processor receives the data. Nothing is kept on personal devices or in a second database. This website is static: it has no database and stores nothing about its visitors beyond the hosting provider's request logs.
How it is protected
- In transit: every connection uses TLS, between Slack and the app, between a browser and the app, and between the app and the database.
- At rest: the database provider encrypts stored data with AES-256.
- Access tokens: each workspace's Slack access token is encrypted by the app with AES-256-GCM before it is written to the database, under a key held only in the hosting environment. The encrypted value is tied to its workspace, so it cannot be reused for another.
- Requests: every request from Slack is checked against Slack's signature before the app acts on it.
- Secrets: credentials are held in the hosting provider's environment settings and are never committed to source code.
Who can reach it
Production access is limited to the owner of Expedition Labs. There are no shared credentials. The data is used only to run the app. We do not sell it, share it with anyone for their own use, use it for advertising, or use it to train or improve any machine-learning model.
Separation between workspaces
Every stored record carries the id of the workspace it belongs to, and the app acts in a workspace only with that workspace's own token. A link to the page where a person marks availability in a browser is signed for one person and one poll, expires after 24 hours, and is rejected if the workspace in the link does not match the poll.
Backups
We keep no separate backup files. Recovery relies on the database provider's restore history, a rolling window of at most 30 days that is stored and encrypted by the provider.
Changes
When a provider or a storage practice changes, this page is updated and given a new effective date.
Contact
Questions about this page go to hello@expeditionlabs.co. Requests about data held by Meeting Mouse go to support@meetingmouse.net.