Security

Security is part
of every build.

A useful system needs clear permissions, failures you can see and people who know what they own. We set those boundaries as part of the build.

Access follows the job

Each workflow gets only the accounts, data and actions it needs. Reading data and changing it are separate decisions. Publishing, changing a budget or anything else with consequences needs an agreed point where a person approves.

Make failures understandable

When data is missing, a permission has expired or a check fails, the system should stop or send the work for review, and say why. We agree how someone on your side can look at a run, fix the problem and start again safely.

Protect the public website

This website is made of pre-built pages, fonts served from our own domain and optimised images. It does not run AI for visitors and it never asks you for account passwords. When the enquiry form is switched on, submissions are checked on the server and need a completed security check.

Found a security problem?

Email dylan@compoundlab.ai with the page address, what you found and how to reproduce it safely. Please do not access other people's information, interrupt the service or include secrets in your report.

Every project is agreed separately

How data is handled, how long it is kept, who owns access and what support you get are agreed for each piece of work. This page is an overview. It is not a certification, a service-level agreement or a promise that any system is free of risk.

Read the privacy policy or see how we work.