Use case · GDPR
Analytics built for GDPR.
Pieowl sets no cookies and doesn't store IP addresses. Visitor IDs change every day. Your data is stored in our EU cloud.
- No cookies
- No stored IPs
- EU cloud
- No cookies
- A visitor ID that changes daily
- IP addresses are not stored
- EU cloud
- Consent mode when you need it
The problem
Why analytics creates privacy work
The analytics most teams start with often brings extra privacy work along with it.
- 01
Cookies mean consent questions
Google Analytics sets first-party cookies, such as _ga, to tell visitors apart. Under EU rules, cookies like that usually need consent, which means a banner and a consent setup.
- 02
Data far from your users
Many teams want analytics data stored in a specific region. Not every analytics tool gives you that choice.
- 03
More personal data than you need
Full IP addresses and long-lived IDs are often stored by default. The less you collect, the less you have to protect and explain.
- 04
Hard to answer the auditor
When someone asks what you collect, where it's stored and for how long, the answers are spread across settings and vendor documents.
What you get
How Pieowl keeps analytics data lean
Privacy choices built into how Pieowl works, not added on top.
No cookies
The tracker never sets a cookie and stores nothing on your visitors' devices.
A visitor ID that changes daily
Anonymous visitors are counted with a hash of browser, IP, site and a secret salt. The salt changes every day, so the same visitor gets a new ID each day.
IP addresses are not stored
The IP is used for the location lookup and the hash, then dropped. The events table has no IP column.
EU cloud
Your data is stored in our EU cloud.
Consent mode when you need it
Where you need consent, start the tracker disabled. Events wait in memory and are sent only when you call ready. Session replay waits for allowReplay.
Session replay with text always hidden
Replay is opt-in. When it's on, all text and form fields are always hidden, and you can block any element.
Export one person's events
The export API can filter raw events by profile ID, which helps when someone asks for a copy of their data.
Why Pieowl
Why privacy-minded teams pick Pieowl
Less personal data, a clear answer to where it lives, and analytics that still go deep.
Simple answers to privacy questions
No cookies, no stored IPs, a daily-changing visitor ID, and data stored in the EU. Each answer fits in one line.
Often no cookie banner for analytics
Pieowl sets no cookies, so in many cases you don't need a consent banner just for Pieowl analytics.
Depth without extra data
Funnels, retention, cohorts, revenue and replay run on events, not on cross-site tracking. You get product answers without collecting more than you need.
FAQ
Frequently asked questions about GDPR-friendly analytics
Common questions from founders, developers and privacy teams looking at Pieowl.
Do I need a cookie banner with Pieowl?
Often not for analytics. Pieowl sets no cookies and stores nothing on your visitors' devices, so in many cases you don't need a consent banner for it. It depends on your country and the features you use: session replay needs consent, and some countries, like Germany, Poland and Ireland, have no exemption for analytics. Our docs page "Do you need a cookie banner?" has the details. If you add other tools that set cookies, like ad pixels, those may need consent too.
Is Pieowl GDPR compliant?
Pieowl is built for GDPR: no cookies, no stored IP addresses and a visitor ID that changes daily. Compliance also depends on how you use it, for example what you send when you identify users. Check your setup with your privacy lead or lawyer.
Where is my data stored?
In our EU cloud.
What does Pieowl collect about a visitor?
The events you send, with page, referrer, campaign, browser, operating system, device type and an approximate location. The IP address is used for the location lookup and the visitor hash, and is not stored.
Can I wait for consent before tracking?
Yes. Start the tracker disabled and events wait in memory. When the visitor agrees, call ready and the queued events are sent. If they don't, nothing is sent. For session replay, keep "Record only after visitors agree" on and call allowReplay when they agree.
How do I handle a request for someone's data?
If you identify users, the export API can return the raw events for one profile ID. That helps with access requests. There's no self-serve tool to delete one person's events yet, so for deletion requests contact hello@pieowl.com.
How does Pieowl compare to Plausible and Matomo?
All three can run without cookies. Plausible is simple and EU-hosted, but it points people who need replay, cohorts or retention to other tools. Matomo offers cookieless tracking and a free self-hosted version. Pieowl adds funnels, retention, cohorts, replay, revenue and an MCP server for your AI assistant. It runs only in our EU cloud and has no self-hosted version. Checked October 2026.
Does Pieowl have SOC 2 or ISO certification?
No, not today.
Keep reading
Your first dashboard in five minutes.
14-day free trial, no card needed. Then from $9 a month for 10K events.