Secure delivery
We use reputable service providers, HTTPS for public web traffic, and access controls appropriate to the systems we manage. Architecture and safeguards vary with project scope and data sensitivity.
Our current security approach—without claiming certifications or guarantees we do not have.
Effective 22 July 2026 · Last updated 22 July 2026We use reputable service providers, HTTPS for public web traffic, and access controls appropriate to the systems we manage. Architecture and safeguards vary with project scope and data sensitivity.
We aim to collect and retain only what is reasonably needed for an enquiry, project, support, or legitimate records. Sensitive information should not be placed unnecessarily in forms, demos, prompts, or support messages.
For deployed AI systems we recommend restricted permissions, clear tool access, appropriate logging, human escalation, scenario testing, and human review for sensitive or consequential decisions.
Clients should protect credentials, use multi-factor authentication where available, restrict access, maintain connected accounts, obtain required consent, and report suspicious activity promptly.
No website, automation, or connected service can be guaranteed completely secure or continuously available. We work to reduce reasonable risks and respond responsibly when an issue is reported.
Email copywrk0@gmail.com with the affected URL, reproduction steps, and likely impact. Do not access other people’s data, disrupt services, run destructive testing, or publish details before we have had a reasonable opportunity to investigate.