No Secrets Through the Public Website
Do not submit passwords, production keys, connection strings, certificates, tokens, regulated data, or customer confidential material through the public website or normal email.
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.
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. They 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.
Clients remain responsible for approving changes, granting access, maintaining production controls, and validating compliance obligations for their own environments.
Secure Intake
Agree on the channel and access model before sharing confidential technical material.