Your Data Deserves Real Security Controls — Not Just a Privacy Policy
What is Zenphi's approach to data security? Zenphi was born in the cloud and designed from the ground up with security in mind. Every layer — transit, storage, access, and audit — is encrypted and independently verified, so security is never an afterthought bolted on later. Data encrypted in transit (TLS 1.2/1.3) and at rest (AES-GCM 256-bit via Google Cloud), access controlled through Google SSO and audited permissions, and independent third-party certifications across ISO 27001, GDPR, HECVAT, CASA Tier 2, and HIPAA.
Updated · Reviewed by the Zenphi Security & Compliance Team
Encrypted End-to-End — Transit → Storage → Access → Audit
In transit
TLS 1.2/1.3 on every transfer. Prevents man-in-the-middle interception of data in motion.
Encrypted
At rest
AES-GCM (256-bit) via Google Cloud. Applied to every database, blob store, and sensitive credential.
Encrypted
Access & audit
SSO + per-action authorization checks. Every action is logged and reviewable by the workspace admin.
Auditable
Five Certifications — Not Just a Claim on a Page
Zenphi undergoes independent third-party audits on a regular basis so you don't have to take our word for it. Request the latest report or verify our status directly with each governing body.
ISO/IEC 27001:2022 Certified
Zenphi complies with the ISO/IEC 27001:2022 standards for information security.
Read more about ISO/IEC 27001 → View the certificate →GDPR Compliance
Zenphi complies with the strict General Data Protection Regulation (GDPR) privacy legislation.
Read more about GDPR compliance →HECVAT Compliance
Zenphi complies with the HECVAT policies for higher education information security and data protection.
Read more about HECVAT →CASA Tier 2 Verified
Zenphi passed CASA Tier 2 assessment — a testament to our dedication to maintaining the highest standards in data protection and operational integrity.
Read more about CASA verification →HIPAA Compliance
Zenphi complies with the strict Health Insurance Portability and Accountability Act of 1996.
Read more about HIPAA →Security Isn't an Afterthought — It's How Zenphi Was Built
Zenphi was born in the cloud and was designed from the ground up with security in mind. Security-related best practices are an integral part of our work culture. We incorporate them in all parts of Zenphi — from product development to data handling, to operations.
No matter how well a system is designed, it's bound to run into a few hiccups. Even with an enterprise grade platform like Zenphi, our clients may sometimes run into issues that they may not be able to resolve themselves. In these circumstances, our clients know that they can depend on our support team to help them resolve these issues. But in this era of privacy and data regulation, many of our clients may not be so comfortable sharing this critical information with us.
"[In the future] more and more enterprises will become selective about what data they give to their vendors, even if that choice makes the product or service they're using less effective… [we] will see organizations choosing to opt-out of data sharing due to concerns about anonymization, privacy, and accidental disclosure."
— Forrester Research, Predictions 2020: CybersecurityAt Zenphi, we take customer data privacy seriously. The Zenphi platform was designed with security and privacy in mind. We have controls built into the product as well as policies that govern how we manage and operate our infrastructure.
What Data We Collect, and Why
In order to automate processes, Zenphi needs to store and utilize certain data. The stored data is required for providing automation services for our customers. We can classify this data into two categories.
Flow Reference Data
Data that is required for an execution of an instance of a flow. This data is required for the proper execution of the flow — without it, the flow would not be able to execute. For example, a flow triggered by a Google Form that updates a Sheet needs to store the information captured in the form so it can be passed to the "Update Row" step. All reference data stored by Zenphi is encrypted as outlined below.
Flow Metadata
Information about the flow execution — when the flow started/ended, when each step started/ended, the status of the flow, log stream messages, etc. This information is displayed in the recent runs and run details page.
Data Encryption and Security
It's important to ensure that all the data is secured while in transit as well as in storage (at rest).
Data in Transit
All data sent to/received from Zenphi services, as well as any internal calls, is encrypted using TLS v1.2/1.3. This prevents any "man-in-the-middle" attack, where a malicious third party tries to intercept and/or modify data being transmitted.
Data at Rest
All data stored by Zenphi is encrypted by Google Cloud. This covers all data stored in databases, blob storages, etc. Google Cloud uses AES-GCM (256 bits) encryption with keys backed by key stores to ensure all data is encrypted.
Sensitive Data at Rest
Client sensitive data — connection credentials, flow reference data and files, Zenphi vault tokens — gets an additional layer of protection: each workspace has a dedicated encryption key, itself encrypted by a Zenphi encryption key and stored in a key store.
How sensitive data encryption works
All sensitive information is encrypted by the workspace encryption key before it's stored in database or blob storage. All stored information is in turn encrypted by Google Cloud.
Managing Zenphi's Access to Your Data
This section explains the limited circumstances under which access to customer data may be required by Zenphi personnel, the internal controls that keep that access appropriate and limited, and the settings you can use to manage and control your own stored data.
How Does Zenphi Safeguard Your Data From Unauthorized Access?
Security and data privacy was not an afterthought at Zenphi — it forms the foundation of the entire Zenphi platform and was part of it from inception. At Zenphi, we follow a secure software development life cycle (SDL). From ideation to development, testing, deployment and maintenance, security best practices are followed and enforced throughout. This ensures any new feature that we develop does not inadvertently compromise on the security and data privacy of our customer's data.
Access controls are built into Zenphi. Only authorized users for a workspace are able to access data. All users are authenticated using Google single sign-on and assigned access tokens for workspaces that they have access to. These tokens contain security permission information, which is verified by Zenphi for every action they take in the system. All actions a user takes in the system are audited and can be viewed by the workspace administrator.
Within the workspace, users can control who can view/edit items such as flows, connections, etc. This privacy setting is enforced throughout the system.
Customer Controls Over Access to Data
At Zenphi, we are firm in the belief that: you own your data, and we will never use it for any purpose other than those necessary to fulfill our contractual/legal obligations. We understand that, in addition to our commitments, customers want additional transparency and control over their data in Zenphi. That is why Zenphi offers industry-leading controls to define how and when data is purged from our system.
While a flow is executing, Zenphi requires the flow reference data and metadata for it to be able to execute the flow to completion. When the flow completes, either successfully or in an erroneous state, this information is no longer required and can be purged. Customers can define how data is purged using the data handling global setting or override it on a per-flow basis — automatically upon completion, or on a schedule (e.g. 14 days after the flow has completed). There are 3 levels that customers can configure:
Preserve reference data and metadata
Lets customers diagnose and troubleshoot any issues, and aids Zenphi personnel if the customer raises a support request. All access to view reference data is audited. This allows re-running failed steps and using advanced error recovery mechanisms such as SmartResume.
Preserve metadata only
Purges all flow reference data and keeps only the flow instance metadata. With this option, diagnostics and advanced error recovery aren't possible, and Zenphi support can't perform in-depth troubleshooting since the data is no longer available.
Purge all data
All data is purged from the system. The only information that remains is when a flow ran and its status (e.g. completed, faulted). As with Level 2, the ability to troubleshoot a problematic flow is very limited.
With these options, customers have granular control over their data stored in Zenphi. For example, a customer could configure Level 2 when a flow completes successfully and Level 1 when it errors, plus a schedule on Level 3 to purge all information after 30 days regardless of flow state. If the flow succeeds, reference data is purged immediately; if it errors, the team can troubleshoot and rectify it before the 30-day schedule purges everything.
Access Authorizations for Zenphi Employees
All Zenphi employees undergo background checks, are required to execute a confidentiality agreement, and comply with Zenphi internal policies. The number of employees that may have access to customer data is limited, and systems are in place to actively monitor and log the activities of those employees.
Zenphi employees are only granted a limited set of default permissions to access company resources. Access to internal support tools is controlled via Access Control Lists (ACLs). A formal process is followed at Zenphi to grant or revoke employee access to Zenphi resources, and access is automatically removed for departing employees.
Access authorization is enforced at all relevant layers of the system and infrastructure. When a support engineer needs access to customer data for diagnostics, an approval workflow is triggered in Zenphi and required minimum privileges are granted on an as-needed basis. An employee's authorization settings are used to control access to all resources, including data and systems of the Zenphi platform.
Security and Compliance Standards
Our customers expect independent verification of security, privacy and compliance controls. At Zenphi, we undergo independent third-party audits on a regular basis to provide this assurance. The key international standard we are audited against:
- ISO 27001 – Information Security Management
Customers can request our latest certification report as well as verify our status with the ISO governing body.
Hosting
Zenphi is fully hosted on the Google Cloud Platform and benefits from the comprehensive security controls in place by Google Cloud Platform (cloud.google.com/security).
When signing up with Zenphi, you can choose one of our data centers to host your Workspace data. Your data will never leave the selected data center, so you can be sure you're complying with data sovereignty requirements. At the moment Zenphi offers the following data centers:
GDPR
Being a security and compliance centric company, Zenphi considers its data processing and protection of customers' privacy as one of the most important tasks. On top of that we do our best to comply with the EU's General Data Protection Regulation (GDPR) and to fulfil customers' rights under the GDPR regulation.
Our Commitment to You
Protecting customer data is a primary design consideration for the Zenphi platform. Our security practices are verified by independent third parties, providing assurances to customers regarding our security controls and practices. In line with our view that customers own their data, we offer advanced options for customers to control how their data is managed in the platform.
Security is an ongoing commitment at Zenphi, and we will ensure our customers can use our platform in a secure and transparent manner.
Protecting Customer Data Is A Design Requirement At Zenphi — Not An Afterthought
Independently audited, encrypted end-to-end, and built so you stay in control of your own data.