Privacy summary

Voidproof Privacy

Voidproof collects and processes information needed to operate customer accounts, proof requests, evidence intake, billing, support, public receipts, public registers, revocation status, and security operations.

Private Customer Data

Private customer data belongs behind authenticated customer and owner surfaces. It must not be bundled into public static sites, public verifier assets, public marketing pages, or public register files unless that information is intentionally part of a public receipt or register record.

Public Proof Data

Public receipts, signed registers, revocation status, defect notices, and verifier outputs may be public when they are part of the proof reliance model. The proof package remains the object of reliance.

Billing And Account Data

Billing, subscription, invoice, and payment-method handling may be processed through a payment provider. Owner access is operational and non-billable. Public verification must not require payment.

Support And Notifications

Transactional email may notify customers about invitations, proof delivery, blocked proof requests, and operational alerts. Email must not contain private evidence or proof package contents when a public receipt link is the safe reference.

Reliance Boundary

Reliance is limited to the proof package, public verification, declared scope, declared window, coverage and limits, and public register status. Public verification must remain free and no-login. Private explanation cannot override verifier output.

This summary explains the product's privacy posture in plain language. Customer-specific processing terms may add more detail where required.