Data Safety

Last update: 19.02.2024
Deskie has several ways to secure an account from unauthorized use:

  • adding agents in bulk from a CSV file with "complex" passwords. Read more

  • restriction account access only to specific IP addresses. Read more

  • setting up two-factor authentication for administrators and agents. Read more

Data privacy in Deskie

We don't shift the entire responsibility for security onto users. Data privacy in Deskie is also ensured by our team.

1. Basic privacy principles are set out in the Terms of Service and Privacy Policy sections of our website:

  • we use customer information solely to ensure the high-quality delivery of services and for record-keeping purposes;

  • we do not disclose the data of one customer to another within the service;

  • we never publish information publicly or share it with third parties.

2. We have a DevOps team that constantly monitors the service performance and potential threats. Upon identifying issues, they immediately make the necessary corrections or notify developers if the solution requires their involvement.

All of Deskie’s application and data infrastructure is hosted on Hetzner’s dedicated servers. The server architecture runs on Kubernetes to provide fault tolerance and the fastest scaling.

Access to our production infrastructure is restricted to DevOps only.

3. All data transmitted within the web application is done through an encrypted connection (TLS 1.2), ensuring that the data cannot be viewed by a third party.

The SSL certificate is issued, even when you connect your domain; it is utilized for both administrator and agent accounts, as well as for the help center. More details on SSL certificate issuance.

The mobile applications also operate through an encrypted connection (SSL Pinning) to eliminate the possibility of "Man-in-the-middle" attacks.
Additionally, we support a number of security focused features to help keep your data safe:

  • all sensitive customer data is encrypted at rest including: user passwords, email addresses passwords and etc;

  • creating different API keys with the option for quick disconnection;

  • TLS encryption on all inbound and outbound email;

  • automatic logout of an agent after a certain number of hours of inactivity

Was this article helpful?