Privacy
PulseMetrics was built to count what happens in an app without learning who did it. This page says exactly what that means.
Last updated 21 October 2026
When a site uses the snippet, a visitor leaves three things
- page address
- query string
- token
- name
- phone number
- email address
- health data
- IP address
Stored
- event name
- random browser id
- time of the event
The snippet sends a short fixed event name that the site's owner chose in their code (for example queue_joined), a random browser id that the snippet makes itself, and the server records the time it arrived. That is the whole record. The browser id is kept in the visitor's browser storage, not in a cookie, and it is not made from anything about the person.
What is never collected
The snippet never reads the page address, the address bar's query string, the referrer, the language or the kind of browser. The server refuses any event that carries anything else, and event names that look like an address, a token, a name, a phone number or an email are refused before anything is saved. This matters because some apps put private links in their addresses; those never reach PulseMetrics.
Every request on the internet carries an address for the reply. PulseMetrics does not store it. It is used in memory for a minute to stop one machine flooding the service, in a scrambled form that cannot be turned back into the address, and it is forgotten when the server restarts.
Do Not Track
A visitor whose browser says Do Not Track, or Global Privacy Control, is not tracked at all: the snippet does nothing, sends nothing, and writes nothing to their browser.
Owners
- An owner's account holds a name, an email address and a password. The password is stored only as a one-way hash, never as text.
- The dashboard sets one cookie, to keep an owner signed in. It sets no cookie on visitors of the sites it measures.
- Sign-in does not keep the owner's IP address in the database. Repeated failed sign-ins from one address are slowed down using a short-lived count kept in the server's memory.
How long it is kept, and deleting it
- Events older than 180 days are deleted automatically, every day.
- Each site can hold up to 200,000 events; after that, new events are refused until old ones age out.
- An owner can delete a site at any time from the Sites page. That deletes the site and every event it received, immediately and for good.
- Deleting an account is not available in this version. Deleting all of an owner's sites removes all of their event data.
Where it lives
The database runs on Neon and the server on Render, both in the Singapore region, and the dashboard on Vercel. Nothing is sold, shared with advertisers, or combined with data from anywhere else.
Questions or concerns: open an issue on the project page. Back to how it is built.
Privacy · No cookies on your visitors. No page addresses stored.