Trust & Security

Your data stays on your infrastructure, under your rules

I build AI systems that run on your own servers, in your cloud account or with no external connection at all. Your customers will share their test results and SCADA logs only with a supplier they trust. That is step 3 of the approach. This page says where data lives, which models read it and what is logged. Your compliance team signs off, not mine.

Deployment Options

Every option does the same job. The difference is how far your data may travel.

On-Premises

Full deployment inside your data centre. No external network calls. You keep complete physical and logical control.

VPC / Private Cloud

Deployed in your AWS, Azure or GCP environment: your account, your keys, isolated at network level.

Air-Gapped

No external connection at all. Local models run through Ollama, and the system can sit on a SCADA or OT network.

Hybrid

Processing stays on your premises, with selected cloud services. You define what stays local and what may leave.

This website runs on Cloudflare Workers, D1 and R2. That is my choice for my own platform, not a requirement for yours. Client deployments run on whatever you specify: AWS, Azure, GCP, bare metal or your own on-premises systems.

Data & Models

You decide where your data lives and which models read it. Both decisions are written down.

Residency: your data stays in the region you name. I do not copy it or move it without your written agreement.
Encryption: AES-256 at rest and TLS 1.3 in transit, with keys held by your team or your cloud provider's key service.
Retention: you set the policy and I implement it. The default keeps nothing past the active session.
Chat and AI interactions: processed as they happen and not stored past the session unless you opt in. Local models through Ollama send no data out. Commercial AI models from Anthropic or OpenAI run under their enterprise terms, when the extra capability is worth it.
No lock-in: every system I build can switch between local and API models, so the design never ties you to one supplier.

Audit, Compliance & Source Code

Every system I build logs what it did and who asked. Each request carries a timestamp and a hash of its input and output. The log is append-only and includes permission changes. A GDPR data-subject request can be answered from the application, with no database export. None of that makes a system compliant: your auditor decides that. What I can promise is that the evidence already exists when an audit under SOX or NERC CIP asks for it.

Certifications belong to where the code runs, not to the application. Cloudflare publishes SOC 2 Type II and ISO 27001 reports for the infrastructure this website uses. A deployment in your AWS, Azure or GCP account inherits that provider's attestations instead, and your compliance team joins them to the application's controls. I design to the IEEE and IEC standards that govern the equipment in the room, and the drawings name them.

You receive the source code for everything I build, with no compiled binaries and no obfuscation, so your security team can check it. The repository can go into escrow if business continuity requires it. Any maintenance agreement is optional, and you can end it when you like.

Need a Security Overview for Your Team?

Book a call and I will walk your security and compliance team through the architecture, the data handling and the deployment options before any of your customers' data moves.

Book a Technical Scoping CallPrivacy PolicyAI Policy