Security
Know what Elyntic reads, sends, and can do.
You choose the sources, models, tools, and rules behind every action. Elyntic makes it clear what stays on your device, what is sent to a service, and what happens automatically, requires your approval, or stops for you to decide.
- 01 / Connected SourceNorth star email + selected historyGmail keeps its copy
- 02 / On-device workspaceTask, context, and working draftStored locally in your Elyntic workspace
- 03 / Optional chosen model and toolsUses only the context the task needsYour provider terms apply
- 04 / Checked Result ReturnsClient response ready outputsRequires your approval before sending
- 05 / Kanban task managerProject boardStored in external server
*Local-first does not mean no data ever leaves your devices
What data can Elyntic use?
Only what you choose to connect. Each channel has its own capabilities, so you can see exactly what Elyntic can access.
Gmail provides the most complete communication path today. Other connections add context and actions according to what you configure.
| 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, Apple Messages (iMessage) can add history and triage. |
SMS | Configured connections | SMS support depends on the active provider setup. |
 Outlook / IMAP | Basic email connection | Retrieval and drafting exist without Gmail-level historical processing. Sending follows the configured rule for that connection and workflow. |
 Teams | Configured connections | Teams integration adds organizational context according to your enterprise configuration and permissions. |
Where the data goes
Core workspace records—tasks, saved results, and review state—stay on your device. When a task uses a connected source, AI provider, or tool of your choosing, only the data needed for that task is shared with that service.
On your device
Core task, saved-result, and review-state records stay in your desktop workspace.
Connected sources
Gmail, Slack, and other connected services retain data according to their own policies and your account settings.
AI models and tools
The provider you choose receives the data needed to perform the task. Their handling and retention policies apply to the data they receive.
Model training
Elyntic does not use your workspace to train its own foundation model. Training and retention policies for any AI provider you connect still apply.
Set the limits. Choose what runs—and what asks first.
Permissions, tools, budgets, and per-action rules define the working area. A trusted workflow can deliver automatically after its checks; exceptions and consequential spending can still require confirmation.
This client follow-up asks before sending. Other trusted workflows can deliver automatically within the rule you set. Available controls vary by connection and workflow.
- 01
Runs automatically
Work and delivery can continue inside the allowed task, tool, budget, and action rules.
- 02
Asks first
Actions marked Confirm—such as this client reply—pause for a person before they continue.
- 03
Stops
Missing permission, a hard budget limit, or a failed path can stop the work.