“Cookieless” means the tracker does not use a browser cookie for visitor recognition. It does not mean that no data is collected, that every visit is anonymous, or that a server cannot derive a pseudonymous identifier.
What cookieless collection can support
It can support pageviews, referrers, campaign tags, coarse technology and geography, goals, events, performance metrics and aggregate timing. A short-lived or pseudonymous session estimate can help explain a funnel when its limitations are shown.
What the label cannot prove
It cannot prove that observations are unlinkable. Nanolytica's current per-site salt can link the same input across days, while shared networks and changing addresses can merge or split estimates. Read the identifiers section of the architecture page.
A responsible setup
- Honor Do Not Track and provide a clear opt-out where your deployment needs one.
- Keep query strings, credentials and personal values out of paths, campaign fields and custom properties.
- Use a retention window and aggregate views that reduce the risk of tiny cohorts.
- Explain public sharing and account cookies separately from visitor measurement.
For a SaaS-specific metric plan, see analytics for SaaS. For a direct product comparison, see Nanolytica vs Plausible.