Table of Contents

Privacy

Last updated:

Privacy settings let each signed-in user keep agent execution on local resources. Offline mode limits public egress for that user's agent runs without changing other users or shutting down the host network.

Note

Egress means data leaving the machine or local network for an outside service.

Turn on offline mode

  1. Open Settings > Accounts & Access > Privacy.
  2. Enable Keep agent runs offline.
  3. Click Save Privacy Settings.

The saved setting applies to later runs and rebuilds cached agents. Reset discards an unsaved draft.

When offline mode is active, Oscova blocks:

Surface Offline behavior
Model providers Providers classified as cloud are rejected before credential lookup
Tools Tools effectively classified as Internet are not exposed to the agent
Host-managed HTTP Requests to public endpoints are rejected during the run
Public HTTP MCP Public server calls and air-gapped connection attempts are blocked
Embeddings Cloud-backed memory search and vector indexing are blocked
Speech Cloud speech recognition and synthesis providers are blocked
Shell Host execution is rejected. Docker shell networking is disabled

Local model providers, local tools, loopback services, and LAN endpoints remain available when their own configuration allows them.

Important

Offline mode is an agent-run policy, not a host-wide network switch. Settings operations and explicitly enabled external channel transports have their own behavior.

Sign out an idle browser

Use Automatic sign-out to end this browser profile's session after a period without human activity.

  1. Open Settings > Accounts & Access > Privacy.
  2. Under Automatic sign-out, choose Off, 5 minutes, 15 minutes, or 30 minutes.
  3. Click Save Privacy Settings.

Mouse, touch, keyboard, scrolling, and submitting a message count as activity. Agent responses, streaming output, text-to-speech, microphone listening, scheduled work, and connected-channel traffic do not extend the idle period.

Open Oscova tabs for the same user in one browser profile share activity and the selected timeout. A different browser profile, device, or signed-in user keeps an independent idle clock.

Automatic sign-out uses ordinary logout. It clears the browser session and discards incognito chats. It does not lock the Host's already-unlocked confidential-data key, remove the retained user scope, or cancel agent tasks and ordinary detached work.

Read the live effect

When the draft toggle is on, Live effect shows:

  • Internet: the number of currently known Internet-classified tools disabled by the policy.
  • Cloud providers blocked: configured model providers classified as cloud.
  • Local network: a reminder that loopback and LAN endpoints remain available.
  • Redaction: saved-secret masking is always on.
  • Connected channels: Discord and Telegram remain external transports when enabled.

The count and provider list explain the current configuration. They are not a complete list of every possible external action, and they do not include cloud speech or channel traffic.

Saved secret values are masked in agent logs, approval details, and captured request data. Redaction cannot be disabled from this page.

Understand connected channels

Discord and Telegram connect to their own external servers for polling or gateway traffic, approvals, and replies. Enabling Offline mode does not stop those bot connections, but local-only runs do not download attachments from either channel.

Messages received through those channels still run the main agent under the user's global and agent-level local-only policy. This can keep model, embedding, speech, shell, and tool execution local while the channel transport itself remains external.

Outbound channel replies appear in the run's egress audit. Inbound gateway, polling, and attachment transport stay outside that ledger because they bring data into Oscova rather than sending run data out.

Disable the Discord or Telegram bot in its channel settings if the transport must stop using the network.

Keep one agent local only

Use agent-level Local only when one agent must stay local while the user's other agents may use public services.

  1. Open Settings > Agents.
  2. Edit the agent.
  3. Enable Local only.
  4. Save the agent.

Global Offline mode and agent-level Local only combine as a ceiling. An agent cannot disable the user's active global policy, and a delegated agent cannot weaken the initiating run's offline posture.

Agent-level local-only applies the same provider, tool, embedding, speech, and shell restrictions to that agent's runs.

Keep one agent's stored work confidential

Confidential Chat is separate from Local only. Local only controls where a run may send data. Confidential Chat encrypts that agent's saved chats and task runs and excludes its conversations from memory, indexing, and reflection.

The setting requires your vault to be unlocked. Logging out leaves the unlocked key in the running Host so background tasks can continue. Restarting the Host locks it. Oscova asks for the Vault Password before loading authenticated content.

If a confidential scheduled run becomes due while locked, Oscova records it as skipped without running the agent or sending content through a hook or notification channel. Recurring tasks stay enabled. Run a skipped one-shot manually after unlocking.

Classify provider endpoints

Oscova classifies model endpoints automatically:

  • Loopback, private LAN, and link-local addresses are local.
  • A hostname is local only when all its resolved addresses are local.
  • Public, unresolved, or mixed local/public DNS results are cloud.
  • Built-in local provider types are local.

For a proxy or gateway that automatic detection classifies incorrectly, edit the provider and set Endpoint scope:

  • Auto-detect uses the provider type and endpoint.
  • Treat as local allows the provider in local-only runs.
  • Treat as cloud blocks the provider in local-only runs.

Use Treat as local only when you control the endpoint and know traffic remains on an approved local or LAN route.

Tool network classification is managed separately under Settings > Tools. A tool marked Can reach network is not removed solely by the Internet-tool filter, so classify tools according to their real purpose.

Troubleshooting

  • No provider is available: configure a local provider or correct its Endpoint scope.
  • A LAN provider is blocked: confirm every DNS result is local, or choose Treat as local after verification.
  • A cloud credential error appears: confirm the run is using the intended local provider. Cloud providers should be blocked first.
  • An Internet tool is missing: turn off the applicable local-only policy or use a local alternative.
  • A public HTTP MCP server is unavailable: public MCP traffic is blocked during the air-gapped run.
  • Memory search or indexing fails: select a local embedding provider.
  • Speech fails: select a local speech provider or leave local-only mode.
  • Host shell fails: use Container Sandboxed mode for offline execution.
  • Discord or Telegram still sends traffic: stop that channel. Offline mode does not disable its transport.