1. Our Commitment
Security is a core part of Daim. Because our platform handles your business conversations and connected-channel credentials, we design and operate it with defense-in-depth practices across infrastructure, application, and organization levels.
2. Encryption
- In transit: all traffic between your browser and our servers uses TLS (HTTPS) encryption.
- Access tokens: tokens for connected channels (WhatsApp, Messenger, Instagram, Telegram) are stored encrypted and are never exposed in logs or API responses.
- Passwords: user passwords are hashed using strong one-way algorithms and are never stored in plain text.
3. Access Control and Authentication
- Role-based access control limits what each user and admin can see or modify.
- Two-factor authentication (2FA) is available for additional account protection.
- Administrative access to production systems is restricted to authorized personnel only, on a least-privilege basis.
4. Infrastructure and Data Isolation
- Customer data is logically isolated; each account can only access its own conversations, contacts, and channels.
- We host on reputable cloud providers with physical security, redundancy, and network protection.
- Regular backups protect against data loss, with retention and restoration procedures in place.
5. Platform Integrations
- We follow the security requirements of each connected platform, including Meta's Platform Terms and data-handling requirements.
- Webhooks and API callbacks are verified (signature validation) before processing.
- Disconnecting a channel stops all related data flows immediately.
6. Monitoring and Incident Response
- We monitor systems for anomalies, abuse, and intrusion attempts.
- Security incidents are triaged and handled through a defined response process; affected users are notified when required.
- Anti-abuse protections (rate limiting, spam controls, bot detection) guard the platform and your channels.
7. Application Security
- Input validation, output encoding, and parameterized queries protect against common web attacks (XSS, SQL injection, CSRF).
- Dependencies are kept up to date, and code changes go through review before deployment.
8. Your Responsibilities
Security is shared. We recommend that you:
- Use a strong unique password and enable 2FA.
- Review connected channels and team-member permissions regularly.
- Keep your devices and browsers up to date.
- Never share your credentials or API keys publicly.
9. Reporting a Vulnerability
If you discover a security issue, please report it responsibly through the Contact Us page. We investigate all reports and appreciate coordinated disclosure — please do not publicly disclose an issue before we have had a reasonable chance to address it.
10. Continuous Improvement
We regularly review and improve our security practices as threats evolve, and we update this page to reflect significant changes.