GDPR & PECR
Astrolytics by default doesn't use or collect IP adresses or any personal information about your users. You can see the total list of data we collect on this page.
The only data we store on user devices is a small cache file in case users go offline for the data to be sent later.
That means you are not required by law to ask consent. However, we recommend you to read and follow the practices below.
Whether you need to ask consent to your users before tracking depends on if you plan to report personal identifiable data (with setProps() or setUserId()).
This is in the case where you intend to submit personal identifiable information to our servers (by tying personal data and user ID to events you submit).
Ask before starting the analytics session. We recommend doing that before you even load the modules.
Provide the option to your users to disable/enable tracking as they wish.
Astrolytics' modules support doing that with the enableTracking() and disableTracking() modules.
... or Anonymise
Else, if you still choose to track individual users and report personal data, you should assign them an ID that doesn't allow to identify the original person.
That's why email adresses are bad ideas.
The same goes when tying properties to your users, those should be at the best extent not personal identifiable informations.
In both cases, you should inform your users what data will be collected about them.
If that helps, you can link to our data transparency page that list all the data we collect and store (that doesn't include IP adresses).
To get information about the devices and behavior of our users, we use Astrolytics to provide analytics. This service gives us insight about how users interact with our software. It does not store any personal identifiable information. Visit their transparency page to get the full list of data they collect.