elyntic
Request a 14-day trial
Menu

Security and control

Know what Elyntic reads, sends, and can do.

You choose the sources, models, tools, and rule for each action. Elyntic shows what stays on your device, what reaches a service, and what runs, asks first, or stops.

Request a 14-day trialSee how it works
Client follow-up / data pathAsk before send
  1. 01 / Connected sourceNorthstar email + selected historyGmail keeps its copy
  2. 02 / On-device workspaceTask, context, and working draftStored in your Elyntic workspace
  3. 03 / Chosen model and toolsOnly the context the task needsYour provider terms apply
  4. 04 / Checked result returnsClient response readyAsk before send

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 provides the most complete communication path today. Other connections add context and actions according to what you configure.

Current communication channel support
ChannelCurrent stateWhat that means
GmailFirst working pathSelected sent and received history can be stored. Eligible high-priority messages can become agent work.
SlackContext and on-demand triageConfigured messages and mentions can add context. Continuous Slack-to-task routing is not yet claimed.
iMessageConfigured MacsOn supported Macs with the required permissions, iMessage can add history and triage.
SMSConfigured connectionsSMS support depends on the active provider setup.
Outlook / IMAPBasic email connectionRetrieval and drafting exist without Gmail-level historical processing. Sending follows the configured rule for that connection and workflow.

2 / Where can the data go?

Core workspace records stay on your device. Connected services receive what the task needs.

Task, saved-result, and review-state records are stored on your device. Connected sources, AI providers, and tools keep the data they receive under their own policies.

  1. 01

    On your device

    Core task, saved-result, and review-state records stay in the desktop workspace.

  2. 02

    Connected sources

    Gmail, Slack, and other services keep their own copy under your account policy.

  3. 03

    AI models and tools

    The provider you choose receives the data needed to perform the task.

  4. 04

    Model training

    Elyntic is not training its own foundation model on your workspace. Your chosen provider's retention and training terms still apply.

  5. 05

    Early-access request

    The website keeps the work email you submit so Elyntic can manage access and contact you. It is separate from your workspace and is not used to train AI.

3 / What may the AI do?

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.

Example / client follow-upActive
Read connected contextOffConfirmAll
Create and update workOffConfirmAll
Send an external replyOffConfirmAll
Spend outside the task budgetOffConfirmAll
Approval queueReply to Northstar Studio
1 waiting

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.

  1. 01

    Runs automatically

    Work and delivery can continue inside the allowed task, tool, budget, and action rules.

  2. 02

    Asks first

    Actions marked Confirm—such as this client reply—pause for a person before they continue.

  3. 03

    Stops

    Missing permission, a hard budget limit, or a failed path can stop the work.

4 / How do export and deletion work?

Your workspace and each connected service keep their own copy.

Deleting one copy does not automatically remove the others.

On-device workspace records
Core task, saved-result, and review-state records stay on your device. Export and deletion options can differ by record type.
Early-access requests
The website keeps the submitted work email in its private waitlist so Elyntic can manage access and contact you. Ask for removal through the Elyntic communication you receive.
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

Connect the sources, define the work, and set clear limits.

Request security detailsSee how Elyntic works