Privacy Policy
Last updated: 2026-09-23
Zonely ("the app") is a Slack app that detects time mentions in messages (like 10am CST or 3pm India) and replies in-thread with the equivalent time in each teammate's own timezone. This page explains what data it accesses and why.
What Zonely accesses
- Message text in channels, groups, and DMs it's added to — read only to detect time mentions and generate a reply. It is not stored in a database.
- Timezone setting of workspace members (via Slack's
users:read scope) — used only to convert detected times into each person's own timezone.
- Channel membership lists (via
channels:read/groups:read) — used only to determine which timezones to convert into for a given channel.
- An OAuth access token issued by Slack when your workspace installs Zonely — required to post replies and make the API calls above on your workspace's behalf.
What Zonely stores
The only data Zonely persists is the OAuth access token for each workspace that installs it, plus the associated team ID. This is kept only so the app continues to function without requiring reinstallation, and is deleted automatically when your workspace uninstalls the app or revokes access.
Message content is processed in memory to detect times and is not written to any database. Basic operational logs (e.g. that a message was received, whether a time was detected) may be retained briefly by our hosting infrastructure for debugging purposes.
What Zonely does not do
- It does not sell, share, or use your data for advertising.
- It does not store message content in a database.
- It does not access data outside the scopes listed above.
Data retention and deletion
Uninstalling Zonely from your workspace (or revoking its access in Slack) deletes its stored access token for that workspace. To request deletion of any other data associated with your workspace, contact us using the details below.
Contact
Questions about this policy or how Zonely handles your data: pawan@octonomus.com
Privacy · Terms · Support
← Back to Zonely