Privacy and contact posture
Veristio Web currently presents public, static information about the company, products, services, and their maturity boundaries.
The public contact paths use ordinary email links. Clicking one asks your browser to open your email application; this site does not submit a contact form or store the message in the page.
If you choose to send an email, the message leaves this static site and is handled through your email service and the receiving mailbox. Do not include passwords, credentials, tokens, account numbers, payment data, broker details, or other sensitive records.
Pre-launch subscriber privacy design
The Verified Intelligence Briefing customer path is designed to minimize account and subscription data, separate Stripe payment handling from canonical Veristio entitlement truth, preserve consent and lifecycle evidence, and support applicable privacy-right requests.
Stripe is the intended payment processor for card and billing-provider handling. Payment-card details are expected to be handled by Stripe rather than stored by Veristio Web. Shared Identity/Auth0 is the corrected identity-provider direction for account registration, sign-in, recovery, and privileged-role controls before launch.
Subscriber support, billing questions, cancellation assistance, refund or billing-error reports, account/access problems, and account deletion or privacy-right requests should route to support@veristio.com once the service opens.
No subscriber account or payment data is currently collected by the public site. A production privacy notice identifying the accepted identity, payment, persistence, retention, support, privacy-rights, deletion, backup, and audit workflows must be approved before checkout opens.
What the current public site does not provide
The current public routes do not provide account registration, subscription enrollment, payment, a customer dashboard, a general contact form, or an in-page service intake workflow.
Any future form, account, storage, provider-backed workflow, or expanded data-handling posture requires separate review and an updated public explanation before implementation.