Does the browser extension send my prompts anywhere?

No. The token count, the price, the personal-data and secret checks and the writing suggestions run in the page on your device. Nothing leaves the page unless you connect a workspace and ask the router for a quote or a second opinion - and then only the text you chose to send.

Are prompts and answers stored by the platform?

Not by default. The platform meters the request - tokens, cost, target, latency - and keeps the trace of the decision. The prompt and the answer are kept only when a workspace turns on log_payloads in its policy, and they are deleted with the workspace.

Can a rule be overridden by a good score?

No. Constraints - data boundary, region, tenant, cost and latency ceilings, allowed and denied targets, PII handling - are applied before any strategy scores a candidate. A target that fails a constraint is not in the ranking; the trace lists it under policy rejections with the reason.

How do I prove where a request went six months later?

Every decision and every reported outcome is appended to a hash-chained audit trail per workspace. Export it as CSV or JSONL from the dashboard; each record links to the previous one, so a changed or missing row is detectable.

Security and data control

Safe before it is sent. Governed while it routes. Provable afterwards.

OpenSmartRoute treats a request as something to protect at three moments: on the device where a person writes it, in the router where policy decides who may answer, and on the record where an auditor will look for it. Each moment has a control you can see the state of, not a sentence in a policy document.

Open the governance report Read the security guide

Controls the governance report shows in force

Input guard
PII redaction
Steering strip
Output guard
Budgets
Circuit breakers
Tracing
Metrics
Audit chain
Decision cache
Routing SLM
Autopilot

Each is a setting of the deployment. The report shows its state - on, off, or which mode - with a compliance posture score and the findings behind it.

On the device

Caught before the prompt leaves.

The browser extension and the desktop app read a draft on the device first. Personal details and pasted secrets are highlighted; one click swaps them for placeholders, one click undoes it. The site never sees the original unless you send it anyway.

Looks for e-mail addresses, phone numbers, card numbers, IBANs, national ids (SSN, Aadhaar), IP addresses, API keys and tokens and pasted secrets
Redact, Undo, Redact and send, Send anyway - the choice stays with the personExtension
The same checks over any app on Windows, macOS and LinuxDesktop
Administrators pin the analysis policy for everyone with managed settingsManaged

In the router

Policy first. Scores second.

Constraints run before any strategy weighs a candidate, so no score can trade them away. The input guard strips injection and steering; PII is redacted before it reaches a model; the output guard flags or blocks leaked secrets on the way back.

Data boundary, region, tenant, cost and latency ceilings, allowed and denied targetsPolicy
Input guard for injection and gadget attacks; a learned detector for steeringGuide
Tool-parameter provenance and resource limits for agents and tools; signed MCP manifestsMCP
Circuit breakers and budgets per target, workspace and tenantEnterprise

On the record

Every decision, provable later.

Decisions and outcomes are appended to a hash-chained audit trail per workspace. Prompts and answers are not kept unless you say so. Who may see any of it is a matter of roles, single sign-on and the keys you rotate.

Hash-chained audit trail of decisions and outcomes, exportable as CSV or JSONLAudit
Payload logging off by default; retention you set; deleted with the workspacePrivacy
Members with roles, SSO, an organisation's verified addresses, key hygieneMembers
Public status with the readiness checks this deployment passes nowStatus

One policy, every request

A rule the router cannot break, written in plain fields.

The workspace policy is edited from the governance page and applied to every key the workspace holds. It is not a prompt, a suggestion or a weight - a target that fails it is not a candidate, and the trace says so.

Edit the policy Watch a rejection in the trace

Workspace policyyaml

# the workspace policy, as the dashboard writes it
data_boundary: private        # never a public endpoint
region: eu                    # EU targets only
contains_pii: true            # route as if every request may carry PII
deny_targets: [llm-frontier]  # never this one, whatever the score
max_cost_per_1k: 0.01
daily_budget_usd: 250
log_payloads: false           # prompts and answers are not kept

Questions security teams ask

Straight answers.

Does the browser extension send my prompts anywhere?: No. The token count, the price, the personal-data and secret checks and the writing suggestions run in the page on your device. Nothing leaves the page unless you connect a workspace and ask the router for a quote or a second opinion - and then only the text you chose to send.
Are prompts and answers stored by the platform?: Not by default. The platform meters the request - tokens, cost, target, latency - and keeps the trace of the decision. The prompt and the answer are kept only when a workspace turns on log_payloads in its policy, and they are deleted with the workspace.
Can a rule be overridden by a good score?: No. Constraints - data boundary, region, tenant, cost and latency ceilings, allowed and denied targets, PII handling - are applied before any strategy scores a candidate. A target that fails a constraint is not in the ranking; the trace lists it under policy rejections with the reason.
How do I prove where a request went six months later?: Every decision and every reported outcome is appended to a hash-chained audit trail per workspace. Export it as CSV or JSONL from the dashboard; each record links to the previous one, so a changed or missing row is detectable.

Found something? Report a vulnerability. The security review lists what was examined and what was fixed.

Set the policy once. Every request obeys it.

Create a workspace, write the data boundary and the region into its policy, and route a request that breaks it - the trace shows the rejection.

Create a free account Talk to sales

Free plan, no card. Fifteen thousand decisions a month with the full trace.

Safe before it is sent. Governed while it routes. Provable afterwards.

Caught before the prompt leaves.

Looks for e-mail addresses, phone numbers, card numbers, IBANs, national ids (SSN, Aadhaar), IP addresses, API keys and tokens and pasted secrets

Redact, Undo, Redact and send, Send anyway - the choice stays with the personExtension

The same checks over any app on Windows, macOS and LinuxDesktop

Administrators pin the analysis policy for everyone with managed settingsManaged

Policy first. Scores second.

Data boundary, region, tenant, cost and latency ceilings, allowed and denied targetsPolicy

Input guard for injection and gadget attacks; a learned detector for steeringGuide

Tool-parameter provenance and resource limits for agents and tools; signed MCP manifestsMCP

Circuit breakers and budgets per target, workspace and tenantEnterprise

Every decision, provable later.

Hash-chained audit trail of decisions and outcomes, exportable as CSV or JSONLAudit

Payload logging off by default; retention you set; deleted with the workspacePrivacy

Members with roles, SSO, an organisation's verified addresses, key hygieneMembers

Public status with the readiness checks this deployment passes nowStatus

# the workspace policy, as the dashboard writes it data_boundary: private # never a public endpoint region: eu # EU targets only contains_pii: true # route as if every request may carry PII deny_targets: [llm-frontier] # never this one, whatever the score max_cost_per_1k: 0.01 daily_budget_usd: 250 log_payloads: false # prompts and answers are not kept