Sutherland Robility adopts a “privacy-first” approach to the protection of customers’ data and infrastructure. There are three types of data processed in Robility.
Operational Data: This includes status and log information that aids in running the automations such as error logs, audit logs, device connectivity stats, and operational dashboards.
Business Data: This data is used in operating a business and that is being passed between systems as part of bot automation such as customers’ client data, invoice numbers, or images of PoS. For instance, data uploaded to the cloud can be used to process documents.
Personal Data: This is any data that could be used to identify an individual and is governed by laws such as GDPR and the CCPA. Examples of such personal information include, but are not limited to, individual names, telephone numbers, email addresses, job titles, and contact information contained in invoices or emails.
Data Collection
In the deployment model of Robility, customers take charge of building and managing their bots using the cloud-based Control Room. Here's a concise and stylish version:
Customers are empowered to unleash their automation potential with Robility's deployment model. They design and develop their bots, leveraging the intuitive Robility platform. The bots are rigorously tested to ensure their accuracy and reliability.
Once ready, the bots are deployed to execute tasks on the users' computer infrastructure. The Control Room, hosted in the cloud, becomes the nerve center of bot management. From here, customers gain centralized control, monitoring, and scheduling capabilities.
This crisp and sophisticated model puts customers in control of their automation journey, offering flexibility, customization, and seamless integration with their existing systems.
Telemetry
The Robility Automation Command Centre plays a crucial role in monitoring and supporting the operational performance of the deployment system. This includes activities such as system scaling, service maintenance, and adherence to the SLA specified in the service agreement between Sutherland and the customer.
It's important to emphasize that Sutherland Robility respects the privacy and security of customer data. The support personnel of Sutherland Robility do not have inherent visibility into the customer's data unless permission is granted expressly. Access to customer data is strictly controlled and limited to instances where it is necessary for troubleshooting and resolving technical product issues.
To enhance the product and provide valuable insights, Sutherland Robility analyzes feature usage data. This involves implementing telemetry mechanisms that capture operational information about feature usage. By analyzing this data, Sutherland Robility gains valuable insights into how customers interact with the product. This information is then utilized to prioritize enhancements and improvements to the product. For example, it helps to identify frequently used application commands, and enables the team to prioritize their inclusion in future releases.
Additionally, it facilitates the generation of operational best practices recommendations and enables support services to update, secure, and troubleshoot the product effectively. Moreover, personalized product experiences and tailored recommendations can be offered based on usage patterns and preferences.
Through the analysis of feature usage data and the implementation of telemetry, Sutherland Robility strives to continuously enhance the product's functionality, performance, and user experience, while ensuring the utmost privacy and security of customer data.
Data Retention After Subscription Termination
Understandably, data retention is an important aspect of the Robility platform. Sutherland Robility follows a data retention policy to ensure the appropriate handling of customer data, configurations, and logs. Here are the specifics.
Customer Data and Configurations: Sutherland Robility retains customer data and configurations for a period of 30 days after the expiry of the customer's subscription. This ensures that data and configurations are accessible if the customer needs to retrieve or transfer them within a reasonable timeframe.
Logs: Most logs generated by the Robility platform are retained for 30 days after the expiry of the customer's subscription. These include logs related to system activities, bot executions, and platform operations. Retaining these logs enables historical analysis and troubleshooting if necessary.
Extended Log Retention: However, certain logs may be kept for an extended duration of up to 180 days after the expiry of the customer's subscription. These logs may contain critical information or provide valuable insights for auditing, compliance, or forensic purposes. The retention of these logs beyond the standard 30-day period allows for a longer window of access if needed.
By following this data retention policy, Sutherland Robility ensures that customer data, configurations, and logs are appropriately maintained and accessible within specified timeframes. This helps facilitate data management, compliance, and potential future requirements.