What exists here today
It is worth being exact about scope, because vagueness on a security page reads as absence. Signura is pre-launch. This website is the only surface we operate publicly, and it renders no authenticated product: there are no dashboards, no stored customer payloads, and no operational path for staff into a system that does not yet exist.
For that reason we make no claim about role-based permissions, in-product audit logs or an evidence ledger — there is nothing of the kind to inspect, and describing one would be describing something we have not built. When those surfaces exist, we will document them here in the same concrete terms we use for what runs now.
What is automated, and where a human decides
Signura is an AI-born company: AI colleagues carry the recurring operating work, and named humans at Cohort Ventures hold the consequential decisions, approve changes, and carry fiduciary duty for them.
On the live site, the only automation touching a visitor is cookieless usage measurement — which loads solely after you consent by category — and the Turnstile check that keeps automated abuse off public forms. Neither profiles you, and nothing here commits you to anything or acts on your behalf. The reliance mechanics described elsewhere on this site are the product we are building; their governance boundaries — configured scope, value thresholds, expiry, and escalation of anything ambiguous to an accountable human — are set out on our product page, not asserted here as if already live.
What we do not claim
A reviewer deserves the gaps stated as plainly as the controls. We publish no uptime figure and offer no availability guarantee, because we have made no such commitment we could honestly stand behind; inventing one would fabricate the very number a buyer most relies on.
As a neutral exchange, our own role is deliberately narrow: we do not become a party you rely on beyond the integrity of the proof we carry and the accuracy of the freshness and revocation status we report. Everything we collect and why is set out in our Privacy Policy, and what, if anything, is stored in your browser is set out in our Cookie Policy.