Analytics that respect your users.

A few years ago I was part of a digital team at a large public health services organisation. We wanted to understand how people were actually using our services — which flows worked, where they dropped off, what to improve.

Simple question. We couldn't answer it.

Every analytics tool we evaluated collected more than we were legally allowed to store. We were bound by strict healthcare data regulations. Consent banners were off the table. Most tools fingerprinted users or stored IP addresses by default. The team went back and forth for months.

In the end, we built our own solution. It worked, but it wasn't the right answer — we didn't want to build and host an analytics service ourselves, we just wanted to use a good one. A good one didn't exist.

That stayed with me. The insights we needed weren't complicated — page views, user flows, where people got lost. Nothing that required identifying anyone. But nothing on the market was built that way. Privacy was always an afterthought, a checkbox, not the foundation.

So I built Inslo.

No cookies. No fingerprinting. No personal data collected — ever. Just the aggregate insights your team actually needs, in a form that works even in sectors with the strictest data laws. If a healthcare team can use it without a legal review, it's doing its job.