"Keeping our customers' data secure is the most important thing that Journey does."
We would like to make two things clear. First, we respect your privacy and take significant efforts to protect all your data. Second, we would never do anything with your data that we wouldn’t be proud to tell the world about.
Keeping our customers’ data secure is the most important thing that Journey does. We go to considerable lengths to ensure that all data sent to Journey is handled securely – keeping Journey secure is fundamental to our business.
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 like Amazon and Facebook.
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.
Should a security breach occur and customer data is exposed, Journey will promptly notify you as well as the competent data protection authority within 72 hours, in compliance with the EU General Data Protection Regulation (Regulation (EU) 2016/679) which comes into effect in May 2018.
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 dozens of times a day, so we have high confidence that we can get a security fix out quickly when required.
All of our services run in the cloud. Journey does not run our own routers, load balancers, DNS servers, or physical servers.
The vast majority of our services and data are hosted in Amazon Web Services (AWS) facilities in the USA, and we are in the process of consolidating all services and data there. Journey 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.
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.
Journey uses MongoDB’s MMS backup solution for datastores that contain customer data.
We have uptime of 99.9% or higher. You can check our past month stats athttps://status.journey.hr
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 to ensure data privacy and prevent one customer from accessing another customers data. 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.
All data sent to or from Journey 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.
Intercom is served 100% over https. Journey runs a zero-trust corporate network.
There are no corporate resources or additional privileges from being on Intercom’s network.
We have two-factor authentication (2FA) and strong password policies on GitHub, Google, AWS MongoDB and Intercom to ensure access to cloud services are protected.
Permissions and Admin Controls
Journey enables permission levels to be set for any employees with access to Journey.
Permissions and access can be set to include app settings, billing, user data, or the ability to send/edit manual messages and auto messages.
On an application level, we produce audit logs for all activity, ship logs to Logentries for analysis, and use S3/Glacier for archival purposes.
All access to Journey applications is logged and audited.
Bastion hosts are used to login to devices.
All actions taken on production consoles or in the Journey application are logged.
We bi-annually engage with well-regarded third-party auditors to audit our code-base, and work with them to resolve potential issues.
We use technologies such as Logentries, AWS Cloudtrail and Security Monkey to provide an audit trail over our infrastructure and the Journey 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.
Journey complies with the U.S.-E.U. Safe Harbor Framework and the U.S.- Swiss Safe Harbor framework as set forth by the U.S. Department of Commerce regarding the collection, use and retention of personal data from European Union member countries and Switzerland.
Journey, Inc. has certified that it adheres to the Safe Harbor Privacy Principles of notice, choice, onward transfer, security, data integrity, access, and enforcement.
Journey is not subject to PCI obligations. All payment instrument processing is outsourced to Stripe.