Review our security practices and public policies, meet our subprocessors, and contact us about documentation for your security review.
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.
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.
We rely on a small set of vendors to operate the service:
The full list lives in our Privacy Policy.
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.