- Introduction
- Product lifecycle
- Use of customer data in UiPath
- Use of customer data with Agents
- Use of customer data with AI Center
- Use of customer data with AI Computer Vision
- Use of customer data with Apps
- Use of customer data with Assistant
- Use of customer data with Automation Ops
- Use of customer data with Automation Hub
- Use of customer data with Autopilot for Everyone
- Use of customer data with cloud robots
- Use of customer data with Context Grounding
- Use of customer data with Data Service
- Use of customer data with Document Understanding™
- Use of customer data with Healing Agent
- Use of customer data with Insights
- Use of customer data with Integration Service
- Use of customer data with IT Automation
- Use of customer data with IXP
- Use of customer data with Orchestrator
- Use of customer data with Process Mining
- Use of customer data with Robot
- Use of customer data with Studio and StudioX
- Use of customer data with Studio Web
- Use of customer data with Test Manager
- Licensing
- Delivery options
- UiPath Platform
- UiPath documentation
- Troubleshooting

Overview
We process the information used with our services for the following purposes:
-
Provide our services
Provide our services
We use documents and data, stored or accessed via API or Data Service etc., provided in designtime, and/or runtime to deliver our services, such as designing and running the app, and showing data to users in runtime etc.. Apps enables customers to build custom business applications, as further described in the Apps documentation.
We process telemetry data, such as usage data, errors, peak loads etc., to make sure that our platforms operate smoothly, and to optimize the user experience based on the feedback and usage patterns we observe. We use data analytics to measure and evaluate the performance of our services.
We process account information such as username, password, email etc., in order to provide you with access to the services, and to secure your account.
We may process data that you send to us for support, or as necessary for troubleshooting issues, in accordance with our Support terms.
Apps does not store any data directly, but customers may need persistent storage for Apps, and hence, may indirectly store the same via additional Orchestrator Storage Buckets and Data Service Entities when using this product, as selected by you and in accordance with our Data residency page.
Apps, as a platform component, only has session-level data, and it does not store any customer data unless the user configures the information to another activity during the session.
Customers may, at designtime, pass on the data the user enters while using Apps to their system of records/system of engagement via Integration Service as activities, or as Entities, or may also access the same data, and vice versa.
Apps may interact with generative AI activities from other platform components, via Studio activities. Apps can invoke these activities via Events, and the user can configure the inputs it passes to these activities, or the outputs it receives from the activities displayed to users at runtime. For these activities, please check how the data is used with these activities. To disable the use of AI features through the AI trust layer policy, Please check Settings for AI Trust Layer Policies to disable the use of AI features through the AI Trust Layer policy.