Elyan Intelligence Disclosure
This disclosure explains how intelligence-assisted features in Elyan work, how context is processed for tasks, and where user control applies.
1. Separation of roles
The mobile app and web surface are task-control layers. When you start a task, Elyan moves it through the secure control plane to the appropriate execution path; private local actions remain within the desktop runtime boundary.
2. Context that may be processed
Prompts, task content, conversation continuity, summaries of attachments, and permitted device context may be processed to generate a response. Where possible, Elyan uses limited, scored, privacy-controlled context packages instead of raw data.
3. Local workspace
Elyan Desktop keeps a local-first boundary for private files, local applications, and on-device capabilities. Private local files are not automatically moved to the cloud without user approval or explicit task context.
4. Training and personal content
Elyan is developed as one product identity through its own intelligence layer. Personal commands, private conversations, and local files are not used for model development without explicit consent.
5. Errors and user control
Elyan may produce incomplete, outdated, or incorrect outputs. The user is responsible for final review when code, documents, health, finance, law, security, or device actions are involved. Elyan does not provide medical diagnosis, legal advice, or financial investment advice.
6. Safe automation boundary
File writes, browser control, device actions, connector operations, and tasks that can create side effects in external systems are limited by permission, safety policies, and task traces. Elyan is not designed to perform hidden or user-unaware background actions.