Trust and security
Trust, security and the evidence behind both.
Security claims are cheap. This page lists what we actually do, what you can verify yourself in a browser, and what we will hand you in writing before you sign.
TLS 1.2+. HSTS. CSP. Nosniff. X-Frame-Options. All verifiable at securityheaders.com.
6
Controls, each with evidence
5min
Monitoring interval
24h
Incident notification window
90d
Log retention minimum
What you can check yourself
01
TLS
This site is served over TLS 1.2 or higher with HSTS enabled. Paste the domain into any TLS checker and confirm it.
02
Security headers
Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy and Permissions-Policy are set at the server, not just in a plugin. Check them at securityheaders.com.
03
No trackers before consent
Analytics loads only after consent. There is no advertising pixel on this site.
04
Published security contact
/.well-known/security.txt names the address for vulnerability reports.
What we do on every managed site
| Control | What it means in practice | Evidence we provide |
|---|---|---|
| Patching | Weekly maintenance window; critical fixes within 24 hours; snapshot taken before every change. | Patch log with dates and versions. |
| Backups | Encrypted, off-site, 30 daily and 12 monthly copies; restore tested quarterly. | Last restore-test date and scope. |
| Monitoring | Uptime, TLS expiry, disk, memory and response time checked every five minutes. | Uptime report for the billing period. |
| Access | Named accounts only, MFA required, least privilege, access reviewed monthly. | Access register and review date. |
| Incident response | Written procedure: contain, assess, notify, fix, review. | Procedure document; incident notice within 24 hours if data is affected. |
| Change control | Every production change has an owner, a reason and a tested rollback. | Change log on request. |
Data handling, in plain terms
01
In-region data
Client data stays on infrastructure we control, in the region named in the contract.
02
No AI training on client data
Customer records are never pasted into third-party AI tools. Internal drafting tools run under agreements that exclude training on client data.
03
No card data on our servers
Card data never touches our servers. Payments run through the provider’s hosted page.
04
Agreed retention
Retention is agreed in the contract; deletion is logged and confirmed in writing.
Government and enterprise requirements
Public-sector buyers usually need more than a promise. We prepare the file that procurement asks for: data-residency statement, subprocessor list, access-control matrix, backup and restore evidence, incident history, insurance certificate, and a security schedule attached to the contract. Where a jurisdiction requires in-region hosting, the region is written into the agreement and shown in the control panel.
Reporting a vulnerability
Send details to the address in /.well-known/security.txt. We acknowledge within one business day, tell you what we found, and credit you if you want the credit. We do not pursue researchers who act in good faith and stop at proof of concept.
What we will not do
| Control | What it means | Evidence |
|---|---|---|
| No security theatre | Every claim on this page is verifiable | securityheaders.com, TLS checker |
| No untested backups | Restore tested quarterly, date recorded | Last restore date |
| No hidden incidents | Client notified within 24 hours if data affected | Incident procedure |
| No credential sprawl | Named accounts, MFA, least privilege, monthly review | Access register |
Want the file, not the paragraph?
Ask for the evidence pack. It is the same document we give procurement, with the dates and signatures filled in.