PostHog. Google Analytics. Databuddy, One event call. @c15tdev 3.1 gives you useEventDispatcher() to send events across your supported, configured analytics integrations, with consent checks built in. inth.com/blog/c15t-3-1

A customer thought the new c15t.com had two cookie banners. Apparently our demo was a little too convincing. So we gave it a badge.

Introducing c15t v3 The open standard for cookie banners ✦ Set up c15t in my app: c15t.com/SKILL.md → Open source → 8 frameworks and a script tag → Banner in the server HTML → 34 policy presets, GPC and GPP built in

Your startup could be one privacy mistake away from a $10,000 CIPA demand letter. It’s coming. Will you be ready before it lands?

12 days since we launched the @Inth I always wanted to build. On the day we filmed the launch video, @willde_ath and I had a little chat...

We're opening early access to the new @Inth before our public launch. we'll run a free privacy scan of your codebase and website if you're in engineering, legal, or growth at a fast growing or enterprise company, plus give you a big discount on any paid features. The goal is to help you catch privacy gaps in your product before they delay launches or harm customer trust. We're already working with some great teams and have room for a few more. Interested? Comment or DM me.

YC’s latest RFS calls for AI-Native Compliance Infrastructure. For us at @Inth, we know privacy has always lived in the codebase. The problem is that most privacy platforms have never treated it that way. Point-in-time scans and surface-level checks miss the gaps that actually ship in PRs. We’re building privacy assurance and governance that's continuous, lives in the codebase, and AI-native. We’re unveiling new Inth tooling next week that tackles exactly this.

Demo Day is in 7 days at @ycombinator. Quick recap since we joined YC: - ran our first Launch Week - rebranded the company to @Inth - c15t crossed 3M npm downloads - hit 912k npm downloads in May - grew 46.4% month over month - served 32.4M hosted consent sessions in May - passed 2,600 public sites detected by Wappalyzer - teams like Zed, Cal, Parabola, Unkey, Infisical, Kernel, and others are using c15t - started converting open-source usage into hosted revenue - opened platform conversations with major AI app builders, frameworks, and commerce platforms - started the first design partner work for what comes after c15t: agents that inspect codebases for privacy and compliance issues - got much clearer on the wedge: c15t earns trust with developers, then we expand from consent into the codebase The bigger thing we learned: Code is moving faster and faster. Teams can barely inspect it for bugs now, let alone keep it up to date with compliance. So we’re building Inth for the place compliance now has to live: inside the codebase. Still feels like the beginning.

Most teams add consent at the very end of a launch. By then, it’s already fighting with performance and UX. With @c15tdev and @Inth we bring consent into code and back it with managed infrastructure, so it ships with your app instead of after it.