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 firstname.lastname@example.org if you have any questions or comments.
Web portal connectivity
- 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).
- 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.
- 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 data
All customer data, besides what is listed below, is removed from Fivetran's system within 24 hours using object lifecycle management. Fivetran retains subsets of a customer's data that are required to provide and maintain Fivetran's solution. This includes only:
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 stored securely in a key management system backed by a hardware security module managed by our cloud provider.
Customer metadata - Fivetran retains data points such as table and column names for each integration so that this information can be shown to your organization in Fivetran's user interface.
Event data from Webhooks and Snowplow.js - If you use Fivetran to store webhooks or Snowplow event data, we will persistently store that data so that it can be re-synced if that is ever needed. By default, we store that event data in an online bucket in the US, separate from the region you select for the rest of your account. If you prefer, you can configure Fivetran to store event data in a bucket you manage.
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 is 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.
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 safeguards
Since Fivetran relies on Google Cloud Platform, physical and environmental security is handled entirely by Google. Google provides an extensive list of compliance and regulatory assurances, including SOC 1/2-3, PCI-DSS and ISO27001. See Google Cloud Platform compliance, security, and data center security documentation for more detailed information.
Your organization permissions
- 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.
- 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 privacy
- 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, 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.
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 and never resides in Fivetran systems for more than 24 hours.
In the event of a data breach
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 policy
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 email@example.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 and will attempt to keep you regularly informed of our progress toward resolving the vulnerability. If you have followed the above instructions, we will not take any legal action against you regarding the report.