Security Policy




At ZEVAC we take the protection of Client data extremely seriously. This ZEVAC Security Policy describes the organizational and technical measures ZEVAC implements platform-wide, designed to prevent unauthorized access, use, alteration or disclosure of Client data. The ZEVAC services operate on Microsoft AZURE or Amazon Web Services (“AWS”); this policy describes activities of ZEVAC within its instance on Azure / AWS unless otherwise specified. 


Security Team


Our infrastructure and security team includes people who’ve played lead roles in designing, building, and operating highly secure Internet facing systems at companies ranging from startups to large public companies.


Best Practices


Incident Response Plan

  • We have implemented a formal procedure for security events and have educated our staff on our policies.

  • When security events are detected they are escalated to our emergency alias, teams are notified and assembled to rapidly address the event.

  • After a security event is fixed we write up a post-mortem analysis.

  • The analysis is reviewed in person, distributed across the company and includes action items that will make the detection and prevention of a similar event easier in the future.

  • ZEVAC will promptly notify you in writing upon verification of a security breach of the ZEVAC services that affects you. Notification will describe the breach and the status of ZEVAC’s investigation.


Build Process Automation

  • We have functioning, frequently used automation in place so that we can safely and reliably rollout changes to both our application and operating platform efficiently.

  • We typically deploy code very frequently, so we have confidence that we can get a security fix out quickly when required.



  • All of our services run in the cloud. ZEVAC does not run our own routers, load balancers, DNS servers, or physical servers.

  • All of our services and data are hosted in Microsoft AZURE / AWS facilities and protected by Microsoft / AWS security as the case may be.

  • ZEVAC services have been built with disaster recovery in mind.

  • All of our servers are within our own virtual private cloud (VPC) with network access control lists (ACL’s) that prevent unauthorized requests getting to our internal network.



  • Client data is stored in multi-tenant datastores; we do not have individual datastores for each customer. However strict privacy controls exist in our application code that are designed to ensure data privacy and to prevent one customer from accessing another customer’s data (i.e., logical separation). We have many unit and integration tests in place to ensure these privacy controls work as expected. These tests are run every time our codebase is updated and even one single test failing will prevent new code being shipped to production.

  • Each ZEVAC system used to process Client data is adequately configured and pathed using commercially-reasonable methods according to industry-recognized system-hardening standards.


Data Transfer

  • All data sent to or from ZEVAC is encrypted in transit using 256-bit encryption.

  • Our API and application endpoints are TLS/SSL only and score an “A+” rating on SSL Labs’ tests. This means we only use strong cipher suites and have features such as HSTS and Perfect Forward Secrecy fully enabled.

  • We also encrypt data at rest using an industry-standard AES-256 encryption algorithm.



  • ZEVAC is served 100% over https. ZEVAC runs a zero-trust corporate network.

  • There are no corporate resources or additional privileges from being on ZEVAC’s network.

  • We have two-factor authentication (2FA) and strong password policies on GitHub, Google, AWS, and ZEVAC to ensure access to cloud services are protected.


Permissions and Admin Controls

  • ZEVAC enables permission levels to be set for any employees with access to ZEVAC.

  • Permissions and access can be set to include app settings, billing, user data, or the ability to send/edit manual messages and auto messages.


Application Monitoring

  • On an application level, we produce audit logs for all activity and ship logs to our service providers for analysis.

  • All access to ZEVAC applications is logged and audited.

  • Bastion hosts are used to login to devices.

  • All actions taken on production consoles or in the ZEVAC application are logged.


Security Audits and Certifications

  • We regularly engage with well-regarded third-party auditors to audit our code-base, and work with them to resolve potential issues.

  • We use technologies to provide an audit trail over our infrastructure and the ZEVAC application. Auditing allows us to do ad-hoc security analysis, track changes made to our setup and audit access to every layer of our stack.

  • ZEVAC has undergone a SOC 2 Type II audit. A copy of the applicable report can be made available upon reasonable request. 


Customer Responsibilities

  • Managing your own user accounts and roles from within the ZEVAC services.

  • Protecting your own account and user credentials by using two-factor authentication for all of your employees accessing the ZEVAC services.

  • Compliance with the terms of your services agreement with ZEVAC, including with respect to compliance with laws.

  • Promptly notifying ZEVAC if a user credential has been compromised or if you suspect possible suspicious activities that could negatively impact security of the ZEVAC services or your account.

  • You may not perform any security penetration tests or security assessment activities without the express advance written consent of ZEVAC.