Skip to content

Trust & Verification

This platform brokers introductions and deals between defense companies, active-duty operators, consultants, program managers, and private capital — relationships where privacy failures have real consequences. These are the standing safety invariants the platform is built on. They are not policy promises: most are enforced by tests that run on every change, and the signed exports can be verified by anyone, without trusting us.

Data privacy

  • Row-level security: members read their own rows; deal counterparties resolve through aliases, never raw identity.
  • Every aggregate statistic is k-anonymized — cohorts below k≥5 are suppressed entirely, not shown on small samples.
  • Active-duty operators are anonymized end to end: bio only, no matchable fields, enforced at storage, API, and AI layers.

Access control

  • Four privilege tiers — public, member, admin, super-admin — with every API route pinned to a tier.
  • The tier map is a continuously-run test suite: a route that weakens or forgets its guard fails the build before it ships.
  • Public endpoints are rate-limited and serve only k-anonymized or code-resident data.

Change safety

  • Features ship behind tiered flags; the highest-impact toggles require super-admin, and all changes are reversible without redeploys.
  • Moderation quarantines are flag-and-log, reversible, and audit-backed — deletion is never the first tool.
  • State-changing endpoints carry CSRF guards, verified by the same in-CI test discipline as the tier map.

Cryptographic proof

  • Exports that make claims — expert review receipts, operator impact ledgers, market-research memos, acquisition audit trails, CMMC attestations — are Ed25519-signed.
  • Verification keys are published at public endpoints, so auditors, contracting officers, and insurers can verify independently.
  • A signature proves the platform issued the claim at a point in time — it does not certify the claim's truth, and every attestation says so.

Verify without trusting us

Each signed export family publishes its Ed25519 verification key at a public, unauthenticated endpoint. Paste any attestation into the verifier and get a cryptographic ✅/❌ — nothing you paste is stored.

Verify an attestation

Honesty note: low-volume statistics are withheld rather than estimated, empty states are shown as empty, and signatures attest issuance — not truth. Questions or a suspected gap? Report it from your account; safety reports are reviewed under the same audited admin process as everything else.