Great question, the following measures have been implemented:
- The product respects the browser's Do Not Track setting.
- The beacon (which captures all analytics events) can be used with your own custom domain (proxied) to prevent add-blockers altogether.
This is something we considered but ultimately decided against. The cost (time, money and focus) that comes with patching, supporting and maintaining multiple version of our backend/infrastructure is not worth it at this stage of the product. We understand that this will be a turn-off for a big chunk of the enterprise market, we're OK with that.
Great question, the following measures have been implemented:
- The product respects the browser's Do Not Track setting. - The beacon (which captures all analytics events) can be used with your own custom domain (proxied) to prevent add-blockers altogether.