Arrows Security Details

Last updated: November 1st, 2023


We take security very seriously at Arrows. From day one the product and all features have taken security into account. This page describes Arrows' approach and practices around security. You may also be interested in our privacy policy and terms of service.

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:

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?

Please view a list of our subprocessors.


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 is built with Ruby on Rails and benefits from 16 years of security work on the framework. Our Ruby and Javascript dependencies are audited for vulnerabilities on every deploy using bundler-audit and yarn audit respectively. Dependencies are updated monthly to ensure we receive the latest security updates.

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 and we'll happily update this doc.