Aleria's deployment and data handling depend on the environment your organization uses. Your administrator can confirm the hosting arrangement, enabled models, external connections, and policies that apply to your account.
Understand the boundaries
Distinguish where Aleria runs from where a connected service runs. Enabling an external connector can allow requests to that service under the authorized account. Do not assume every deployment is offline or that using a plugin keeps all activity within one network boundary.
An isolated environment may have a different set of models and capabilities from an internet-connected deployment.
Control access to work
Review project members and the sharing controls on chats, Sources, agents, skills, and apps. Use the intended audience for each item. Automation output can contain data retrieved from connected systems, so review its audience as well as its input account.
Ask for the applicable policy
For requirements about retention, backups, data residency, model providers, or use of data for training, obtain the current policy or contractual documentation for your organization's deployment. A general help article cannot substitute for those deployment-specific commitments.
Report a concern
If you believe someone has inappropriate access, record the item and the access you observed, reduce the relevant sharing where you can, and contact your administrator or support. Avoid sending credentials or sensitive source files in an initial support message.
See sharing and access and account security.