Security posture
ProofRelay is built for controlled assurance workflows. Claims are not buyer-facing until reviewed, evidence-backed, and permitted by disclosure rules.
Security
Built for controlled assurance workflows where mistakes matter.
ProofRelay is designed to govern buyer-facing trust output with reviewed claims, evidence, freshness checks, disclosure rules, and auditability.
Governed release checklist
Buyer-facing output waits for controls
Question mapped01
Claim reviewed02
Evidence linked03
Owner assigned04
Freshness checked05
Disclosure permitted06
Proof pack approved07
Honest posture
Conservative by design, explicit about what is claimed.
No SOC 2 certification, external pentest, or compliance certification is claimed on this public website. Current security posture details are provided directly during private pilots and procurement review.
Controlled output architecture
Drafting is separate from release.
ProofRelay treats buyer-facing output as a governed release step, not an automatic AI action.
AI draft
Cited suggestions from approved material
Human review
Owners approve buyer-facing wording
Control checks
Evidence, freshness, and disclosure gates
Buyer-facing output
Reviewed response or proof pack
Access controls
The platform is designed around role-aware access, owner assignment, review workflows, and separation between internal proof management and buyer-facing output.
Data handling
Teams should upload only the assurance artifacts needed for their review workflow. ProofRelay does not require customer secrets, production credentials, or private keys.
LLM usage
AI can draft cited suggestions from approved material, but AI does not silently create truth or approve buyer-facing answers. Human review remains the release gate.
Buyer-facing output safety
Evidence, freshness, and disclosure checks gate buyer-facing output. Restricted artifacts can be marked for internal use, NDA-only sharing, or exclusion from proof packs.
Proof-pack sharing
Proof packs can use expiry and revocation patterns so teams can share buyer-specific evidence without treating every artifact as permanently public.
Audit logging
Audit logs track material actions such as claim updates, approvals, evidence changes, proof-pack creation, and buyer-facing export decisions.
Deletion and offboarding
Deletion and offboarding workflows should be handled through the customer’s pilot or production agreement. Contact ProofRelay for current operational details.
AI can draft; humans approve. ProofRelay governs what leaves the building.
For security questions or a current data handling packet, contact the ProofRelay team.
Contact security