We take security very seriously here at ReQtest. Here’s a breakdown of our security policy;

Data security

Encrypted traffic

All traffic between the customer’s web browser and ReQtest’s servers is encrypted with SSL, using a digital certificate issued by GlobalSign. You can inspect the certificate in your web browser. (The exact procedure varies between different browsers.)

Database access

The database is stored on our servers, which are located in the data center of our service provider Ipeer. Data is never transferred from our servers to any other place, except for backups (see below).

The database is password-protected. Only the developer team at ReQtest has access to the database password.

ReQtest’s servers are protected by a firewall. The servers, files and database can only be accessed from IP addresses that belong to ReQtest. All data traffic between ReQtest’s office and the data center is encrypted.

Backup and restoration of data

The database and the files are backed up once per day. The backup is stored offsite, physically separate from the data center.

In addition to the backup, the customer’s data is protected against inadvertent access, in that data in ReQtest is generally not deleted but only marked as deleted, like the trash can in Windows. A deleted project or item (requirement, test case, bug report) can be restored by ReQtest support staff without restoring the entire database.

Password management

Users’ passwords are encrypted for storage in the database. The encryption is done by hashing, i.e. one-way, non-reversible encryption – the password cannot be decrypted. ReQtest employees have no way of viewing a user’s password.

At login, the number of login attempts is limited. After five failed login attempts with invalid passwords, the user account is locked. This protects against brute force attacks.

A user can reset their password with the help of a single-use link, which is sent to the email address that the user registered with.

Security routines

ReQtest employees never share customer or user account information, or customer data, with anybody outside the company.

We never edit the status or role of user accounts on a user’s request.

Secure code

All features in ReQtest are reviewed with regards to security aspects, and tested specifically for SQL injection, XSS attacks and request parameter hacking.

Hardware

ReQtest’s servers are physically managed by our service provider Ipeer. The infrastructure in the data center includes 24-hour monitoring, redundant internet connections, UPS, and redundant backup generators.

The servers themselves have built-in redundancy and automatic failover. In case of a server error, the service is automatically moved to a new server with no downtime.

Security updates

All software on the servers, including virus protection and firewall, is regularly updated with the most recent security updates.

Feel free to browse and read our full Terms of Services.

We bill on a monthly basis to the billing address or email address you specify in the invoice settings within ReQtest.

You can also download the invoicing data for all past invoices from the invoice settings page. This is an Excel file that lists all users that were included in the invoice for a given month, as well as which projects they were members of.

You can manage your license costs by enabling and disabling user accounts. Since we only charge you for enabled user accounts you won’t need to pay for more than what your company needs. This is makes ReQtest advantageous when compared to other testing software. In many other tools you have to buy licenses for the maximum number of users that you are going to have.