Data Security in Quick3

Modified on Fri, 6 Nov at 10:12 AM

Introduction


When using a cloud-based data system like Quick3, you need to be sure that your data is safe and confidential. In this article, you can learn more about the procedures we follow at Quick Systems and how we think and work when it comes to data security.


At Quick Systems, we are mindful of the most important security principle of all: the weakest link is always sitting at the keyboard. We therefore regularly refresh all employees’ awareness of the assets and surfaces we consider vulnerable, and how to keep them safe. Of course, we recommend that your company does the same.


For an easy first step in this work, we recommend NorSIS’s guide to Digital security for small and medium-sized businesses.


Security isn’t something you have. Security is something you do.




Data protection


Your data is protected from unauthorized access in the following ways:


  • Continuous encryption of all stored data.
  • Encryption of all traffic between your browsers and our cloud services.
  • All our cloud services are provided by a world-leading provider.
  • All our internal resources are protected by access logs and MFA (multi-factor authentication).
  • Strong encryption of passwords you store in our systems. Where possible, these are “hashed” and “salted,” making them practically impossible to decrypt. Where passwords cannot be “hashed,” we use strong 256-bit symmetric encryption.
  • The number of access points to sensitive resources is kept to a minimum. As a general rule, users should be given the minimum level of access.




Data loss


How do we prevent data loss?


  • All data is backed up 4 times: three times in the same data center, and then one copy in a separate data center/location in case of an emergency. This gives us both local and global redundancy for all data. All backups are snapshotted so that data can be “rolled back” when needed.
  • All files in the file archive are versioned, so it is not possible to overwrite and lose data.
  • We conduct dry runs to practice restoring the cloud environment in response to different types of incidents and crises.




What you can do


How can you protect your data?


  • Avoid storing sensitive customer data in plain text. Use the Secrets tab on the customer card for this, or store it in an external system designed for that purpose.
  • Avoid sharing Quick3 users and passwords with multiple people.
  • Disable accounts for people who no longer work at your company so they can no longer log in.




Technical details


Quick3 Web App

  • Runs on a Virtual Machine (VM) in Azure.
  • Backups of the VM and all associated disks are managed through Azure Recovery Vault, with a daily schedule and 7-day retention. The backup is a PaaS solution, completely separate from other Azure services.
  • No services, either inside or outside Azure, have access to this backup.
  • The application server (VM) contains no customer data, configurations, keys, or secrets.
  • Configurations, keys, and secrets are stored in a separate PaaS solution in Azure (Azure Key Vault).


Databases

  • Runs on a separate PaaS solution (Azure PostgreSQL Flexible Server).
  • Zone redundancy with point-in-time recovery (PITR) across three separate data centers in Western Europe (the Netherlands).
  • Backups are managed by a separate Azure PaaS solution with 99.9999999999% durability from Microsoft.
  • Backups run daily and are retained for 14 days.
  • Access to backups is restricted to very few users through the Azure portal and secured with MFA. Even network access does not allow interaction with the backups, which means that any ransomware or crypto-lockers that might somehow get onto the network cannot compromise them.


Files

  • Files and documents are stored in Azure Storage Accounts (PaaS).
  • Geo-redundancy: Three copies are stored across different data centers in Western Europe (the Netherlands), with an additional backup in a data center in Northern Europe (Dublin).



These details were last updated on 2026-09-08.




Future improvements


We have concrete plans to improve security in Quick3:


  • Implement multi-factor authentication at login.
  • Create a centralized user registry that further isolates sensitive information from the rest of the system.



Do you have more questions? Contact Support.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article