# I started Inth because privacy should live with the product.

Christopher Burns, Founder, Inth · Author, c15t

## Cookie banners showed me the bigger problem.

I started with [c15t](https://c15t.com) because cookie banners were the part of the problem that everyone could see. 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 bigger problem became obvious. A banner can record a choice, but it cannot tell you whether a new SDK, vendor or AI feature made your privacy policy untrue.

Inth is what we are building around that problem. It follows each change from pull request to production. It keeps the people, the reasoning and the outcome with that change, so you can show why your product does what it does.

Christopher

## Privacy evidence should change when the product changes.

Privacy policies and contracts say what a product should do. The code and the live site show what it does. Inth keeps the two from drifting apart.

*Example evidence for one change on acme.shop: a pull request sends email and user ID to LogRocket, a reviewer approves it with email masked, and Website audit sees LogRocket load after opt-in with email masked*

## What Inth does today

- Runs c15t in your app, with a consent policy for each region.
- Answers questions about your product from your evidence, and cites each source.
- Loads your live site like a visitor and shows what runs before consent.
- Finds privacy changes in your code and keeps the decision with the pull request.

## How we build Inth

1. **Put privacy in the product.** Privacy is product behavior. It belongs in the same systems that teams use to build, review, test and run software.
2. **Prefer open infrastructure.** Critical privacy controls must be open to inspection and easy to move. c15t, the library under the Consent banner, is open source under the Apache‑2.0 license.
   [See our open-source projects](/oss)
3. **Follow change, not checklists.** Evidence that keeps up with the product catches a regression in its pull request or the next scheduled audit, not a year later.
4. **Keep human judgment visible.** Software can find changes and collect context. A person still makes the decision, and Inth keeps their reasoning with the change.
5. **Treat performance as trust.** Privacy controls must not slow the product down. In CookieBench, the c15t banner appeared in a median 27 ms.
   CookieBench medians, Next.js desktop.

## The company

- **Legal name:** Consent Management Inc (Inth)
- **Incorporated:** Delaware, United States
- **Customers:** Mainly in the United States, the United Kingdom and the EU
- **IAB TCF:** Registered CMP, ID 490 (web)

[Trust center](/trust) · [Privacy policy](/legals/privacy-policy)