Data protection,
security and
compliance

Trust is our foundation

Data protection is our top priority

When it comes to the security of your data, we make no compromises

High safety standards

Our virtual employees process a large number of documents and data every day. Therefore, it goes without saying that the responsible handling of sensitive information is our top priority. We attach great importance to the protection of personal and company-related data and work closely with certified data protectionists, lawyers and IT security experts with many years of experience. To ensure that your data is always safe and secure, we also provide various protection mechanisms.

ISO certified data centre

Certifications, training, audits and reviews are all part of our commitment to excellence and continuous quality improvement. Our software solutions are hosted in an ISO 27001 certified data centre. We are also ISO 9001 certified. These standards enable us to demonstrate the effectiveness of our information security management system and ensure data subjects’ rights through concrete technical and organisational measures and data protection impact assessments.

0 %
Data protection
0 %
Security
0 %
Compliance

Sustainable sensitisation of our employees

Promote safety awareness

In order to raise our employees’ awareness of information security and data protection, regular training sessions are held on various topics. On the very first day, all new colleagues receive a training on security, data protection and compliance, which is also refreshed several times a year. Furthermore, we contribute our expertise in many ways to professional networks such as the Berufsverband der Datenschutzbeauftragen Deutschlands e.V. (BvD) or the Gesellschaft für Datenschutz & Datensicherheit e.V. (GDD).

Secure setup of the infrastructure

Your data is secure with us

The auto.mates software consists of three different components: the orchestrator, which controls the robots, the studio, in which the robot is modelled, and the robot itself. To enable process automation with a virtual employee, all three components (orchestrator, studio and robot) must be integrated into the infrastructure. The system landscape can be set up individually according to your needs. Basically, we distinguish between three different options for setting up the infrastructure:
  • auto.mates x customer
    The Studio and the robot are installed on a Windows machine that is provided in your company's network. Via Remote Desktop Protocol (RDP), TeamViewer or Teams, our developers can then model the robot in the Studio. After the successful development of the robot, the Studio is uninstalled again, and the corresponding connections are also disconnected. The robot is controlled via the Orchestrator, which is installed in our ISO-certified data centre. For the Orchestrator to communicate with the robot, the computer needs a connection of TCP port 443. This infrastructure is particularly suitable for our Robotics as a Service implementation model, where we take over the operation, development as well as the control of the process.
  • auto.mates
    All components (Studio, Robot and Orchestrator) are installed on a virtual machine in our Tier 3 level ISO 27001 certified data centre. This means that no port or access to your company's network is required. If there are applications in the process to be automated that are not web-based, these must also be installed on the virtual machine so that the robot can execute the process without any problems. In order for you to receive the data or results of the process, the software robot makes them available, for example, via an SFTP server or by e-mail.
  • Customer
    All components (Studio, Robot and Orchestrator) are installed on a Windows machine that is provided in your company's network. The orchestrator also needs access to a database in which relevant information (such as start and end times of the robots or error logs of the robots) can be stored and retrieved. This type of infrastructure is particularly suitable if you are planning to set up your own centre of excellence and only want to draw on our process and development expertise. If direct support is needed from our side, we can then establish an RDP connection, for example.

    auto.mates x customer

    The Studio and the robot are installed on a Windows machine that is provided in your company’s network. Via Remote Desktop Protocol (RDP), TeamViewer or Teams, our developers can then model the robot in the Studio. After the successful development of the robot, the Studio is uninstalled again, and the corresponding connections are also disconnected. The robot is controlled via the Orchestrator, which is installed in our ISO-certified data centre. For the Orchestrator to communicate with the robot, the computer needs a connection of TCP port 443. This infrastructure is particularly suitable for our Robotics as a Service implementation model, where we take over the operation, development as well as the control of the process.

    auto.mates

    All components (Studio, Robot and Orchestrator) are installed on a virtual machine in our Tier 3 level ISO 27001 certified data centre. This means that no port or access to your company’s network is required. If there are applications in the process to be automated that are not web-based, these must also be installed on the virtual machine so that the robot can execute the process without any problems. In order for you to receive the data or results of the process, the software robot makes them available, for example, via an SFTP server or by e-mail.

    Customer

    All components (Studio, Robot and Orchestrator) are installed on a Windows machine that is provided in your company’s network. The orchestrator also needs access to a database in which relevant information (such as start and end times of the robots or error logs of the robots) can be stored and retrieved. This type of infrastructure is particularly suitable if you are planning to set up your own centre of excellence and only want to draw on our process and development expertise. If direct support is needed from our side, we can then establish an RDP connection, for example.