Security Overview

Fivetran is committed to security and focused on keeping you and your data safe. Fivetran adheres to industry-leading standards while connecting, replicating, and loading data from all of your data sources. To learn about Fivetran security in detail, see our security white paper.

Contact security@fivetran.com if you have any questions or comments.

Web portal connectivitylink

• All connections to Fivetran’s web portal are encrypted by default using industry-standard cryptographic protocols (TLS 1.2+).
• Any attempt to connect over an unencrypted channel (HTTP) is redirected to an encrypted channel (HTTPS).
• To take advantage of HTTPS, your browser must support encryption protection (all versions of Google Chrome, Firefox, and Safari).

Connectorslink

• Connections to customers’ database sources and destinations are SSL encrypted by default.
• Fivetran can support multiple connectivity channels
• Connections to customers’ software-as-a-service (SaaS) tool sources are encrypted through HTTPS.

Permissionslink

• Databases and API cloud applications - Fivetran only requires READ permissions. For data sources that by default grant permissions beyond read-only, Fivetran will never make use of those permissions.
• Destinations - Fivetran requires the CREATE permission. This permission allows Fivetran to CREATE a schema within your destination, CREATE tables within that schema, and WRITE to those tables. Fivetran is then able to READ only the data it has written.

Retention of customer datalink

All customer data, besides what is listed in the Exceptions section, is purged from Fivetran’s system as soon as it is successfully written to the destination. For normal syncs, this means data exists in our system for no more than eight hours. There are some cases where the retention period may be longer, as described below. In the following two cases, customer data is automatically purged after 30 days using object lifecycle management.

• Destination outage - Fivetran maintains data that has been read from your source if the destination is down, so we can resume the sync without losing progress once the issue is resolved.
• Retrieving schema information for column blocking or hashing purposes - For newly created connectors, if you choose to review your connector schema before syncing in order to use column blocking or hashing, we queue your data while we read the full schema and only write it to the destination once you approve.

Exceptionslink

Fivetran retains subsets of a customer’s data that are required to provide and maintain Fivetran’s solution. This only includes the following data:

• Customer access keys - Fivetran retains customer database credentials and SaaS OAuth tokens in order to securely and continuously extract data and troubleshoot customer issues. These credentials are securely stored in a key management system. The key management system is backed by a hardware security module that is managed by our cloud provider.

• Customer metadata - Fivetran retains configuration details and data points (such as table and column names) for each connector so that this information can be shown to your organization in your Fivetran dashboard.

• Email attachments collected by Email connector - If you use Fivetran to collect and store email attachments in JSON or CSV format, we back up and permanently store these attachments in an internal S3 bucket so that they can be re-synced if needed.

• Event data from the Webhooks connector and other connectors using webhooks - If you use Fivetran to sync webhooks and event data, we store that data so that it can be re-synced if needed. The data retention period depends on the connector type.

  Click to see the complete list of connectors using webhooks and their respective data retention period

  Connector	Data Retention Period	Note
  AppsFlyer	30 days
  Eloqua	30 days
  Github	30 days
  Greenhouse	30 days
  Help Scout	30 days
  Hubspot	30 days
  Intercom	30 days
  Iterable	30 days
  Jira	30 days
  Pipedrive	30 days
  ReCharge	30 days
  Branch	Persistent
  Mandrill	Persistent
  Segment	Persistent	If you chose to use webhooks instead of S3 bucket
  SendGrid	Persistent
  Shopify	Persistent
  Snowplow	Persistent
  SurveyMonkey	Persistent
  Webhooks	Persistent

  By default, we store that event data in a cloud storage service in one of the following locations:

  • the EU region (for destinations run in the EU region)
  • the US region (for all other destinations)

  NOTE: For the Webhooks connector, you can configure Fivetran to store event data in a bucket you manage, if you prefer.

• Temporary data - Some data integration or replication processes may use ephemeral data specific to a data source. This stream of data is essential to the integration process and is deleted as soon as possible, though it may briefly exceed 24 hours in rare instances. Examples of this temporary data include Binary Logs for MySQL or the Event Stream for Asana.

Solution infrastructurelink

Access to Fivetran production infrastructure is only allowed via hardened bastion hosts, which require an active account protected by MFA (multi-factor authentication) to authenticate. Further access to the environment and enforcement of least privilege is controlled by IAM (identity and access management) policies. Privileged actions taken from bastion host are captured in audit logs for review and anomalous behavior detection.

Physical and environmental safeguardslink

Physical and environmental security is handled entirely by our cloud service providers. Each of our cloud service providers provides an extensive list of compliance and regulatory assurances, including SOC 1/2-3, PCI-DSS, and ISO27001.

Googlelink

See the Google Cloud Platform compliance, security, and data center security documentation for more detailed information.

Amazonlink

See the Amazon Web Services compliance, security, and data center security documentation for more detailed information.

Fivetran data residencylink

