Privacy by architecture, not by policy
GDPR-compliant analytics with no cookies, no fingerprinting and no stored IP addresses. Visitor IDs and the key they were made with are permanently deleted every night.
What Privatrak derives identifies no one.
Other tools promise privacy through policy. We build it into the architecture: session IDs are derived server-side from a one-way hash whose key is random and deleted every night, raw visitor metadata is never stored, and once a day is counted nothing is left that points to a person.*
Visitor data lifecycle
Server-derived hash per day
Stored for 24 hours
Pre-aggregated summaries
Permanently removed
Visitor data is permanently deleted every 24 hours
* Custom event attributes are the one exception. They are stored exactly as you send them, so keep your own user IDs out of them.
Only anonymous interactions. Nothing personal.
Privatrak captures the minimum data needed for product analytics, and nothing that could identify an individual.
Auto-Captured Events
Pageviews, clicks, and form submissions are captured automatically. No manual instrumentation needed.
No Personal Data Stored
No names, emails, or device fingerprints are ever stored. IP addresses and User-Agents are used only in memory to derive session hashes, then immediately discarded.
Form Metadata Only
Form submissions are tracked with metadata only: the form's tag and selector. No field values, no input contents, no text entries.
Form submissions are tracked by metadata only. No field values are ever captured.
Compliant by architecture, not by checkbox.
No cookies, nothing stored on your visitors' devices, no IP addresses kept. Privatrak is built for GDPR, CCPA and ePrivacy from the ground up, so you can measure your product without consent banners, cookie popups or privacy policy rewrites.
GDPR Compliant
Visitor IDs come from a one-way hash with a random daily key that is deleted every night. IP addresses and User-Agents are never stored.
CCPA Compliant
No sale or sharing of personal information. No opt-out mechanism required because there's nothing to opt out of.
ePrivacy / Cookie Law
Zero cookies, zero localStorage, zero browser storage of any kind. Nothing is stored on your visitors' devices, so there is nothing there to ask consent for.
No consent banner needed. No cookie popup. No complex privacy policy changes.
Your data pipeline, fully transparent.
From script to dashboard, every step is designed to minimize data and maximize privacy. Here's exactly what happens.
Data Architecture
Frequently Asked Questions
Everything you need to know about privacy and data handling in Privatrak.
No. Privatrak uses zero cookies, zero localStorage and zero browser storage. Visitors are identified only by an irreversible hash the server works out and throws away every night.
Yes. Privatrak relies on legitimate interest under GDPR Art. 6(1)(f) instead of consent, and is built so that this holds: nothing is stored on your visitors' devices, no IP address is ever saved, and the day's visitor IDs and their key are deleted every night. That is why it runs without a cookie banner or consent popup.
The server derives session IDs from visitor metadata using a random key for each day. Raw IP and User-Agent are used only in memory and never stored. Events carry these session IDs until the nightly aggregation, which deletes the IDs together with the day's key. Only the counts remain.
Not from anything Privatrak derives. Session IDs come from a one-way hash with a random key for each day, raw IP and User-Agent are never stored, and the IDs and that day's key are deleted every night, so visits cannot be linked across days, not even by us. The exception is data you send yourself: a stable user ID placed in a custom event attribute is stored as-is, and would make visits linkable.
No. Your analytics data is yours alone. We never sell, share, or provide access to any third party. There are no ad trackers, no data brokers, and no third-party scripts.
Only through data your own site puts there, in two places. Page addresses: a link such as /reset?email=ada@example.com or /users/ada-lovelace carries personal data in the URL. Before an event leaves the browser, Privatrak blanks out the values of parameters such as email, token, key, password and secret, as well as values that look like an email address or an access key, and collapses ID-like parts of a path, and in your project settings you can add your own parameter names and value patterns. Custom events: whatever you pass to tracker.track(), data-track-* attributes or traits is stored exactly as sent, so keep emails, names and account IDs out of them.
We recommend mentioning Privatrak in your privacy policy for full transparency, even though the data processing is minimal and privacy-friendly. If you're unsure about the details, the best advice always comes from a legal professional.
Start measuring what your users actually do
Create an account and watch your first events arrive in minutes.
Free plan, no credit card needed. The demo needs no sign-up.