@openplatypus have some good point but I want to clarify what I mean by "privacy first"
User information - By default we do not store or log any user related information. All information that is stored in our DB is general information. We see this as a important privacy for your visitors.
Data - Your data will never be sold or given to a third party. You'll be able to export, import and delete all data related to your projects.
Cookie - We do not use any cookies or localStorage to keep track of your users
--
Their are some big downsides with privacy first since you wont be able to track users over several days (get retention and what not). So I have decided to give my customers the option to do what they want.
If this is an important metric to them they can decide to pass a profileId to the SDK. Then we'll use this ID and will be able to track that users over several days. This is an opt-in feature and thats also why I say "Privacy first".
Privacy means very different things to different people.
On basic level it is just that your data is not used/sold beyond basic, statistical analysis of visitors. That's it. Cookie can be "private" in this context, if they are SameSite and httpOnly with short life.
In terms of law, Privacy is very different thing. In case of GDPR in the EU it is set of rules and laws that you have to comply with.
Just because you don't use cookies or host in EU, doesn't mean you are automatically GDPR compliant.
We built Wide Angle Analytics, and we invested in strict compliance. We hired experienced DPO (one of requeirements), host in EU on EU cloud, not just EU located servers. We document every data processing activity and do not engage in any international data transfer ( in context of GDPR). Plus much more.
Cookieless does not mean privacy. There is lot of snake oil out there.
My understanding is the plausible, unlike GA, doesn't use cookies.
Does that mean web analytics are IP-only?
[edit: Or does it mean no third party sees your analytics?]