Privacy

If you are reading this because a site you visited uses nitur, this is the whole of what was recorded about that visit:

• the path you opened, with the query string and fragment removed
• the domain that referred you, or direct — never the full referring URL
• a browser family, operating system and device class, each reduced to one of a handful of values with version numbers discarded
• a two-letter country code, supplied by the hosting network
• the time the page was opened
• a daily visitor code, explained below

To report how many people visited rather than how many pages were loaded, each view carries a code derived like this:

hash(daily secret + site + your IP address + your browser’s User-Agent)

The address and User-Agent are used to compute that code and then discarded. Neither is stored.

The daily secret is destroyed every day. While it exists, views from the same person on the same site can be grouped for that day — which is what makes a visitor count and a bounce rate possible at all. Once it is gone the code cannot be recomputed from any address, and because the next day uses a different secret, the same person is a different code tomorrow. Nothing links a visitor across two days, by construction rather than by policy.

Worth stating plainly: this is weaker than storing no identifier at all, which is what this service did previously. It is the same approach other cookieless analytics use, and it is what allows the counts people actually expect. What it is not is a profile — the code is meaningless the day after it is made, and there is nothing to join it to.

• No cookies. The tracking script sets nothing in your browser, and reads nothing from it. There is no consent banner because there is nothing to consent to.
• No local or session storage, and no other client-side state.
• No IP address. The country comes from a header the hosting network adds. The address itself is never written to storage or to logs. It is read once, in memory, to enforce rate limits — hashed with a key that is regenerated on every restart and never saved, so it cannot be reversed or matched to anything.
• No fingerprinting. No canvas, fonts, screen dimensions, hardware details, or timing signals. The raw User-Agent string is discarded after being reduced to the coarse categories above.
• No persistent or cross-site identifier. The daily code above is scoped to one site and one day; it cannot follow you between sites, or between today and tomorrow.
• No query strings or campaign tags. Anything after ? is stripped before storage, so tracking parameters and anything accidentally placed in a URL never arrive.

These are properties of the code, not promises about intent. There is no setting that turns any of them on.

A site can record that something happened — a signup, a purchase — and attach its own details, called properties. A property might be plan: pro.

Properties are stored exactly as the site sends them. They are not inspected, filtered or anonymised on the way in. If a site puts something personal in one, that is what gets stored. This service warns the site’s owner in their dashboard when a property looks like an email address, a phone number or an identifier, but that check is a safety net and not a guarantee.

Events carry the same coarse context as a page view and the same daily code. They cannot be assembled into a journey: linking one person’s actions in sequence would need an identity that outlives the day, and none exists. Counts and rates are possible; funnels are not.

The script checks Do Not Track and Global Privacy Control before doing anything, and sends nothing at all when either is set.

Account holders are a different matter, because an account has to identify someone. If you sign in, we store the email address and name your identity provider gives us, plus the sites you create.

We never see a password. Sign-in goes through GitHub or Google, and only the resulting confirmation reaches us.

One cookie is set: a session cookie that keeps you signed in. It is httpOnly, so scripts running in the page cannot read it. It is the only cookie this service sets anywhere, and it is never set for visitors of tracked sites.

From your account page you can download everything associated with your account as a single file, or delete your account outright. Deletion removes your account, your sites, and all collected page views immediately and permanently. There is no recovery window and we keep no copy.

Data is stored in a PocketBase database on Fly.io in Frankfurt, used by nothing but this application. The application itself runs on Vercel. Both process data solely to operate the service.

Nothing is sold, shared, or used for advertising. There are no third-party analytics, trackers, or advertising scripts on this site — the only measurement running here is nitur itself.

Questions, or a request about your data: shakedamar@gmail.com.