Skip to main contentI started Inth because privacy should live with the product.
Policies and contracts say what a product should do. The codebase and production show what it does. Inth keeps those two things from drifting apart.
- Christopher Burns
- Founder, Inth · Author, c15t
Christopher Burns
Cookie banners showed us the bigger problem.
I started with c15t because cookie banners were the most visible part of a broken system. Developers were loading a blocking third-party script into their product, then handing control of the experience to a dashboard they did not own.
Once c15t lived inside the application, the larger gap became obvious. A banner can record a choice, but it cannot tell you whether a new SDK, vendor or AI feature made your policy untrue.
Inth is what we are building around that gap. It follows change from pull request to production and keeps the people, reasoning and outcome attached.
The privacy record should change when the product changes.
Code shows what the product intends to do. Production shows what happened. Inth keeps the decision and review with the change.
Code shows intent
Controls, policy logic, consent state, and data handling should be versioned and reviewed beside the product they govern.
Production shows behaviour
Runtime behavior shows whether scripts, vendors, domains, and data flows still match the intent expressed in the codebase.
People make the call
The source, reviewer, rationale, fix, and verification become one durable product record instead of scattered paperwork.
Principles for how we build Inth
Put privacy in the product
Privacy is product behavior. It belongs in the same systems teams use to build, review, test, and operate software.
Prefer open infrastructure
Critical controls should be inspectable and portable. Open foundations create more trust than opaque scripts and locked dashboards.
Follow change, not checklists
A current product record is more useful than a periodic reconstruction. Start from what changed and keep the evidence with it.
Keep human judgment visible
Systems can find changes and assemble context. People still make the decision, and their reasoning should remain reviewable.
Treat performance as trust
Privacy controls should not punish the user experience. Infrastructure earns adoption when developers are proud to ship it.