The privacy properties
- No analytics cookies. Core anonymous analytics does not set cookies or write an anonymous analytics ID to the browser.
- No raw IP addresses stored. A visitor’s IP is used only in memory to derive a hashed identifier and an approximate location, then it’s gone — it isn’t kept with your data.
- No cross-site profile. The cookieless identifier is derived for your site, not a stored ID that follows a person across the web.
- No personal data by default. Names, emails, and other identifying details are stored only if you deliberately send them via
identify(), traits, or event properties.
Which features use browser storage?
Optional features use browser storage only when their behavior requires persistence:
These values support a feature on your site; they are not a cross-site advertising profile. They can still matter under laws that regulate non-cookie browser storage, so include them in your consent review when you enable those features.
Do you still need a cookie-consent banner?
Core anonymous analytics sets no cookies and does not persist an anonymous analytics ID in the browser. Whether you need consent still depends on your jurisdiction, the optional features you enable, and the data you choose to send. Review the rules that apply to you and your visitors.This page describes how tinyanalytics works, not legal advice. Your obligations under GDPR, ePrivacy, CCPA, or other regulations depend on your specific use, the data you collect, and where your visitors are. Consult those regulations — or a professional — for your situation.
Keeping data collection privacy-friendly
You decide how much personal data, if any, enters tinyanalytics:- Use a non-identifying ID (like an internal user ID or a hash) with
identify()rather than an email address. - Keep raw personal information out of custom event properties and traits unless you have a reason and a basis to store it.
- If you connect Stripe, leave Email fallback off unless you need it and have a basis for processing customer emails. The email is not stored in the analytics event store, but matching it is still personal-data processing.
- Review the browser storage used by optional features before enabling them.
- Review what your team sends periodically, since properties and traits are free-form.
Related
How cookieless identity works
The mechanism behind privacy-friendly identity.
How your data is handled
Exactly what’s stored and what isn’t.
Identify users
Attach an ID without exposing personal data.
tinyanalytics vs the alternatives
How it compares on privacy and openness.