A measurement company, and nothing else.

01

The word

02

Why Kehai exists

Analytics spent two decades collecting the person in order to count the presence. Consent banners, stored identifiers, sampled reports, modeled numbers dressed as counts: all of it follows from one decision, that the visitor must be known.

Kehai starts from the opposite decision, and the name is the standard every feature answers to. Count what happened, keep the row behind every number, and let the person stay unseen, where they were standing anyway. The tracker sets no cookie, visitor codes start fresh every UTC day, and a forecast never sits in a counted column. The counting rules are public.

It was built for a business or an agency in the European Union that already runs another analytics product and cannot answer a concrete question from its reports: why the store's revenue and the report's revenue disagree, how many of last month's visits were bots, what happened to the campaign the numbers say nobody clicked. Kehai is written so that the answer is on the screen, with the rule that produced it beside it.

03

How it's run

• Warsaw, Poland, EU jurisdiction. The service runs on rented hardware in Warsaw, managed by us rather than by a hyperscaler in another legal system. Backups sit in an OVHcloud bucket in the same city, Cloudflare fronts public requests, and the subprocessor list names every party that sees anything.
• Funded by subscriptions. No investors and no ad model, so nothing about your visitors is worth more to Kehai than the subscription is. Four self-serve plans and one quoted offer, on the same page as the product.
• One person, named. The tracker, the panel, the documentation, and the support inbox are the same person's work, and the data processing agreement is signed by name.
• Said plainly, including what is missing. There is no SOC 2 report, no ISO 27001 certificate, and no third-party penetration test yet. The security page says so, because a buyer's risk assessment needs that sentence more than it needs a badge.
• Narrow on purpose. One product, self-serve plans, and a scope the company can hold to a standard rather than to a roadmap.

Each of these is stated at length where it can be checked: the subprocessor list, the data processing agreement, the security page, and the plans.

04

Where it came from

Kehai is young and says so. These are the dates.

• August 14, 2026First commit. The measurement contract, the tracker's byte budget, and the rule that a modeled number never sits in a counted column were written before the first report.
• August 29, 2026Billing live in Stripe. The first press kit and the brand page published the same day.
• September 10, 2026kehai.io public, with the documentation, the legal pages, and the demo account.
• September 15, 2026Launch: the WordPress and PrestaShop packages, the film, and the first paid search campaigns, in the same week.

05

Who signs

Mikołaj Salecki builds and runs Kehai through salecki.digital, a one-person studio near Warsaw, and wrote the tracker, the panel, and the documentation. The support address reaches the same person.

Questions about the product, the data, or the contract go to hello@kehai.io, and the reply comes from the person who wrote the code. Operator plans start with a conversation rather than a form; the contact page describes how that goes.

salecki.digital Mikołaj Salecki
ul. Gen. Jasińskiego 11/51, 05-500 Piaseczno, Poland
NIP 1231052003 · EU VAT PL1231052003 · REGON 361948200

06

Writing about Kehai?

This page is the company. The facts, the sentences, the pictures, and the press kit are on the press page. The mark, the logo files, and the rules for using them are on the brand page. Quote the material as written; for anything it does not answer, write to us.