Security & Compliance

Public-company status and security.

EVIO is publicly traded on the OTC Current tier with company disclosures published through OTC Markets.

Public-company status

TickerOTC: EVIO
State of incorporationColorado
HeadquartersHenderson, Nevada
Reporting statusOTC Current (not an SEC registrant)
Disclosure cadencePer OTC Markets disclosure requirements (OTC Current); annual + quarterly reports + audited financials
Audit-log retentionIndefinite for compliance: per-agent action history exportable on request

Application security

TransportTLS 1.2+ everywhere via Cloudflare; HSTS enabled
API keysSHA-256 hashed at rest; plaintext shown once at creation
Per-agent scopingRecommended over org-wide keys; pause/revoke with 1-second propagation
Rate limitsPer-agent rate limits, configurable
Webhook signaturesHMAC-SHA256 on all outbound; Stripe + Clerk inbound verified before any DB write
Two-factor authRequired for org owners; recommended for all users
Audit logEvery admin action logged with actor (user OR agent), target, metadata
Secrets managementDoppler: never in code, never in git
PII storageEmail + name (Clerk) + Stripe customer ID. No SSNs, no payment-card data on EVIO infra.

SLA targets

EVIO does not publish a contractual SLA. Internal targets:

MetricInternal target
Uptime99.9%
p50 latency (mock data)< 200 ms
p95 latency (mock data)< 800 ms
Webhook delivery (first attempt)< 30 s
Status pagestatus.evioinc.com

Subprocessors

EVIO uses the following subprocessors. Full list maintained at /api/legal/privacy.

Auth & org managementClerk
BillingStripe
DatabaseSupabase (Postgres)
Edge / WAF / CDNCloudflare
Cache & rate limitUpstash Redis & QStash
Behavioral warehouseMotherDuck
Logs & metricsBetter Stack
ErrorsSentry
SecretsDoppler
HostingVercel (web), Fly.io (API)
DocumentationMintlify
Forward-looking statement

The availability and latency figures on this page are targets, not guarantees of performance.