Last updated date: March 2025.
At Leapwork, we are committed to continuously improving our platform to ensure it delivers the most value to our customers. To achieve this, we track non-personal, non-sensitive usage data to help us understand which functionalities are truly driving adoption, which areas may require enhancements, and where we can proactively resolve potential issues before they are reported. This data is strictly limited to aggregated insights and does not include any personal data or sensitive company data.
Scope of non-personal data collection
What data we don’t track
Leapwork’s data tracking is solely focused to on ensuring that the functionality it builds is being used and works effectively. We do not track:
- Personally identifiable information (PII): We do not know which individuals use specific features.
- Sensitive company data: We do not monitor what test cases customers write, whether tests pass or fail, or the stability of customer systems.
- User behavior at an individual level: We do not collect data on which individual user interacted with specific features, building blocks or created specific test flows.
Instead, we gather aggregated, anonymized usage data to ensure privacy and compliance with applicable data protection standards.
What data we do track
We collect anonymized and aggregated usage data to track feature adoption and system performance such as:
- Automation components
- Building blocks: Frequency of use, execution duration, overall failures (without tracking failure reasons).
- AI / Cloud Blocks: Included in the above tracking.
- Subflow Blocks: Counted toward total usage and execution statistics.
- Building blocks: Frequency of use, execution duration, overall failures (without tracking failure reasons).
- Recording & detection
- Recorders: Frequency of use, execution duration, and failures (if any).
- Subcomponents of recorders: Tracked based on element detection.
- Multiple recorders: If multiple are used in a session, all are counted.
- Recorders: Frequency of use, execution duration, and failures (if any).
- Run lists & schedules
- Run list creation: Count of new run lists created, and count of total run lists maintained.
- Schedules: Count of number of schedules created and executed per day.
- Totals
- Total number of flows built
- Number of new flows created per day
- Number of flows executed per day
- Total execution time per day
- Net change of created/deleted flows per day
- Team & access tracking
- Teams: Number of teams created.
- Logins: Count of unique users logging in and total logins per day.
Why we collect non-personal usage data
By analysing usage trends, Leapwork aims to:
- Enhance the most valuable and frequently used features.
- Proactively detect and resolve platform issues proactively before they impact customer workflows.
- Optimize performance to ensure Leapwork runs smoothly and efficiently.
Customer control over Data Sharing
Leapwork recognizes the importance of data privacy and is committed to handling all collected data with the utmost care. All transmitted data is securely encrypted and does not contain any personally identifiable information (PII) or sensitive company data. By allowing Leapwork to collect anonymized usage data, customers benefit from a continuously optimized product experience, with proactive improvements in reliability, efficiency, and overall performance.
Customers who prefer not to share usage data can opt out of participation by contacting their Customer Success Manager (CSM) or Leapwork Support. For any questions regarding how usage data contributes to product enhancement, please reach out— we are happy to discuss how we balance privacy and continuous improvement.