Security Policy

EFFECTIVE DATE: October 25, 2018


At Canopy we take the protection of customer data extremely seriously. This Canopy Security Policy describes the organizational and technical measures Canopy implements platform wide designed to prevent unauthorized access, use, alteration or disclosure of customer data. The Canopy services operate on Amazon Web Services (“AWS”); this policy describes activities of Canopy within its instance on 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 mature software providers.

Best Practices

Incident Response Plan

  • We have implemented a formal procedure for security events and have educated all 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.
  • Canopy will promptly notify you in writing upon verification of a security breach of the Canopy services that affects your data. Notification will describe the breach and the status of Canopy’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 within minutes.
  • We typically deploy code several times a week, so we have high confidence that we can get a security fix out quickly when required.


  • All of our services run in the cloud. Canopy does not run our own routers, load balancers, DNS servers, or physical servers.
  • All of our services and data are hosted in AWS facilities in the USA and protected by AWS security, as described at Canopy services have been built with disaster recovery in mind.
  • All of our infrastructure is spread across 3 AWS data centers (availability zones) and will continue to work should any one of those data centers fail unexpectedly. Amazon does not disclose the location of its data centers. As such, Canopy builds on the physical security and environmental controls provided by AWS. See for details of AWS security infrastructure.
  • 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.


  • All customer data is stored in the USA.
  • Customer 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 Canopy system used to process customer 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 Canopy 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.


  • Canopy is served 100% over https.
  • There are no corporate resources or additional privileges from being on Canopy’s network.
  • We have two-factor authentication (2FA) and strong password policies on GitHub, Google, AWS MongoDB and Canopy to ensure access to cloud services are protected.

Permissions and Admin Controls

  • Canopy enables permission levels to be set for any employees with access to Canopy.
  • 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 use S3/Glacier for archival purposes.
  • All access to Canopy applications is logged and audited.

Security Audits and Certifications

Payment Processing

All payment instrument processing for purchase of the Canopy services is performed by Stripe. For more information on Stripe’s security practices, please see

Customer Responsibilities

  • Managing your own user accounts and roles from within the Canopy services.
  • Protecting your own account and user credentials by using two-factor authentication for all of your employees accessing the Canopy services.
  • Compliance with the terms of your services agreement with Canopy, including with respect to compliance with laws.
  • Promptly notifying Canopy if a user credential has been compromised or if you suspect possible suspicious activities that could