Trust
Security Overview
Yenvora is designed to support business customer conversations and connected channel operations. This overview summarizes the safeguards we use and the responsibilities customers share when operating their workspaces.
Transport Security
Yenvora uses HTTPS/TLS for public website and application traffic.
Access Control
Workspace access is role-based. Customers are responsible for managing user access and removing users who no longer need access.
Credential Handling
Integration tokens and API credentials are stored for the purpose of operating connected customer services and should be rotated if compromise is suspected.
Backups
Production database backups are currently retained for 14 days for disaster recovery.
Monitoring
Application and infrastructure logs may be used to troubleshoot issues, detect abuse, investigate incidents, and maintain service reliability.
Responsible Disclosure
Report suspected security issues to security@yenvora.com. Please include enough detail for us to reproduce and assess the issue.
Customer Security Responsibilities
- Use strong passwords and secure administrative accounts.
- Grant access only to people who need it.
- Review connected Meta, WhatsApp, commerce, and email integrations regularly.
- Rotate API tokens if an employee leaves or a credential may have been exposed.
- Follow WhatsApp, Meta, and applicable messaging consent rules.