Models and data flows

Local storage does not mean every operation stays on your device

The Tokeny desktop app can manage workspace files, conversations and settings locally. Online model requests may send the prompt, selected context, file excerpts or tool results needed for a task to the configured service. Account, payment, cloud and third-party tool features can also involve servers. The current privacy policy and enabled features define the applicable scope.

Three ways to connect a model

A local model does not automatically make a whole task offline. Browsing, web search, remote MCP servers, synchronization and downloads may still use the network. A stdio MCP connection describes communication with a local process; that process may itself make network requests.

Configure and verify

1. Select the provider or compatible protocol in model settings. Use its documented API address and model identifier.
2. Put the API key in the dedicated configuration field. Keep it out of chats, shared prompts and public screenshots.
3. Send a short request without sensitive information and inspect the response or error.
4. Test tool calls with a synthetic file. Chat capability alone does not establish reliable file-task execution.
5. Recheck destinations after changing a model or channel. Endpoints, tools and enabled features jointly determine the data boundary.

A concrete example

When an online model summarizes a local meeting file, it may receive extracted text or relevant excerpts. Keeping the original file on your computer does not prevent that transfer. With a local model, inference can run at the configured local endpoint, while web searches or remote tools still need a separate review.

Before using sensitive documents, test with redacted input and inspect the selected services, tools and output paths. An organization's administrator should confirm approved channels and tool boundaries.

Common errors and assumptions

A 401 response often indicates invalid credentials or a channel mismatch. A 404 can indicate the wrong endpoint, protocol or model identifier. A 429 can indicate quota or rate limits. Inspect the provider's error before repeatedly submitting private content to different services.

Reading locally saved history and generating an online model response are separate operations. Offline task completion requires the model, source material and all necessary tools to be available locally.

Official references: privacy policy, terms and model setup documentation. For workspace operations, see your first task.