No cookies, no cookie banner, no consent dialogs. Privacy features ship on every plan. Nothing behind a paywall.
Your data lives in a Belgian datacenter, is never replicated or processed outside the EU, and is never sold. Full stop.
Export to CSV, JSON or Parquet at any time. Cancel at any time. No lock-in, no exit fee.
Limits are limits. When you reach your monthly event cap, we stop collecting new events until you upgrade or your next billing period begins. Existing data and dashboards stay fully available.
No overage fees, no automatic upgrades, no hidden costs. You know what you pay, and what you get — in advance.
30 days free. No credit card required. No automatic renewal.
A 30-minute walkthrough of the platform — multi-brand dashboards, the cookieless model, and how sovereignty works in practice. No slides unless you ask for them.
By submitting you agree to our privacy policy. We never share your details — and there's nobody to share them with.
We'll reply within one business day. In the meantime, your message is sitting safely on a Belgian server.
Privacy, engineering, and product writing from the team building analytics that forget.
Most analytics tools bolt privacy on at the end. We started from the opposite premise: what if the system was incapable of identifying anyone in the first place?
There's a familiar shape to most analytics products. They collect everything they can — a persistent identifier in a cookie, a fingerprint, a cross-site profile — and then, once regulation catches up, they add a consent banner and a data-processing addendum and call it privacy. The data model never changed. Only the paperwork did.
We wanted to invert that. Not "collect, then ask forgiveness," but a system that simply cannot reconstruct who a visitor is, by construction. If the identity doesn't survive the day, there's nothing to leak, nothing to subpoena, and nothing to sell.
When an event arrives, we derive a visitor identifier on the server — never in the browser, never written to a cookie. It's a salted hash of four things: a secret salt that rotates every 24 hours, the domain, the raw IP, and the user-agent string.
The raw IP is used in memory for two things only — a country/region lookup and the hash above — and is never written to disk. When the salt rotates at midnight, the previous day's salt is gone. There is no key anywhere that could turn yesterday's visitor_id back into a person. The math doesn't allow it.
The safest data is the data you never stored. The second safest is the data you can no longer read.
You might wonder how you get sessions, bounce rate, or engaged time out of an identifier that resets daily. The answer is that almost everything useful in analytics is aggregate. A session is simply events sharing a visitor_id within a 30-minute window — derived server-side, never tracked across sites or days. You lose the ability to follow one human around forever. You keep the ability to understand how your product is actually used.
This is the trade we think is worth making, and the one we named the company after. Trace plus era: a signal that's read, counted, and then belongs to a moment that has passed. The logo is the same idea — a line that rises into a peak and resolves into a single live node, drawn and then gone.
Because the model is cookieless and stores no personal data, there's a strong, well-documented argument that no consent banner is required for the baseline measurement — the same legal footing pioneered by privacy-first tools before us. But the deeper point is commercial, not legal: when you sell sovereignty to your own customers, your analytics can't quietly ship their behaviour to a third continent. The tool has to embody the promise.
That's why every privacy feature is on every plan, including the cheapest one. It isn't an upsell. It's the foundation the rest of the product is built on — multi-tenant, multi-brand, EU-hosted, and yours to export or delete at any time.