Pirsch: privacy-friendly, cookie-free web analytics
Pirsch is a web analytics option built around privacy rather than browser tracking.
It aims to show how people move through a website while avoiding cookies and personal-data storage, using a server-side, open-source approach.
How cookie-free tracking works
Pirsch is positioned for site owners who want visitor insight without relying on cookie-based tracking. Instead of storing a cookie in the browser, it builds a unique fingerprint for each visitor from four inputs: the IP address, the User-Agent string, the date, and a salt. That fingerprint lets the tool recognise the same visitor across pages on the same site, while the design avoids storing personal information.
For a landing page or blog, that means you can still answer practical questions — which pages are visited, how traffic flows, and whether visitors return — without asking visitors to accept tracking cookies first. The trade-off to check is fingerprint stability: because the date is part of the fingerprint, recognition is naturally time-bound, so confirm how that affects return-visitor reporting for your reporting window.
Drop-in, server-side and open source
Three implementation traits define the tool: it is drop-in, so it can be added to an existing site without a rebuild; server-side, so measurement happens on the server rather than depending only on browser scripts; and open-source, so the codebase can be inspected and, where suitable, self-hosted. That combination suits privacy-conscious teams, developers who prefer auditable code, and publishers who want analytics that does not depend on third-party trackers.
Decision checklist
Use this checklist before choosing Pirsch for a landing page or blog:
- Confirm you do not need cookie-based cross-session identity beyond the daily fingerprint window.
- Check that server-side deployment fits your hosting and maintenance capacity.
- Verify current paid-plan pricing and free-trial terms, which were listed as paid with a free trial.
- Test fingerprint behaviour on your own traffic, including shared IPs and privacy browsers, before relying on return-visitor counts.
- Review how the salt is managed, since it is part of the fingerprint inputs.
| Area | What Pirsch offers | Check before adopting |
|---|---|---|
| Tracking method | Visitor fingerprint from IP address, User-Agent, date and salt | How the date component affects return-visitor windows |
| Cookies and personal data | Cookie-free; no personal information stored | Fingerprint behaviour with shared IPs and privacy browsers |
| Deployment | Drop-in, server-side and open-source | Hosting and salt-management requirements |
| Pricing model listed | Paid, with a free trial | Current plan prices and trial terms |
Based on captured listing evidence; confirm current product details before purchase.
Frequently asked questions
How does Pirsch recognise returning visitors without cookies?
It creates a per-visitor fingerprint from the IP address, User-Agent, date and a salt, then uses that fingerprint to count and follow visits across the site without setting cookies or keeping personal information.
Is Pirsch open source and server-side?
Yes. It is described as a drop-in, server-side and open-source setup, which suits teams that want analytics code they can inspect or self-host rather than a closed hosted-only tool.
What pricing model is listed for Pirsch?
The listing shows paid pricing with a free trial. Check the current plan details on the product site before budgeting, as prices and trial terms can change.