Privacy Policy
Last Updated: September 7, 2026
Zero Message Reading Policy: DibsQueue does not request any message history scopes (such as
channels:history). We do not and cannot read, inspect, or store your private or public Slack messages.
1. Information We Collect
When you install and use DibsQueue, we collect only the minimal metadata necessary to manage locks:
- Slack Workspace Data: Team ID, Team Name, and Bot User ID.
- Encrypted Bot Tokens: OAuth tokens are immediately encrypted at rest using AES-256-GCM.
- Resource Configurations: Resource names, duration caps, active lock holder user IDs, and waiting queue user IDs.
2. Token Security & Encryption
All authentication tokens are secured with AES-256-GCM authenticated encryption with random initialization vectors and cryptographic tags. Data in transit is protected using TLS 1.3.
3. Data Retention & Deletion
When you uninstall DibsQueue, all bot tokens and active queue states are immediately revoked and removed. Workspace records are deleted upon written request to support@dibsqueue.com.
4. Contact Us
For questions or privacy requests, please contact: privacy@dibsqueue.com