BreachSpiderBREACHSPIDER
Research Intel Features Docs About Sign In Sign Up Free

Trust Center

Trust Center, version 2.0, November 8, 2026. CITED Relevance LLC, operator of BreachSpider.

What BreachSpider does with the information you give it, how the service is built and run, and what is not in place yet. Every statement on this page describes the service as it is configured today. Where a detail is still to be confirmed, it says so.

On this page

The short version

Architecture

Tenant isolation

Every customer record belongs to one organization. Isolation is enforced twice:

  1. In the application. Each request is resolved to the caller's organization from the session or API key, and every query is scoped to it. A record of another organization generally answers "not found", so its existence is not revealed.
  2. In the database. PostgreSQL row-level security policies on the customer tables compare each row's organization with the organization set on the connection for that request. A connection with no signed-in caller is set to an organization that does not exist, so a query that runs without a caller returns nothing rather than another customer's rows.

Tests that create two throwaway organizations and try to read across them run in the release checks. MSSP accounts can see the client organizations linked to them, and only those.

Encryption

WhereWhat is in place
Browser to CloudflareHTTPS with TLS 1.2 or 1.3; HSTS.
Cloudflare to serverHTTPS with TLS 1.2 or 1.3 to the origin certificate.
Database backupsEach nightly dump is encrypted with AES-256 on the server as it is written, before it is copied off the server. It never touches disk unencrypted.
Server file backupsEncrypted by the backup tool (restic) before upload.
Vault filesEncrypted in your browser before upload (Argon2id key derivation, AES-256-GCM). BreachSpider never receives the passphrase, the recovery key, any key, the file or its name.
Workspace backup exportsEncrypted in your browser with a passphrase you choose (AES-256-GCM). BreachSpider cannot open or recover them.
Production databaseNot encrypted by BreachSpider. The database files sit on the hosting provider's storage. Device fields you enter, including IP addresses or serial numbers if you choose to enter them, are stored without field-level encryption.

Sign-in, sessions and API keys

Rate limits and abuse controls

Audit logging

Changes to accounts, team members, keys, devices, records and settings are written to an audit log with the organization, the person, the action, the record affected, the time, and the IP address and browser of the request. Calls to the assistant made for account features are recorded with the model used and the scope of what it read. The audit log can be read in Settings and exported, depending on role and plan. Writing an audit record never blocks the action itself, so a failed audit write is logged as an error for us to investigate.

Backups, vault and integrity seals

Service backups

Documents and configuration vault

Where an organization uses the vault, files are encrypted in the browser and stored as ciphertext in a private Backblaze B2 bucket under an object name that is never reused. A separate signing service, running as its own operating system user with its own keys and its own append-only ledger, seals each version: it reads the stored bytes itself, measures their digest and length, and signs a manifest that extends a hash chain per organization. The web application cannot read the signing keys and cannot ask the signer to sign a digest it supplies.

The assistant

The assistant (Claude, by Anthropic) answers questions, explains findings, maps unfamiliar import columns, suggests products for import rows the engine could not resolve, and drafts tickets and report summaries. It never decides whether a CVE applies to a device: those findings come from the matching engine, and every suggestion the assistant makes for an import row goes through the same engine before a person accepts it.

When you use it, BreachSpider sends Anthropic your message, the earlier messages in that conversation, and the account context the answer needs, which can include device names, site names, products, versions and findings. Conversations are saved to your account so you can return to them, and you can delete them. Anthropic processes this data as our subprocessor under its commercial terms.

If a user asks for an answer to be read aloud, the text of that answer is sent to ElevenLabs to produce the audio.

Data sources and citation policy

BreachSpider's findings are built from public and vendor-published records. Naming a source here describes where data comes from; it does not mean that source endorses BreachSpider.

Citation rules the product follows:

More detail: Editorial policy.

Subprocessors

The current list, with what each one receives, is on the Subprocessors page: OVHcloud (hosting), Cloudflare (edge network), Backblaze (encrypted backups and vault storage), Anthropic (the assistant), Resend (email), ElevenLabs (read-aloud audio), Stripe (card payments) and Google Analytics (public marketing pages only).

Retention

Saved reports and the evidence in them are kept for 3 years. Device check history, change events, assistant action records and daily progress snapshots are removed after 3 years. When an organization is deleted, its data is removed within 24 hours; backups age out within about 30 days. The full schedule is on the Data retention page.

Compliance status, stated plainly

How BreachSpider supports common frameworks

Using BreachSpider does not make an organization meet any standard. These are the specific tasks it helps with; your assessor decides what counts as evidence.

Requirement areaHow BreachSpider helps
NERC CIP-007 R2 (security patch management: evaluate applicable patches at least once every 35 calendar days)Lists, per device and version, the vendor-published fixes and advisories that apply, with sources and dates, and keeps a dated history of each check and of the actions you record.
NERC CIP-010 R3 (vulnerability assessments)A device-by-device list of matching CVEs with the affected range and its source, exportable as a report.
IEC 62443-2-3 (patch management in industrial automation and control systems)Tracks which vendor fixes apply to which installed versions and records what was done, by whom and when.
Asset inventory practices in most frameworksA device inventory with vendor, product, version, site and lifecycle status, imported from your own lists.

Reporting a vulnerability

Report security issues in BreachSpider to [email protected]. The policy, scope and our commitment to good-faith researchers are in the vulnerability disclosure policy; the machine-readable contact is at /.well-known/security.txt.

Legal documents and versions

DocumentVersionDateWhat it covers
Trust Center2.0November 8, 2026How BreachSpider is built and run: isolation, encryption, access, backups and integrity seals, data sources, subprocessors and an honest compliance status.
Terms of Service2.0November 8, 2026The agreement for using BreachSpider: what the service is and is not, your data, acceptable use, liability, and disputes.
Privacy Policy2.0November 8, 2026What personal data BreachSpider collects, why, who receives it, how long it is kept and your rights.
Cookie Notice1.0November 8, 2026Every cookie and browser storage item BreachSpider sets, what it is for and how long it lasts.
Acceptable Use Policy2.0November 8, 2026What you may not do with BreachSpider, permitted security work, and how we enforce the policy.
Data Processing Addendum2.0November 8, 2026How we process customer data for you as a processor: instructions, subprocessors, security measures, incidents, deletion and audits.
Subprocessors1.0November 8, 2026The companies that process data for BreachSpider, what each receives and why.
API and SDK Terms1.0November 8, 2026Terms for the BreachSpider API, the Python SDK, the MCP server and the widget: keys, limits, versioning, attribution and what you may build.
Data Retention Schedule1.0November 8, 2026How long each kind of record is kept, what removes it, and what happens when an organization is deleted.
Security and Vulnerability Disclosure Policy2.0November 8, 2026How to report a vulnerability in BreachSpider, what is in scope, what we commit to, and where the security overview lives.
Service Level Agreement1.xSeptember 28, 2026Not revised in this set; under review by the owner.

Changes between versions are listed on the Legal page.