Tenant-scoped access
Dashboard and admin data paths check the authenticated workspace before reading or changing tickets, knowledge, feedback, integrations, and billing data.
Security controls implemented today
No system is mathematically incapable of failure. This page documents controls present in Evnao and clearly states what has not been independently certified.
Controls and boundaries
State remains inspectable
Dashboard and admin data paths check the authenticated workspace before reading or changing tickets, knowledge, feedback, integrations, and billing data.
Provider tokens and connected-action headers are encrypted at rest and treated as write-only in the browser.
FastSpring, Meta, Telegram, and Brevo webhook paths validate the expected signature or secret before durable processing. Legacy billing records remain isolated behind compatibility-only handlers.
Normal users can enable authenticator MFA and backup codes. Admin access uses a separate session boundary, MFA challenge, throttling, and revocation controls.
Website imports and connected HTTPS actions apply DNS/IP checks, redirect limits, response bounds, encrypted credentials, and approval for writes.
Widget visitors receive hashed, expiring ticket capabilities and origin-bound embed tokens instead of access to tenant identifiers alone.
Evnao is not currently represented as SOC 2 certified, HIPAA compliant, or covered by a 99.99% uptime SLA. Those require audited operations, contracts, incident processes, and measured evidence beyond application code.