Trust

Trust Center

How we protect your data, where our security program stands, and how to request documentation.
The short version

Review our security practices and public policies, meet our subprocessors, and contact us about documentation for your security review.

01

How we protect your data

Encryption and isolation
TLS protects data in transit. Credentials Boring stores directly use an encrypted workspace vault, and workspace data stays tenant-scoped.
Least-privilege access
Agents get only the tools and actions you grant — and you can revoke any connection at any time.
Human checkpoints
Agents can pause for feedback or missing context before continuing. New agents start with every connected action waiting for approval, and the assigned reviewer can approve the proposed call, modify its arguments, or reject it.
A reviewable record of every run
Each run records its steps, tool inputs and outputs, approvals, and cost for review. Tool payloads are kept 90 days; the outcome, output, and step list stay. Summaries of an agent's latest 100 runs export as CSV or JSON.
Sensitive values screened at run boundaries
Run inputs and tool results are screened for recognizable long-lived credentials, card numbers, and punctuated US Social Security numbers before they're stored or sent to the model. Cards keep their last four. Signed-link token parameters remain usable, and ordinary contact details stay intact: they're the substance of the work.
Your data stays yours
We never sell your data, and we never train foundation models on your content.
Resilient by design
Runs save their progress step by step, so eligible failed runs resume from the step that failed. In a numbered step plan, when an action's outcome is uncertain, Boring blocks automatic repetition instead of guessing.
02

Policies & documents

03

Security documentation

Evaluating Boring for your team? These topics are covered in our proposed security policies. The policy set is drafted and awaiting formal adoption; these summaries do not represent approved policies or evidence that every control is operating.

Information security
Program ownership, risk management, and the responsibilities behind our security practices.
Access control
Access approval, least privilege, periodic reviews, and removing access when someone leaves.
Vendor management
Assessing providers, reviewing their access to data, and tracking vendor risk.
Incident response
Assessing incidents, coordinating containment, communicating impact, and reviewing what happened.
Business continuity & recovery
Recovery responsibilities, proposed recovery objectives, and plans for testing restores.

Request security documents

Tell us what you need for your review. Our team will confirm what is available and its approval status before sharing. Requests are reviewed individually; submitting this form does not grant document access.

Please leave out credentials and sensitive company or customer data. We use your details to respond to your request, as described in our Privacy Policy.

04

Subprocessors

We rely on a small set of vendors to operate the service:

Composio — integrationsCloudflare — edge & hostingAnthropic / OpenAI — inferencePostHog — product analytics

The full list lives in our Privacy Policy.

05

Security program status

SOC 2 Type I
In progress

Control and policy work is underway. Boring has not yet received an independent SOC 2 audit report; we will update this page as the program advances.

Boring is in early access with design partners. Our public status pagereports checks against the API, database, storage, and integration catalog (cached ~30s on the API), and labels each one with what it actually measures. It reports the present moment only — we don't yet publish an incident log or uptime history — so if an incident touches your data or your runs, we also notify you directly by email.

Boring AI, Inc.legal@boringaico.comQuestions about your data? privacy@boringaico.com — we reply within 30 days.