Data & privacy

Activity statistics

The website records page views and download clicks using a random browser-tab session identifier. Newer desktop clients send a random, per-run online heartbeat. The statistics do not contain chat messages, files, model settings or credentials. For website visits and download clicks, the service records the connection IP and public page path without query parameters. For desktop online activity, it records the connection IP. These details are visible only to administrators. The website respects the browser Do Not Track setting.

Records older than 30 days are removed when new activity is recorded. Online figures estimate active sessions, not verified individuals or completed installations.

Local records

Chats, uploaded files and saved pages are stored in the local client workspace. Files in a selected project folder stay associated with that folder. Published applications also retain fixed versions of their selected configuration.

On Windows, local records and the backend runtime are stored under data in your chosen installation folder. Uninstalling preserves this folder. Back it up before moving or removing it.

Content sent to a model

Using a cloud model sends the provider your request and the content needed for the task. This can include chat text, selected file content, published knowledge or tool results, according to your configuration and the current task.

Connection scope and source relationships are saved locally. Queries read the records needed from the selected source. Raw rows from external databases are not bulk copied into local records. An application may retain grouping or filter values you approved, along with aggregate results and query receipts.

Model credentials

New model secrets can be saved in protected system storage or kept only in the current service process, according to the option you choose. Reading model settings returns configuration and credential status without echoing the stored secret. Secrets kept only in process memory need to be supplied again after that process ends.

Authorization and application scope

Authorization controls whether an action can run. It does not widen the data or tools selected for an application. A published application runs from its fixed version and selected scope. Disabling the application prevents new runs; its historical version can still be read.