Security and Compliance | Quickbase
People collaborating on a project

Security and Compliance

updated 7/15/2021

A Legacy of Trust

Quickbase was a division of Intuit, a global leader in financial and business solutions, from 1999 until its divestiture in 2016. Today, Quickbase is building on a long legacy of Trust (one of our core values) to continue to meet higher levels of security and compliance enabling our customers to build and deploy secure Quickbase apps in mission critical use cases.

Our Mission

  • Embedding best practices into everything we do, in every part of our company
  • Alignment of our processes and controls with industry standards
  • Being transparent with our customers and continuing to learn from them

Shared Responsibility

Security and confidentiality is a shared responsibility between Quickbase and our customers. Quickbase provides a secure platform, and provides the tools, support and training resources that enable our customers to build and maintain secure apps.

Customers have numerous responsibilities around the security of Quickbase apps and data held within them. Customers must understand what data they intend to collect and store in their Quickbase apps, and ensure that risk and compliance requirements are addressed which correlate to the importance and classification of that data. Customers must ensure that security is addressed in the development of Quickbase apps, including ensuring that apps are shared with only those who are authorized to access them.

Security Governance

Quickbase’s Compliance & Information Security Officer, part of the Executive Management team, sets the vision and strategy for the company’s security and compliance program, with the goal of providing strategic direction, ascertaining that risks are managed appropriately and ensuring that objectives are achieved. Quickbase’s Security Team is responsible the design and implementation of security tooling, risk identification and mitigation and aligning our corporate, development and infrastructure controls with best practices in line with Quickbase's business and compliance objectives.

Background Checks and Security Training

All Quickbase staff undergo background checks before they’re hired. All Quickbase staff are also required to take mandatory security, ethics and privacy training once they join Quickbase and on an ongoing basis during their employment with Quickbase.

Security in Software Development

Quickbase integrates security testing into each phase of the development life-cycle —from static code security scans, to dynamic web scans which run daily. We train our development team on how to develop securely using best practices.

Data and Operational Security

Customer Data Segregation

Quickbase is a multi-tenant application Platform as a Service (aPaaS) with logical access segregating each customer’s data. Quickbase customer control logical access to their data via authentication and authorization at the Realm, Account and Application layers. Realms, otherwise thought of as a sub-domain, hold customer Accounts. Within accounts are Quickbase Applications which are built and managed by the customer. Customers manage access and permissions at the Realm, Account and App layers via the Quickbase platform.

Access Control

Customers provision access to the Quickbase apps they develop and deploy to their Quickbase Realm. Quickbase supports Single Sign on and user provisioning/ de-provisioning via the Security Assertion Markup Language (SAML). Quickbase Groups may be used by customers to provision Role Based Access Control to Quickbase apps, at the app, form or field layer.

Quickbase staff do not have access to customer Quickbase apps unless they are invited or authorized by the customer. Quickbase developers occasionally require read/only access to systems which hold metadata, scripts and app schema in order to troubleshoot. A small team of operations personnel have administrative access to the infrastructure which hosts the Quickbase platform.


In Motion: Quickbase encrypts customer data in motion and at rest. All communications over non-trusted Internet networks are encrypted at up to 256 bit (SHA2) TLS certificate, TLS 1.2 and 1.3.

