Privacy and data handling at Dailybot
Dailybot processes the information your team submits through chat and the web app so standups, kudos, workflows, and AI-assisted features can run. This article is a high-level map of what we collect, where it lives, and where to read authoritative detail.
What data is collected
In broad terms, Dailybot handles account and profile data (name, email, role, org membership), usage and product data (check-in answers, commands, configuration you save), chat platform identifiers so messages route to the right person, billing records for paying customers, and technical logs that support security and reliability. If you connect coding agents or webhooks, related tokens, keys, and delivery metadata are stored so those integrations keep working.
Where data is stored and processed
Dailybot operates as a cloud service with infrastructure and subprocessors appropriate to your contract and region. Exact locations and subprocessors are described in our Privacy Policy and Data Processing Agreement (DPA) — use those documents when your legal team needs vendor due diligence.
How to go deeper
- Retention schedules: Data retention policies
- Deletion and GDPR-style requests: Requesting data deletion and GDPR compliance and your rights
- Secrets and API access: Managing API keys and webhook secrets
- Legal pages: Read the published Privacy Policy, Terms of Service, and DPA on Dailybot’s legal site for binding language; Help Center articles summarize but do not replace them.
If you are an admin rolling out Dailybot company-wide, share this overview with IT and Legal, then point engineers to the webhook and key article before they wire custom automation.