Security boundaries for AI-assisted technical work.
VexASI keeps the public website, service intake, private source material, and AI-assisted review work separated so sensitive material does not leak into public surfaces.
The public site is not a private file portal.
VexASI.com is a public static website for service explanation, contact intake, public articles, and public reference pages. It is not used to host private project files, internal review tools, model artifacts, datasets, source PDFs, or client deliverables.
Email-first contact
The public contact form opens an email draft. The page does not upload files, create a portal account, or submit confidential source material to a VexASI web backend.
Private material stays off the public site
Project documents, review outputs, model logs, training candidates, internal dashboards, and evidence packets are not public website content.
Review controls before delivery
AI-assisted findings and records need source evidence, confidence context, review status, and service-boundary checks before they are used externally.
What VexASI Will Not Put On The Public Site
Private Documents
Private PDFs, drawings, specifications, owner criteria, reports, and confidential review text are not used as public examples without explicit approval.
Internal Tooling
Operator consoles, internal review fixtures, source registries, evidence packets, run logs, datasets, model paths, and local dashboards are not public product pages.
Unsupported Claims
VexASI does not present AI output as permit approval, code-enforcement review, responsible control, stamping, sealing, or a replacement for project-team obligations.
Training Leakage
Private source material is not converted into model training data by default. Training candidates require a separate approval and clean-room path.
Need to scope a secure workflow?
Start with the source types, review owners, delivery boundary, and what should never leave the private workflow.