At Rest: Quickbase encrypts all of your app data and any file attachments attached to your Quickbase apps at the application layer using a AES 256 key. Customers may choose to manage a unique key for their Quickbase Realm (a Realm is Quickbase parlance for a customer's security domain within Quickbase). Realm-specific encryption keys provide an additional means to ensure the privacy and confidentiality of that data. In addition to having a unique encryption key, customers who subscribe to this feature can rotate realm-specific encryption keys on their own schedule. To set up realm-specific encryption keys for your organization, please open a support case.


Quickbase’s operations team employs automated incident detection, escalation technologies and procedures which ensure that any infrastructure or sub-service provider issue is rapidly addressed, 24x7x365. Customers may view and subscribe to service status updates at

Logging and Auditing

Logs from the servers, devices and services which power the Quickbase platform are off-loaded and secured in a 3rd party log management platform which performs log analysis, alerting and reporting as well as investigation capabilities for Quickbase operations, engineering and security teams who support the Quickbase platform. These operational logs are retained for 6 months.

Quickbase provides Audit logs as an optional feature for customers. Audit logs provide your Quickbase realm administrator a view of your Quickbase realm user activity, data and schema changes to your apps. Customers may choose to retain audit log data for 6 months, 1, 3 or 7 years.


Quickbase data is continuously replicated from the production to the hot standby data center. In each data center, Quickbase app and file attachment data is backed up via a daily snapshot from online storage to alternate online storage within the same data center. Quickbase maintains 14 daily snapshots and 6 months of weekly snapshots. This same procedure is done in the disaster recovery data center. The backup data is encrypted by virtue of the fact that the data is encrypted at the application layer. Removable backup media is not used, hence there is no physical transportation of media. Additionally customers may download their Quickbase application data at any time. For more information consult our help article on backups.

Disaster Recovery and Business Continuity

Each component of the infrastructure which powers Quickbase — from network equipment to web, app and database servers—is highly available and redundant. If something were to drastically impact our production services, our DR capabilities are best in class. Quickbase maintains 2 identical, geographically diverse, production-ready data centers. Production data is replicated to the hot standby data center with up to a 15 minute delay, i.e., a recovery point objective (RPO) of 15 minutes. If an issue were to impact the production site, we only need 2 hours to bring up production at the DR site, i.e., a recovery time objective (RTO) of 2 hours. We periodically (2-4 times per year) switch between the two data centers as part of our normal disaster recovery plan validation process. Switching between data centers allows us to ensure that Quick Base’s disaster recovery plan is tested and working properly should there ever be a real disaster.

Incident Response

Quickbase employs tools and process which monitor the platform, network, server and service components which make up the Quickbase services, and has a dedicated security team and incident response processes. Quickbase commits to notifying affected customers of any suspected or confirmed unauthorized access to information via e-mail or phone.

Data Sovereignty

Quickbase stores and processes data held in Quickbase apps in the U.S.A. Quickbase does not transfer customer Quickbase app data outside of the Quickbase hosted service hosted in the United States, or to any third-party, without customer authorization.

Data Portability

Data portability allows organizations to move, copy or transfer data easily from their Quickbase apps to other systems. Customer's authorized users may download their app data any time in CSV, Tab-delimited or XML format, via the web interface or our APIs.

Data Retention

Customers are in control and responsible for implementing their data retention requirements for the data they upload to Quickbase apps. Quickbase purges customer data from the online Quickbase platform if you terminate your service with Quickbase. After which, data will be held in Quickbase backup systems for 6 months. Upon data being fully purged from Quickbase backup systems Quickbase will send authorized customer contacts a Certificate of Data Destruction, certifying your app data is completely purged from all Quickbase systems.


Quickbase apps can be configured by the app builder to send reports via email. Quickbase uses a third party service to send reports via email which employs opportunistic TLS. This means that if a customer’s email system supports TLS encryption, email delivered from QB apps will be encrypted in transit (i.e., from the Quickbase Service to the customer’s email system over the Internet).

By default, Quickbase only allows emails sent from a customer realm to be sent to users within that realm, however, authorized customer account administrators may submit a care support case to enable apps within their realm to send emails to other individuals.

Quickbase Sync and Pipelines Gmail Connection and Google API Services

As part of the Quickbase Service, Quickbase allows Quickbase users to synchronize information from their own Google accounts with their own Quickbase applications. Quickbase's use of information received, and Quickbase's transfer of information to any other app, from Google APIs will adhere to Google's Limited Use Requirements (specified in the Google API Terms of Service, Google API User Data Policy).

Security Assurance and Compliance

FDA Compliance


Quickbase conducts annual 3rd party attestations for several compliance standards and regulations including SOC 1/2/3, HIPAA and DFARS.

Cloud Security Alliance

CSA's Security, Trust and Assurance Registry (STAR) is a free, publicly accessible registry that documents the security controls provided by cloud computing offerings, thereby helping organizations assess the security of cloud providers they currently use or are considering contracting with. Quickbase has completed and published its Consensus Assessments Initiative Questionnaire (CAIQ), which provides industry-accepted ways to document the security controls in our PaaS (platform as a service) offering. The CAIQ provides a set of over 140 questions that a cloud consumer and cloud auditor may wish to ask of a cloud provider.

Quickbase's CAIQ is available for download from the CSA Star Registry.

Pen Tests

Quickbase contracts with a 3rd party security firm to conduct a comprehensive security penetration test on an annual basis. Our pen test report is available to customers or prospective customers under NDA.

Vulnerability Scans

Quickbase employs a variety of tools and processes including static code analysis and dynamic web application scans designed to detect security vulnerabilities. Customers may run a security scan against the Quickbase platform under the following conditions:

  • The customer can only test using their own Quickbase application(s) with up to three (3) applications accessed during the testing.
  • The methodology for the test should mimic normal user activities with both normal pace and normal user volume.
  • This should not be a performance test or a denial of service test.
  • The customer should conduct the test during non-business hours to minimize the chance of negatively impacting their own users.
  • The customer must open a support case with Quickbase Customer Care to test up to 3 apps at least 5 business days prior to the security scan and provide the following information:
  • The application URL(s) against which the test will be conducted.
  • The source IP address from which the test will be conducted.
  • The date and time the test will begin and end.
  • The name and contact information of a person or persons with the direct ability to stop the testing if asked to do so by Quickbase staff.

Quickbase reserves the right to block any testing which negatively impacts the platform.

What details should you include when reporting a security issue to Quickbase?

Please provide as many relevant details as you can. In particular: What steps someone can follow to reproduce the issue. Any patches or steps to mitigate the problem.

Secure Data Centers

The Quickbase platform is hosted at Flexential Tier 4 data centers located in Las Vegas, NV and Denver, CO. Flexential has spent nearly two decades building world class data centers with the sole purpose of providing best-in-class colocation and network services designed to meet the most demanding IT requirements. Additionally Quickbase utilizes Amazon AWS for ancillary services such as WebHooks and Quickbase Sync and Google Cloud for Quickbase Pipelines.

SOC Reports

Quickbase undergoes an annual SSAE18 SOC 1/2/3 Type 2 examination covering Security and Availability Trust Services Principles defined by the AICPA Trust Services Principles and Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy. Quickbase began including SOC 1 audit in 2017. Please note customer app and realm controls are not part of the scope of Quickbase's SOC reports; therefore customers may want to include these pertinent Quickbase controls in their respective SOC examination.

Quickbase's SOC 1/2 reports are issued in July annually and is available to customers or prospective customers under NDA. Quickbase's SOC 3 report is publicly available and provides a summary of the Quickbase SOC 2 report. Download the 2021 report here.


The Health Insurance Portability and Accountability Act (“HIPAA”) is a United States law that applies to companies and other entities involved in the healthcare industry that may have access to patient information (called “Protected Health Information”, or “PHI”).

Quickbase abides by the HIPAA Security and Privacy rules in our operation of the Quickbase platform. Quickbase performs an annual HIPAA Attestation as part of our annual SOC examinations conducted by a 3rd party audit firm which validates Quickbase controls meet or exceed the requirements.

Quickbase enables its customers to build HIPAA-compliant applications. Quickbase's Customers are responsible for determining if they are a Covered Entity or Business Associate under HIPAA (and whether a business associate agreement with Quickbase is required) and for ensuring that it uses Quickbase in compliance with HIPAA. Customers who store or process Protected Health Information must sign a business associate agreement with Quickbase. Quickbase will sign BAAs with our customers on annual or multi-year contracts.


GxP is a collection of quality guidelines and regulations applicable to life sciences organizations that make food and medical products such as drugs, biologics, medical devices and medical software applications. GxP regulations include those requirements outlined in US FDA CFR Title 21 Part 11.

The platform and underlying technology is maintained to meet best practices so customers can build and support applications subject to FDA and GxP requirements. Our GxP Assurance Package shows the platform meets the requirements of compliance regulations such as US FDA CFR Title 21 Part 11.


Quickbase utilizes a PCI compliant vendor to process credit cards for our customers. However, the Quickbase platform itself has not undergone a PCI audit, therefore credit card data should not be stored in Quickbase apps.

NIST 800-171

A growing number of customers are adopting Quickbase to handle unclassified Department of Defense (DoD) Covered Defense Information (CDI) including
Controlled Unclassified Information (CUI), Personal Identifiable Information (PII), Protected Health Information (PHI), and other mission-critical data requiring protection from unauthorized disclosure. NIST Special Publication 800-171, Protecting Covered Defense Information in Nonfederal Systems and Organizations, otherwise known as DFARS (Defense Federal Acquisition Regulation Supplement), details the fourteen families of security requirements for protecting the confidentiality of CDI. Quickbase incorporates NIST 800-171 controls into its operation and management of the Quickbase platform and provides independent attestation to our compliance via our annual 3rd party SOC examination. As with our SOC 2 this report is available to customers or to prospective customers under NDA.


FERPA governs use of that data when schools and districts use Quickbase apps which includes FERPA regulated data.

Educational institutions are responsible for maintaining FERPA compliance when handling personal data of their students. These responsibilities include identifying data elements which are uploaded to QuickBase, maintaining access and sharing permissions appropriately, and being transparent with students as to data sharing arrangements with service providers

As a service provider, Quickbase enables education institutions who use Quickbase apps for FERPA data to be compliant with FERPA by:
• Maintaining security of the Quickbase platform via security plans and controls.
• Not sharing or disclosing our app data to any 3rd party.
• Not using customer app data for unrelated activities such as data mining.
• Implementing customer security breach notification procedures.
• Purging app data at end of service contract.

For more information about FERPA, visit the Privacy Technical Assistance Center at the US Dept of Education at

HECVAT, aka the Higher Education Community Vendor Assessment Toolkit, is a questionnaire framework specifically designed for higher education to measure vendor risk of service providers like Quickbase. Quickbase provides an up to date completed HECVAT questionnaire to assist education institutions with their due diligence.


Electronic discovery refers to discovery in legal proceedings such as litigation where the information sought is in electronic format. Quickbase supports key requirements of e-Discovery:<>

  • Preservation of Evidence - Upon legal hold being placed on customer data held within Quickbase apps, the customer may instruct personnel to preserve (not delete) apps and data. Additionally, the customer may choose to make copies of existing apps in order to preserve the data at that point in time. Lastly Quickbase maintains backup copies of customer apps and data. Customers may request apps to be restored via customer support.
  • Identification of Data - Quickbase provides the ability to search apps, however it is important to note that fields must be marked as searchable by the app owner. File attachments may also be searched; however they must be downloaded and searched locally.
  • Data Access - Customers own their data which they have uploaded and stored within Quickbase.


Quickbase abides by privacy laws and regulations that are applicable to our services. Quickbase personnel may have logical access to customer data stored in Quickbase apps only if they are authorized by the customer or have a need for access due to their job function.

Quickbase does not have visibility into or knowledge of what customers are uploading onto its platform, including whether or not that data is deemed subject to privacy regulations. Customers are responsible for their own privacy compliance for data they upload and store in Quickbase apps.

Quickbase’s Privacy Policy describes how Quickbase handles any personal information gathered from visitors to its website at and from users of the Quickbase service.

EU Data Protection Regulations

Quickbase is hosted in the United States and serves customers globally. There are several mechanisms to ensure that data transfers from the EU to the U.S. provide the legal protections required by EU Data Protection Regulations, namely the EU Model Contract clauses and end user consent. For customers that require it, Quickbase has a Data Processing Agreement (“DPA”) which includes the EU Model Contract clauses in order to capture the requirements of GDPR and provide for a valid mechanism of data transfer between the EU and the US.

A third mechanism was via Privacy Shield certification, a framework designed by the U.S. Department of Commerce and European Commission to provide companies on both sides of the Atlantic with a mechanism to comply with EU data protection requirements when transferring personal data from the European Union to the United States. On July 16, 2020, the European Court of Justice invalidated the Privacy Shield program as a valid transfer mechanism. The decision does not relieve participating organizations of their Privacy Shield obligations and the Department of Commerce will continue to administer the Privacy Shield program. Quickbase’s certification under the Privacy Shield program may be viewed at the Privacy Shield site.


On May 25, 2018, a new landmark privacy law called the General Data Protection Regulation (GDPR) took effect in the European Union (EU). The GDPR expands the privacy rights of EU individuals and places new obligations on service providers like Quickbase which store and process EU personal data.

Quickbase views GDPR as an opportunity to deepen our commitment to privacy and data protection best practices. Similar to existing legal requirements, compliance with the GDPR requires a partnership between Quickbase and our customers in their use of our platform. Quickbase complies with the GDPR in the delivery of our service to our customers and we are also dedicated to helping our customers comply with the GDPR. We have closely analyzed the requirements of the GDPR and have made enhancements to our products, contracts, and documentation to help support Quickbase’s and our customers’ compliance with the GDPR. In addition to ensuring our own compliance with the provision of GDPR, Quickbase's updated Data Processing Addendum, available upon request, contains additional provisions to assist customers with their compliance with the GDPR.


Quickbase utilizes subprocessors for the provisioning of our Services to you as described in our agreements on For a current list of our sub-processors please see


The California Consumer Privacy Act enhances privacy rights and consumer protection for residents of California by allowing California residents more control over how companies collect and use their personal information. The bill was passed by the California State Legislature and signed into law on June 28, 2018. The law goes into effect starting January 1, 2020. In providing the Quickbase platform, our customers are "businesses" and Quickbase is a "Service Provider" as described in the CCPA, which means that Quickbase retains, uses and/or discloses personal information only to provide the Quickbase platform and for other uses as permitted by the CCPA.

Export Controls

Prohibited Countries

Quickbase complies with U.S. regulations related to embargoed countries and regions. As such, Quickbase currently prohibits the unauthorized usage of its products and services in Cuba, Iran, North Korea, Sudan and Syria. Because this list of countries and regions may change from time to time, customers and their users are urged to consult the relevant regulations, including the U.S. Export Administration Regulations.

Denied Parties

Quickbase products and services may not be exported to, re-exported to, transferred to, or used by any restricted person or entity, including those listed on the U.S. Treasury Department's list of Specially Designated Nationals, the U.S. Department of Commerce Denied Person's List or Entity List, the State Department's Debarred list, or similar denied parties list without prior authorization by the U.S. Government.

For more information and for further assistance in determining your individual licensing requirements, contact the Department of Commerce, Bureau of Industry and Security ( or Office of Foreign Assets Control (

Prohibited End-Uses

Quickbase products and services may not be exported, re-exported, or transferred if for use directly or indirectly in any prohibited activity described in Part 744 of the U.S. Export Administration Regulations, including certain nuclear, chemical or biological weapons, rocket systems or unmanned air vehicle end-uses.

Accessibility/508 Compliance

To make the interface accessible to users with disabilities, Quickbase includes features that support several specifications in the Web Content Accessibility Guidelines (WCAG) 2.0.

The Voluntary Product Accessibility Template (VPAT) is a standardized form developed in partnership by the Information Technology Industry Council (ITI) and the U.S. General Services Administration (GSA) to document a product’s conformance with key regulations of Section 508 of the Rehabilitation Act. Quickbase has completed an accessibility assessment of the Quickbase platform and has documented their accessibility status using these VPATs. Quickbase's VPAT can be downloaded here.

Find a Security Issue?

Please visit our Responsible Disclosure page here.