Security Policy

Overview

At The Contentment Foundation we take the protection of customer data extremely seriously. This Contentment Foundation Security Policy describes the organizational and technical measures Contentment Foundation implements platform wide designed to prevent unauthorized access, use, alteration or disclosure of customer data. The Contentment Foundation services operate on Amazon Web Services (“AWS”) and Zeit. This policy describes activities of Contentment Foundation within its instance on AWS & Zeit unless otherwise specified. As you continue to learn more about Contentment Foundation we recommend you also review our Terms of Service and Privacy Policy.

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 all our staff on our policies.

• When security events are detected they are escalated to our emergency alias, teams are paged, 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.

• Contentment Foundation will promptly notify you in writing upon verification of a security breach of the Contentment Foundation services that affects your data. Notification will describe the breach and the status of Contentment Foundation’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.

• Our infrastructure is Serverless which allow us to deploy dozens of updates throughout the day, so we have high confidence that we can get a security fix out quickly when required.

Infrastructure

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

• All of our services are hosted in isolated environments and protected by Zeit security, as described at https://zeit.co/security. Contentment Foundation services have been built with disaster recovery in mind.

• All of our servers are hosted in Serverless environments with auto-scale and auto-disaster recovery options, allowing us to maintain uptime during attacks, courtesy of the built-in DDoS protection layer.

• 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 of our data are hosted in AWS facilities in the USA and protected by AWS security, as described at http://aws.amazon.com/security/sharing-the-security-responsibility. Our data stores are scaled across 3 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, Contentment Foundation builds on the physical security and environmental controls provided by AWS. See http://aws.amazon.com/security for details of AWS security infrastructure.

• Contentment Foundation uses a backup solution for datastores that contain customer data.

Data

• 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).

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

Data Transfer

• Our API and application endpoints are TLS/SSL secure.

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

• We control the data access using role based permissions.

Authentication

• Contentment Foundation is served 100% over https.

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

Permissions and Admin Controls

• All internal permissions and admin controls are distributed through secure 256-bit AES encryption to only relevant parties.

• Also the permissions and data distributed is controlled by each requirement.

Application Monitoring

• All access to Contentment Foundation websites and applications is logged and audited.

Payment Processing

• All payment instrument processing for purchase of the Contentment Foundation services is performed by Stripe. For more information on Stripe’s security practices, please see https://stripe.com/docs/security/stripe.

Customer Responsibilities

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

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

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

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

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