Help & reference
Privacy and data handling
Understand how your selected models, tools, and account affect where information goes.
On this page
Model context
When you ask a cloud model to work on a project, relevant prompts, attachments, and tool results can become part of the request sent to that provider. Review what you include and the provider’s data policies before using confidential material.
Using a local model changes where inference runs, but it does not make every connected plugin or external tool local. Consider each connection separately.
Connected tools
A plugin can read or change information in another service within its granted access. Check the service, account, permissions, and requested action before approving. Revoke access in that service when you no longer want it to remain authorized.
Account and usage information
Virillio’s privacy notice explains its account, device, provider, usage, and payment-related information handling. Refer to that notice for the current policy rather than treating this guide as a separate legal promise.
Usage estimates and activity summaries are distinct from the content of your project. Their presence does not establish that every request has been reported or that a provider has charged the displayed amount.
Keep examples and support requests clean
Use a demonstration project when sharing screenshots. Remove credentials, private URLs, customer records, and proprietary code from logs or reproduction steps. If you accidentally expose a provider key, revoke it at the provider and replace the connection.
For account access, correction, or deletion questions, contact support.