SECURITY & PRIVACY

Enterprise controls without the enterprise drag

Your knowledge is your business. BeforeQuery isolates every workspace, masks PII before content reaches any LLM, never trains models on your data, and ships the SSO, audit, and permission controls your security review will ask about.

Start FreeSecurity Details
Capabilities

Controls that matter

The security posture behind every deployment

01
Isolated by design

Data Protection

  • Workspace isolation for content, semantic vectors, and chats
  • Encryption in transit and at rest
  • PII masked before any LLM call
  • Your data is never used to train models
  • Delete a source and its indexed content goes with it
02
Your IdP, your rules

Identity & Access

  • SSO via OIDC and SAML 2.0
  • Per-knowledge-base permissions for members
  • Restricted document visibility within a knowledge base
  • Client keys with scoped, revocable access
  • Allowed-groups enforcement on integration keys
03
Reconstruct anything

Auditability

  • Workspace audit logs for admin actions
  • Conversation history with the source shown
  • Traces of retrieval behind every answer
  • Signature verification on every webhook
Safe by architecture

Grounded answers are a security feature

The biggest AI risk in customer-facing deployments isn't a breach — it's the assistant confidently saying something your company never approved. BeforeQuery's architecture answers only from content you indexed, shows the source paragraph, and falls back transparently otherwise. Combined with human approval on AI Actions, the blast radius of any single answer stays small.

  • Answers bounded by your approved, indexed content
  • Citations make every claim verifiable
  • Public surfaces retrieve only public documents
  • Enterprise plan adds advanced governance and SSO enforcement
What teams say

Deployed in production.

“Deployed on our docs site in an afternoon. Every answer shows the source, and the abstention gate means we've never had a customer complain about a made-up answer.”
Priya Nair
Head of Customer Support · Supabase
“The knowledge base connected to our Slack, Confluence, and helpdesk in one setup. On-call teams get the same grounded answer whether they ask in chat, in the widget, or from Cursor.”
Tom Richter
IT Operations Manager · Grafana Labs
“The gap analytics turned into a real docs backlog. Deflection went up because we finally knew which pages were missing — the AI told us.”
Ana Castillo
VP of Customer Experience · Clerk

Frequently Asked Questions

Common questions about Security & Privacy

No. Indexed content, semantic vectors, and conversations stay isolated to your workspace and are used only to answer your own questions. Nothing is shared across customers or used for model training.
Personally identifiable information in questions is masked before content reaches the LLM, and conversations are stored with that masking applied. Data is encrypted in transit and at rest.
OIDC and SAML 2.0 connections are supported per workspace, so employees authenticate through your identity provider. Enterprise plans include SSO alongside audit logs and advanced governance.
Three layers: separate knowledge bases for public and internal content, per-knowledge-base permissions for members, and restricted document visibility within a knowledge base. Public widgets and API keys retrieve only public documents.

Bring it to your security review

Read the security overview, or talk to us about enterprise requirements.

Get Started Free