Elyan Intelligence Disclosure
This disclosure explains how Elyan intelligence features work, how your data is processed in task context, and where user control remains in place.
1. Role distribution
The mobile app and web surface are task control layers. When you start a task, Elyan routes the request through the secure control-plane to the appropriate execution path; private local actions stay inside the desktop runtime boundary.
2. Context processed by Elyan
Prompts, task contents, conversation continuity, attachment summaries, and permitted device context may be processed to generate responses. Where possible, Elyan uses limited, scored, privacy-controlled context packets instead of raw data.
3. Local execution workspace
Elyan Desktop protects a local-first boundary for private files, local apps, and device-side capabilities. Private local files are not automatically moved to the cloud without user approval or an explicit task context.
4. Training and personal content
Elyan is developed as a single product identity with its own intelligence layer. Your personal prompts, private conversations, or local files are not used for model development without explicit consent.
5. Error margin and user control
Elyan may produce incomplete, outdated, or incorrect output. The user is responsible for final review of critical code, documents, health, finance, legal, safety, or device-action outcomes. Elyan does not provide medical diagnosis, legal advice, or financial investment advice.
6. Safe automation boundary
File writes, browser control, device actions, connector operations, or tasks that may affect external systems are limited by permission checks, safety policy, and task traces. Elyan is not designed to run hidden background actions without user awareness.