Security and control
Know what Elyntic reads, sends, and can do.
You choose the sources, models, and tools. Elyntic shows what stays on your device and what must go to a connected service.
- Reads
- Sources and history you connect
- Stores
- Workspace history, tasks, results, and decisions
- Calls
- Models and tools you configure
- Returns
- Work, exceptions, and actions for review
Local-first does not mean no data ever leaves the device.
1 / What data can Elyntic use?
Only the connections you set up, with different maturity by channel.
Gmail is the first complete communication path. Other channels have useful pieces, not full parity.
| Channel | Current state | What that means |
|---|---|---|
| Gmail | First working path | Selected sent and received history can be stored. Eligible high-priority messages can become agent work. |
| Slack | Context and on-demand triage | Configured messages and mentions can add context. Continuous Slack-to-task routing is not yet claimed. |
| iMessage | Configured Macs | On supported Macs with the required permissions, iMessage can add history and triage. |
| SMS | Configured connections | SMS support depends on the active provider setup. |
| Outlook / IMAP | Basic email connection | Retrieval and sending exist without Gmail-level historical processing. |
2 / Where can the data go?
Workspace records stay local. Connected services still receive what the task needs.
The exact route depends on the source, model, and tool you enable.
- 01
On your device
Workspace records such as tasks, results, and decisions are kept in the desktop app's local database.
- 02
Connected sources
Gmail, Slack, and other services keep their own copy under your account policy.
- 03
AI models and tools
The provider you choose receives the data needed to perform the task.
- 04
Model training
Elyntic is not training its own foundation model on your workspace. Your chosen provider's retention and training terms still apply.
3 / What may the AI do?
Set the limits. Review before it sends or spends.
Permissions, tools, and budgets set the working area. Approval rules can hold selected actions, but they do not yet guard every tool path in the product.
Available controls depend on the active release and configured path.
- 01
Runs
Work inside the allowed task, tool, and budget limits.
- 02
Asks first
A configured important action, such as an external reply, can pause for a person.
- 03
Stops
Missing permission, a hard budget limit, or a failed path can stop the work.
4 / How do export and deletion work?
Your device and each connected service keep their own copy.
There is not yet one delete button that covers every local record and provider.
- Elyntic records
- Stored in the desktop app's local database. Export and deletion controls vary by release.
- Connected sources
- Messages kept by Gmail, Slack, or another provider remain subject to that provider and your account policy.
- Models and tools
- Configured services apply their own processing and retention terms.
- Before access
- Request the current architecture, storage locations, and known limits for your setup.
Inspect before you connect