Security at Evnao

Your trust. Our responsibility.

Understand how Evnao protects workspace access, handles integration credentials, and keeps control with your team. Explore the implemented controls and their limits.

Disclosure policy Data processing terms

Workspace boundaries
Encrypted credentials
Verified inbound events

Implemented controls. Openly explained.

Built into the platform

Control at every layer.

Tenant-scoped access

Dashboard and admin data paths check the authenticated workspace before reading or changing tickets, knowledge, feedback, integrations, and billing data.

Encrypted integration secrets

Provider tokens and connected-action headers are encrypted at rest and treated as write-only in the browser.

Verified inbound events

Payment provider, Meta, Telegram, and Brevo webhook paths validate the expected signature or secret before durable processing. Legacy billing records remain isolated behind compatibility-only handlers.

MFA and session controls

Normal users can enable authenticator MFA and backup codes. Admin access uses a separate session boundary, MFA challenge, throttling, and revocation controls.

Outbound request defense

Website imports and connected HTTPS actions apply DNS/IP checks, redirect limits, response bounds, encrypted credentials, and approval for writes.

Scoped public capabilities

Widget visitors receive hashed, expiring ticket capabilities and origin-bound embed tokens instead of access to tenant identifiers alone.

Certification status

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.

AI provider: Managed generation uses GLM-5.3-Flash through Z.ai as its required primary model. Gemini 2.5 Flash is eligible only for a telemetry-limited emergency fallback, and Google also supplies knowledge embeddings, after paid-service processing is explicitly confirmed. The runtime fails closed when the primary credential is absent and does not accept customer-supplied provider keys. Customer messages, retrieved knowledge, and selectively requested attachment context may be sent to the active provider. Evnao does not use Customer Data to train its own general-purpose models and does not promise universal provider-side Zero Data Retention.
Data retention: Workspace records remain in Evnao’s database until retention or deletion processes remove them. Zero-data-retention is not advertised as active.
Responsible disclosure: Report a reproducible issue to security@evnao.com. Do not access another customer’s data or disrupt service.

Disclosure policy Data processing terms

Security at Evnao

Your trust. Our responsibility.

Understand how Evnao protects workspace access, handles integration credentials, and keeps control with your team. Explore the implemented controls and their limits.

Disclosure policy Data processing terms

Workspace boundaries
Encrypted credentials
Verified inbound events

Implemented controls. Openly explained.

Built into the platform

Control at every layer.

Tenant-scoped access

Dashboard and admin data paths check the authenticated workspace before reading or changing tickets, knowledge, feedback, integrations, and billing data.

Encrypted integration secrets

Provider tokens and connected-action headers are encrypted at rest and treated as write-only in the browser.

Verified inbound events

MFA and session controls

Normal users can enable authenticator MFA and backup codes. Admin access uses a separate session boundary, MFA challenge, throttling, and revocation controls.

Outbound request defense

Website imports and connected HTTPS actions apply DNS/IP checks, redirect limits, response bounds, encrypted credentials, and approval for writes.

Scoped public capabilities

Widget visitors receive hashed, expiring ticket capabilities and origin-bound embed tokens instead of access to tenant identifiers alone.

Certification status

AI provider: Managed generation uses GLM-5.3-Flash through Z.ai as its required primary model. Gemini 2.5 Flash is eligible only for a telemetry-limited emergency fallback, and Google also supplies knowledge embeddings, after paid-service processing is explicitly confirmed. The runtime fails closed when the primary credential is absent and does not accept customer-supplied provider keys. Customer messages, retrieved knowledge, and selectively requested attachment context may be sent to the active provider. Evnao does not use Customer Data to train its own general-purpose models and does not promise universal provider-side Zero Data Retention.
Data retention: Workspace records remain in Evnao’s database until retention or deletion processes remove them. Zero-data-retention is not advertised as active.
Responsible disclosure: Report a reproducible issue to security@evnao.com. Do not access another customer’s data or disrupt service.

Disclosure policy Data processing terms