Trust & Privacy

The terms governing the processing of personal data by Qlik on behalf of customers are set out in our Data Processing Addendum. Qlik may be a data processor on behalf of customers in two scenarios, subject to our written agreements:

1. Cloud: Qlik is the data processor of personal data within customers’ content data while it resides in our cloud offerings. Our cloud offerings are no-view encrypted services, with customer content data, and any personal data within it (and access to it), decided and controlled by the customer; and/or
2. Qlik Services: When Qlik provides support or consulting services to a customer, customers may choose to share content data (from the cloud or a client-managed deployment) with Qlik, which may contain personal data. Such sharing, and whether the content data contains any personal data, is at the discretion and control of the customer. Personal data aspects within content data, in particular for Qlik Support, should be anonymized or minimized by the customer as per privacy law data anonymization/minimization best-practices prior to sharing with Qlik, for example before upload to the support portal on Qlik Community.

Like other software providers, Qlik is not a data processor for customers’ content within their client-managed deployments, as any content data a customer chooses to put into or create in the Qlik client-managed deployment stays on the customer's system(s), unless it is otherwise shared by the customer with Qlik (e.g., for Qlik services).

For our cloud offerings, yes. We host your content data only in the location you choose.

Qlik Cloud has six tenant locations. Ireland (EMEA 1), Frankfurt (EMEA 2), London (EMEA 3), USA (Americas), Australia (APAC 1) and Singapore (APAC 2). Please note that the back-ups are also in the same data-region (with the EMEA back-ups: EMEA 1 in France, EMEA 2 in Italy & EMEA 3 in Spain, AMERICAS back-up in USA, APAC 1 in Australia, and APAC 2 in South Korea).

Talend Cloud has four tenant locations: Germany, Japan, Australia and two in the United States (one utilizing AWS infrastructure, one utilizing MS Azure Infrastructure). Backups of our Talend Cloud are stored in-region in the U.S., EU and APAC.

Our customers control access to their tenant and who they invite into their tenant (and where these users are).

For on-premise customers, your content data is hosted on your systems in the location(s) you select. Qlik does not host, or have access to, this content data.

For Qlik services (technical support, consulting, etc.), customers may choose to share their content data from their cloud offering or their on-prem deployments. However, Qlik does not typically require sensitive/content data to perform our services, and the data we receive for such services does not typically contain any personal data. Such sharing, for example what data a customer inputs/attaches to a technical support ticket, is at the discretion and control of the customer. Any sensitive content, such as personal data aspects, should be anonymized or minimized by the customer as per privacy law data anonymization/minimization best-practice prior to sharing with Qlik, for example before upload to the support portal on Qlik Community. Please note that content data provided to Qlik for services may leave the customer’s country/region. This is because, while Qlik support is generally provided in-region to customers, Qlik’s support model is 24/7/365 (“follow-the-sun”) in order to provide continuous support to our customers. As such, support tickets may be dealt with by Qlik team members outside the customer’s region and support content data may be stored/accessible abroad. For Qlik consulting, while our consulting team members tend to primarily service customers in the same region, we may rely on consulting resources and systems outside of the customer’s region in order to best serve our customers. Further information is available in our International Transfers/Schrems II FAQ.

Qlik’s subprocessor list is available here. Qlik’s responsibilities relating to subprocessors are set out in our Data Processing Addendum.

Our privacy program and measures include:

• Appointing a global Data Protection Officer.
• Measures to safeguard the lawful transfer of personal data between group companies in different countries.
• Maintaining a Record of Processing Activities, as required by laws such as GDPR’s Article 30.
• Privacy-By-Design and Privacy-By-Default processes, e.g., in our vendor vetting and in our R&D/product development processes.
• Data retention and access governance.
• Implementing Privacy Policies and Notices on various topics, from website data collection to our products.
• Providing customers with a Data Processing Addendum, enabling them to provide us personal data of theirs.
• Maintaining a data incident detection and response program.
• Regular privacy and security training.
• Honoring data subject rights requests.
• Certification of our U.S. operating companies under the EU-US Data Privacy Frameworks.

Our cloud offerings are no-view services. Customer content, and access to it, is decided and controlled by the customer and its users. Qlik’s Data Processing Addendum enables customers to input personal data content (as defined under laws such as the UK and EU’s GDPRs, Brazil’s LGPD, California’s CCPA, etc.) into our cloud offerings. If your organization has signed a Business Associate Agreement (BAA) with Qlik, this enables you to input US PHI (as defined under US HIPAA) into our cloud offerings.

As a general software provider our offerings are generally not subject to industry-specific laws. Visit our Trust & Security page to view our certifications/attestations, including those relating to specific industries. Subject to our agreements with you customers may determine, in light of their particular country and industry requirements, whether the controls of our cloud offerings meet their particular (e.g., industry specific) requirements and decide whether to put their industry-specific data into our cloud offerings. Further information regarding security, controls and certifications and can be found on our Trust & Security page.

As our cloud offerings are not PCI DSS certified, customers should not store PCI DSS data in our cloud offerings.

For Qlik's on-premise products, which are client-managed, Qlik does not receive the content that the customer puts in the software. For support and consulting services, support case attachments and/or consulting-related data are only accessible to those that need access as part of their job responsibilities. All Qlik personnel are bound by confidentiality obligations and receive training on data protection and security.