Measurement and privacy
Pluraterra measures aggregate site use to improve its data, accessibility and reliability. These application metrics do not retain raw IP addresses, full user-agent strings, URL query strings, full referring URLs, search text, household-cost inputs or raw browser session IDs.
Browser measurements
A random identifier in sessionStorage recognises a browser tab across page loads. On the server, a day-scoped HMAC deduplicates daily tab-session counts. These counts are not unique people: a person can use several tabs or devices, and a tab can be counted again on another day. We count pageviews, broad referral categories, download clicks, source-link clicks and tool changes. We do not transmit values entered into controls.
Browser measurement skips declared automation and respects browser Do Not Track and Global Privacy Control signals. Ad blockers, disabled JavaScript or storage restrictions can also prevent measurement. The opt-out below stops this browser’s future measurement events; it does not disable aggregate HTTP operational counts.
Requests and identifiable crawlers
Server metrics count HTTP outcomes, API access and declared crawler identities. A source IP is used transiently for rate limiting and checking an identity against a provider’s published ranges, then discarded from the application metrics. A user-agent claim alone is unverified. Crawler requests are not proof that a model cited us or used our data in an answer.
Retention and access
When Postgres storage is configured, aggregate metrics and day-scoped session hashes have a 90-day retention window. Without it, counters are explicitly limited to the current process and reset on restart. A bounded flush queue can lose recent counts during a crash. The owner dashboard requires a private access token; it is not public visitor data.
Heroku may separately maintain platform operational logs under its own policies. This description concerns Pluraterra’s application measurement, not a promise that every intermediary keeps no logs. No advertising analytics or cross-site identity service is used.