- Getting started
- Capabilities
- Data privacy and governance
- Data privacy
- Architecture and data flow
- Product availability
- Earlier Autopilot capability sets
- User scenarios
- Prompting guide
- Example prompts
- Autopilot usage pool for testing
- Best practices and limitations
- Supported models and limits
- Quality-check requirements
- Generate tests for requirement
- Import manual test cases
- Find obsolete tests
- Generate tests for SAP transactions
- Generate synthetic test data
- Generate test reports
- Generate coded test cases
- Search Test Manager project
- Troubleshooting
- Troubleshooting
- Autopilot for Everyone
- About Autopilot for Everyone
- Licensing
- User types
- Data sources
- Toolset automations
- Localization
- Prerequisites
- Autopilot widget
- The Autopilot for Everyone tenant card
- Prerequisites for installation
- Enabling Anthropic models
- Installing Autopilot for Everyone
- Updating Autopilot for Everyone
- Uninstalling Autopilot for Everyone
- Configuring Autopilot for Everyone
- Disabling the Autopilot welcome screen in Assistant
- Configuring an LLM for Autopilot for Everyone
- Deploying toolset automations
- Prompt-to-response flow
- Launching Autopilot for Everyone
- Autopilot settings for business users
- Using a specialized Autopilot
- Using a starting prompt
- Uploading and analyzing files
- Running automations
- Interacting with Autopilot answers
- Using suggested prompts
- Starting a new chat
- Chat history
- Providing general feedback
- Clipboard AI Enterprise version
- Designing relevant automations for Autopilot for Everyone
- Troubleshooting
Data privacy
UiPath Autopilot data privacy practices and compliance with global data protection standards.
UiPath values data privacy and aims towards protecting all users' right to privacy when sharing data while using the UiPath Autopilot functionality.
UiPath Autopilot ensures the security and privacy of data through a comprehensive approach that includes compliance with global data protection regulations like GDPR, ensuring legal standards in data handling are met. The platform employs data encryption for both data in transit and at rest, safeguarding against unauthorized access. Additionally, robust access control mechanisms, such as role-based access control (RBAC), restrict system and data access to authorized users only, enhancing data security.
The platform also adheres to secure development practices, which minimizes the risk of software vulnerabilities. Regular security audits and updates help in keeping the platform resilient against emerging threats. Furthermore, strong user authentication and authorization processes are in place to prevent unauthorized system access. In the event of a security breach, UiPath Autopilot is equipped with an incident response plan to effectively mitigate potential impacts on data security and privacy.
Processed data
We process requests containing information relating to your user query and the context in which the query is made. The context might involve workflow definitions, available User Interface (UI) objects, and any possible activities or code definitions based on your interactions with this functionality.
For the data that Autopilot sends with each request, what UiPath stores and logs, and the controls available to admins, refer to Architecture and data flow.
Processing operations
The primary objective of our data processing is to ground our model in the context of your unique user experience. This approach helps us better understand your particular needs and enables us to build output that matches your expectations in a given context.
Data centers
UiPath hosts data in several data centers, geographically distributed to accommodate your organization tenant region:
- North America: For users within the United States and Canada, data processing is managed in UiPath data centers located in North America.
- Europe: For users in European countries, including in the United Kingdom, data processing is managed in UiPath data centers located in Europe.
- Japan: For users in Japan and other Asia, Pacific, and Japan (APJ) regions not specifically mentioned, data processing is managed in UiPath data centers located in Japan.
UiPath retains telemetry data and Autopilot chat history in the mentioned data centers.
Model providers and routing
Autopilot uses models from several third-party providers, through the UiPath LLM Gateway. Each model is hosted in specific regions. When a model isn't available in the region of your organization or tenant, requests are routed to a region where it is, while data residency is maintained. For the providers, hosting regions, and routing of each Autopilot feature, refer to AI features and model routing.
Autopilot for Everyone chat data
To learn how Autopilot for Everyone handles data received through chat interaction, refer to Chat history storage management.
References
UiPath Data Residency policy is the place where you can find all regions where UiPath Automation Cloud™ and our cloud services can be hosted, depending on your licensing plan and region preference.
The UiPath Privacy Principles for Sub-processors set out the general rules for processing of personal data in accordance with UiPath's instructions, transfers and security of personal data, as well as for cooperation between UiPath and sub-processors.
Security is very important to us. UiPath Security information is available for you to check at any time.
For more information about how UiPath handles and processes personal data, refer to the Privacy Policy.