Data Protection at Runtime - Data Protection at Runtime - Hyland RPA - Security - Hyland RPA - Hyland-RPA/Security/Foundation-25.1/Hyland-RPA-General-Information-and-Security/Security/Data-Security/Data-Protection-at-Runtime - Foundation 25.1 - Foundation 25.1

Hyland RPA General Information and Security

Platform
Hyland RPA
Product
Security
Hyland RPA
Release
Foundation 25.1
License
ft:lastPublication
2025-04-03T07:42:42.326000
ft:locale
en-US

The bots can process orders, transfer files and move data from one system to another. Most importantly, the bot does not store any data in the Heart database.

The bots only transfer data at runtime, so data is only cached in internal memory. This ensures that your data is secure throughout the entire process.

When building a bot, avoid logging personal information or storing it in a task as input or output data. Instead, use technical identifiers like the ones those listed below.

  • With Mail => Unique Mailid
  • For ticket systems => ticketid
  • For customer queries => customernumber

If you need to enter personal information, ensure to use Hyland encryption.

Other features and configuration options can be used to prevent unauthorized data access or tampering, including:

  • Time limit: Set a time limit after which an automation will be terminated if it is not completed.
  • Central control: The ability to centrally control (pause, resume, stop) the operation of remotely running automations within Hyland RPA Manager.