ILLUSTRATIVE · CONTROLLED
What we collect
Name, work email, company, role/team, company size, primary service line, launches per quarter, handoff system, largest delay, desired timeline, and consent.
DATA-BOUNDARY CUTAWAY
A narrow path for qualification data.
The website accepts only the fields needed to discuss a workflow audit. A sealed boundary blocks document uploads and sensitive client material.
Concept-stage product · All workflow interfaces and data shown are illustrative.
ORYVANTAILLUSTRATIVE
ILLUSTRATIVE · CONTROLLED
How it moves
Your browser sends JSON over the site’s /api/leads endpoint. The application validates origin, size, types, allowed values, honeypot, and rate limits.
ILLUSTRATIVE · CONTROLLED
How it is stored
Accepted records receive a submission ID and UTC timestamp, then are atomically appended to a server-local JSON file. The application does not store your IP, request headers, or honeypot value.
ILLUSTRATIVE · CONTROLLED
Retention and access
Records are retained for sales follow-up without an automated expiration. Access is by server administrators over SSH. There is currently no self-service access or deletion portal; contact us by replying to our follow-up email.
ILLUSTRATIVE · CONTROLLED
Infrastructure caveat
Although the application does not record IP addresses, upstream infrastructure such as a reverse proxy, hosting provider, or network service may keep operational logs under its own configuration.
ILLUSTRATIVE · CONTROLLED
Never submit
Client names, contracts, credentials, vulnerabilities, evidence, regulated data, or any other sensitive information. This site has no file upload.
START WITH A FIXED-SCOPE AUDIT