Trust Center

Intelligence you can check

How findings are grounded in their sources, how collection stays healthy, and how your data is protected.

Answers you can check

A claim you cannot trace is a claim you have to take on faith. Every factual statement in a report traces back to the source it came from.

Every claim is cited

Follow any finding to the original intelligence and see exactly where it came from.

Fabrications don't reach you

Before a report is finished its facts are checked against its sources. Anything that doesn't trace back, such as an invented CVE or an unsupported attribution, is held for review rather than published.

Measured, not asserted

We evaluate our own extraction and analysis against a labelled benchmark and hold the pipeline to it. Accuracy is something we measure, not an adjective.

How the checking is held in place

Labelled datasets, not spot checks

Entity extraction, requirement routing, retrieval, citation faithfulness and answer quality each have a hand-labelled benchmark held in the codebase.

The evals block the build

Each one carries a regression floor and runs in continuous integration. A change that degrades accuracy fails the build rather than shipping quietly.

Vulnerability decisions are checked against CISA

Our prioritisation is tested against the published CISA coordinator decision table, so the reasoning matches a public standard rather than a private one.

Figures on request

Current scores, sample sizes and method go to security reviewers in technical due diligence. We would rather discuss a number with its denominator than print it without.

Healthy collection, not just collection

A source count is easy to put on a slide. Keeping those sources actually flowing is the harder part, and it decides whether a gap in your coverage is one you can see.

Sources break. We notice.

Feeds move, change format or go quiet. Source health is monitored and degradation is flagged, so a silently broken feed never becomes a silent gap.

Breadth with accountability

Every source is tracked for reliability, not just counted. Failing or low-value sources are surfaced and managed.

How your data is protected

Tenant isolation

Every organisation's data lives in its own isolated database schema. Your requirements, reports, notes and files are never visible to another tenant.

Encryption

Data encrypted in transit (TLS 1.3) and at rest (AES-256). Keys and credentials stored using environment-level encryption.

Access controls

Role-based access within each tenant: owners, admins and analysts see and do only what their role allows.

Compliance & documentation

Conundrum aligns with the major cybersecurity and data-protection standards regulated organisations face, and maps your intelligence workflow to the evidence they ask for.

See it against your own requirements