The Public Website Stores No Accounts
The website has no login, no visitor accounts, and no stored visitor profiles. It is served over HTTPS, form submissions use bot protection, and submitted details go only to the tools used to run the business.
Security
Use the website for service information, booking, and basic contact. Client findings, diagrams, exports, approvals, and attachments are handled through the agreed delivery process.
Last updated May 31, 2026
The website has no login, no visitor accounts, and no stored visitor profiles. It is served over HTTPS, form submissions use bot protection, and submitted details go only to the tools used to run the business.
Do not submit passwords, production keys, connection strings, certificates, tokens, regulated data, or customer confidential material through the public website or normal email.
When project access is needed, use scoped, time-limited, least-privilege access with named accounts and a client owner.
Runbooks, architecture notes, and decision records must not embed secrets. Share sensitive operational details through an agreed secure process.
Client decision records, findings, diagrams, approval notes, and attachments are confidential engagement records and are not published on the public website.
Confidential client decisions, approvals, and technical material stay out of AI processing unless the client approves a secure workflow in writing.
Clients remain responsible for approving changes, granting access, maintaining production controls, and validating compliance obligations for their own environments.
To report a security issue with the website, email the address below or see /.well-known/security.txt. Do not include secrets or client data in the report.
Secure Intake
Agree on the channel and access model before you share confidential technical material.