Arrows Security Details
Last updated: May 11th, 2022
Hosting and Data
Where is Arrows hosted?
Arrows is hosted on Heroku. Heroku utilizes AWS data centers for hosting. AWS data centers are accredited under:
- ISO 27001
- SOC 1 and SOC 2/SSAE 16/ISAE 3402 (Previously SAS 70 Type II)
- PCI Level 1
- FISMA Moderate
- Sarbanes-Oxley (SOX)
You can read more details about Heroku's security practices below:
- Security Assessments and Compliance
- Penetration Testing and Vulnerability Assessments
- Environmental Safeguards
- Network Security
- Data Security
- System Security
- Vulnerability Management
- Disaster Recovery
- Access to Customer Data
Arrows data is stored in Heroku Postgres. Data is backed up under Heroku's Continuous Protection ensuring customer data is incrementally snapshotted and backed up. We monitor our servers and logs and have an engineer on call 24/7.
Arrows is deployed multiple times per week, ensuring that any fixes can be deployed rapidly.
All Arrows web page requests are protected with SSL and HTTPS.
Our goal is to help you onboard your customers successfully, and we only store and use data in service of that end goal.
Where is data stored and processed?
All data is stored and processed in the United States with Salesforce's Heroku.
What third-parties do you share data with?
- Heroku - Data storage and hosting
- AWS - File storage
- Stripe - Payment processing
- Segment - Analytics
- June - Analytics
- Hightouch - Reverse ETL
- Postmark - Transactional Emails
- Hubspot - Marketing and sales
- Google Analytics - Pageviews & Conversions
- Reform - Forms
Arrows payments are processed by Stripe. Stripe is certified as a PCI Level 1 Service Provider—the most stringent level of certification available in the payments industry. Arrows does not handle any payment data.
Arrows does not store user passwords in our database. Instead we provide magic login links sent via email.
Security training is part of Arrows employee onboarding. Arrows employees use 1Password to manage and ensure secure passwords, and use 2 factor authentication where available.
Any further questions?
Great! Please email us at firstname.lastname@example.org and we'll happily update this doc.