Privacy-Friendly Analytics and GDPR

TinyAnalytics makes core anonymous analytics privacy-friendly by default. It sets no analytics cookies, stores no raw IP addresses, and counts anonymous visitors with a server-derived one-way identifier instead of a browser ID.

​

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 — the default — sets no cookies and does not persist an anonymous analytics ID in the browser, so in most jurisdictions anonymous measurement alone needs no banner. Identified mode is different: the moment you call identify(), the user ID and traits you send are personal data, you act as the data controller for them, and you owe your users a lawful basis — typically consent. The consent-exempt audience-measurement carve-out some jurisdictions allow does not cover cross-referencing identified customer data. 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.

​

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