Website analytics
We use Umami Cloud to understand aggregate website usage, such as page views and referral sources. Analytics collection is separate from account authentication and cloud synchronization.
What the analytics service processes
Standard analytics requests can include the requested page URL, page title, referring page, browser language, screen dimensions, website identifier, and technical request information. Umami may process a visitor IP address and browser User-Agent to produce an anonymous session identifier and approximate location. According to Umami’s documentation, the IP address is not stored as a field in the standard analytics session record, although infrastructure or security logs may involve separate processing.
Safeguards configured for TrafficBlueprint
- Production-only measurement: the tracker is restricted to traffic-blueprint.netlify.app.
- URL fragments excluded: content after #, including encoded read-only campaign snapshots, is removed before analytics reporting.
- Search strings excluded: URL query parameters are removed before analytics reporting.
- Do Not Track respected: the tracker is configured to honor supported browser Do Not Track signals.
- No advertising technology: we do not use advertising pixels, session recording, or analytics form-content capture on TrafficBlueprint.
Ordinary page paths can still contain non-descriptive route identifiers. We currently use standard page-view and referral measurement rather than custom events containing campaign names, offer details, or workspace form values. Cookie-free measurement does not necessarily mean that no personal data is processed under every legal definition.
For more information, see Umami’s metric definitions and Umami’s Privacy Policy.