Home

Legal and IP

Catch privileged and client markers before Send. Govern agent tools separately.

UK-first AI governance for law firms and in-house legal teams: local Browser controls for human prompts and a separate MCP gateway for agent tool calls.

Start a team pilot →

The problem

A matter reference, privilege marker or client identifier can be enough to create a confidentiality incident. The same risk appears again when an agent reaches a document, case-management or knowledge tool through MCP.

Two separate products

People at Send

Sovara Browser

  • - A Legal preset for privilege phrases, matter and client references, court references and SRA numbers.
  • - Local checks before Send, with warnings that let a user review risky context without uploading the draft for inspection.
  • - Central Browser policy and metadata evidence for a team pilot.
Explore Sovara Browser →

Agents at the tool

Sovara Gateway

  • - Verified agent identity for routed traffic and policy at the configured MCP tool-call boundary.
  • - Tool allow-lists, roles, scopes, raw argument patterns, approvals, time windows and rate controls.
  • - Structured masked evidence in your chosen sink, with optional response DLP and a tamper-evident Gateway hash chain.
Explore Sovara Gateway →

One-page sector brief

Legal AI governance one-page brief

A concise overview of Sovara Browser controls for law firms and in-house legal teams. It covers the Browser product specifically and is designed to share with security, compliance and operational stakeholders.

View the one-page brief →

PDF · 1 page

Consistent evidence, separate stores

Browser: metadata-only events for decisions on supported AI chat sites; signed Browser evidence exports are available when signing is configured.

Gateway: tool-call events with agent identity, masked arguments, policy outcome, latency and upstream status.

The shared schema makes later analysis consistent; it does not merge the two products or their stores automatically.

Start with one team and one workflow.

We will scope the surface, policy, evidence and success criteria before rollout. Browser and Gateway can be piloted together, but they remain separate workstreams and products.

Start a team pilot →