Fivetran runs data connectors on servers in the United States (US), Canada, European Union (EU), United Kingdom (UK), Australia, and Singapore. You can select your preferred data processing location when configuring your destination. All connectors configured in a destination run in the destination’s designated location. This means that in most cases, your data will not leave our region-specific servers during processing. For example, if you configure your destination to use our EU servers, your data will not leave the EU during processing. See our destination documentation to learn how to configure your data processing location.

The exception to this rule are connectors that sync webhooks and event data. By default, we store that event data in a cloud storage service in one of the following data processing locations:

• the EU location - for destinations run in the EU location
• the US location - for all other destinations

Fivetran runs our services on Google Cloud Platform (GCP) and Amazon Web Services (AWS). The following table lists regions supported by Fivetran for each service provider:

Regardless of the plan you use, you can select the geography when creating a destination. If you are on an Enterprise or Business Critical plan, you also can select the cloud service provider. Lastly, if you are on a Business Critical plan and select AWS as a cloud service provider, you can select a cloud region.

NOTE: For GCP, we don’t provide choice of the cloud region.

IMPORTANT: You need to allowlist the corresponding Fivetran IPs in your firewall for the geography and region you selected for your destination.

Your organization permissionslink

• Users can use Single Sign-On through Google Apps.
• Only users of your organization registered within Fivetran and Fivetran operations staff have access to your organization’s Fivetran dashboard.
• Your organization’s Fivetran Dashboard provides visibility into the status of each integration, the aforementioned metadata for each integration, and the ability to pause or delete the integration connection - not organization data.
• Organization administrators can request that Fivetran revoke an organization member’s access at any point; these requests will be honored within 24 hours or less.

Company policieslink

• Fivetran requires that all employees comply with security policies designed to keep any and all customer information safe, and address multiple security compliance standards, rules and regulations.
• Two-factor authentication and strong password controls are required for administrative access to systems.
• Security policies and procedures are documented and reviewed on a regular basis.
• Current and future development follows industry-standard secure coding guidelines, such as those recommended by OWASP.
• Networks are strictly segregated according to security level. Modern, restrictive firewalls protect all connections between networks.

Compliance and privacylink

• Fivetran regularly (annually) undergoes its own, independent AT101/SOC2 audit, and the report is made available under NDA to all existing and prospective customers by request under NDA. This comes in addition to the benefits from the comprehensive set of Google Cloud Platform compliance programs.
• Fivetran maintains an Information Security Management System (ISMS) that complies with the requirements of ISO 27001 (Security, Availability, and Confidentiality criteria). ISO/IEC 27001 certification applies to the overall Fivetran infrastructure and all products. See our ISO/IEC 27001 certification.
• Fivetran, in its potential role as data subprocessor, adheres to the principles of the EU94/95 privacy rules as well the upcoming GDPR rules when they are in effect.
• Fivetran’s Privacy Policy

HIPAAlink

Under The HIPAA Security Rule, Fivetran does comply with HIPAA requirements for Protected Health Information (PHI) and will sign a Business Associate Agreement (BAA) with customers who are subject to HIPAA mandates (typically, HIPAA covered entities). Fivetran is not a covered entity under HIPAA rules, and therefore cannot be “HIPAA compliant”, since HIPAA itself applies to covered entities (that is, those entities that are subject to regulation by the HHS). Fivetran serves as a data pipeline, which means that PHI traversing the Fivetran environment is never permanently stored. All transmissions are encrypted using industry best practices (at present, TLS 1.2+). Temporary storage may occur when the amount of data transmitted exceeds the capacity for real-time processing, and as a result, requires short-term caching. Such temporary storage is encrypted. All customer data, including PHI, is purged from Fivetran’s system as soon as it is successfully written to the destination.

In the event of a data breachlink

To date, Fivetran has not experienced a breach in security of any kind. In the event of such an occurrence, Fivetran protocol is such that customers would be made aware as soon as the compromise is confirmed.

Responsible disclosure policylink

At Fivetran, we are committed to keeping our systems, data and product(s) secure. Despite the measures we take, security vulnerabilities will always be possible.

If you believe you’ve found a security vulnerability, please send it to us by emailing security@fivetran.com. Please include the following details with your report:

• Description of the location and potential impact of the vulnerability
• A detailed description of the steps required to reproduce the vulnerability (POC scripts, screenshots, and compressed screen captures are all helpful to us)

Please make a good faith effort to avoid privacy violations as well as destruction, interruption or segregation of services and/or data.

We will respond to your report within 5 business days of receipt. If you have followed the above instructions, we will not take any legal action against you regarding the report.

Diagnostic data accesslink

IMPORTANT: Fivetran cannot access your data without your approval.

When working on a support ticket, we may need to access your data to troubleshoot or fix your broken connector or destination. In that case, we will ask you to grant Fivetran access to your data for the next 21 days. You can allow or deny data access. If you grant us data access, you can revoke it at any moment before the 21-day diagnostic period has expired.

See our Getting Support documentation for more details.