Our data

We’re building software.
Not a dossier on you.

Some data makes the product work. Some powers the analytics our customers use. Some helps us find what’s broken. Here’s what those jobs involve, across our brands.

A visual inventory, based on the product code and published policies. The activity below is illustrative — no live visitors, customer records or payment details are shown.

Illustration · not a live feed

A signal, without a biography.

An illustrative page view, link click or error. The reference here changes for the animation; actual retention and identifiers differ by product. Customer analytics are stored to produce the reports described above.

Small cupboards. Clear labels.

“Anonymous” should mean something. A random-looking ID can still link activity together. So we distinguish anonymous counts, pseudonymous visitor records, and information tied to an account. We also distinguish data on your device from data held by us or a service provider.

Payments need records. Support needs a conversation. Email software needs your email. Our job is to make those purposes clear, keep the scope sensible, and keep questioning what we actually need.

Why we build this way