Data flow and privacy
Understand what stays with your connector and what each feature shares.
The database connector is the component that connects to your database. The control plane manages accounts, permissions, configuration, approvals, and audit services.
| Flow | Data involved |
|---|---|
| Connector to browser | Records and fields the signed-in user may read. |
| Connector to MCP client | Records the connecting user may read; the client may send them to its model provider. |
| Connector to control plane | Schema names and types, configuration exchanges, health and backlog metadata. |
| Connector to audit ingestion | Actor and operation metadata, identifiers, and field changes according to redaction settings. |
| Connector to SDK plugin | The requested operation and its context, at your configured plugin URL. |
| Record notes | Note text is stored in the control plane. It checks record access with a fresh connector session and discards the returned record body. |
Optional AI features
Ask your data sends your question and schema to the configured language-model provider to produce a query. It does not need to send record values for query generation, but any values you include in the question are part of the prompt.
Decision fields send their selected input fields for evaluation. Risk checks can send action information, target information, and form values. By default, the connector sends these requests through the control plane to Clef (Cloudflare) via OpenRouter. Enum form suggestions use the same decision provider. If the decision model is temporarily unavailable, Aviato can use its configured LLM fallback.
In Workspace settings → AI, add your own OpenRouter API key to bill decisions and their LLM fallback to your OpenRouter account. Without a workspace key, eligible requests use the plan's included AI credits and the platform key. A separate Cloudflare key is not required. The key applies to every project in the workspace, so only workspace owners and admins without a custom role on any project can set or remove it. Each change is recorded in the audit trail of every project (ai_settings.openrouter_key.set, ai_settings.openrouter_key.remove); the key itself is never recorded.
The server operator can set AI_DECISION_MODEL to cloudflare/clef (default), cloudflare/clef-flash, or typesafe/jev-1.13. Existing deployments with an explicit Jev setting keep using Jev until that setting changes. These models apply to typed decisions; ask-your-data uses the separate language model.
Clef requests have a conservative 2,000-byte UTF-8 limit for the serialized state and questions together to avoid upstream text truncation. Oversized requests fail without an LLM fallback; reduce the selected input fields or their content, or ask the server operator to configure another decision model. This is a byte limit, not a 2,000-character limit.
For local decisions, point the connector's AVIATO_DECISIONS_URL at a self-hosted Laya server. Decision inputs then stay in your infrastructure instead of passing through the control plane to OpenRouter.
Platform-funded requests have durable request quotas and concurrency limits. These credits are admission limits, not a promise of a particular currency cost.
Approvals and hosted connections
Approval targets and form values are sent to the control plane; form values are encrypted at rest. A hosted connector also requires its database connection details to be managed by the hosting platform. A self-hosted connector keeps its database credentials in your deployment.
Audit values and destinations
Full audit redaction mode can include business field values. Select a more restrictive mode if those values should remain out of the audit store. Audit exports and streaming send the resulting redacted events to your configured destination.