Ideate about tracking

This issue only about designing/debating a solution. For the actual implementation, new issues can be created.

In order to improve the application, some behavior tracking might be useful. This would include things like:

• acquisition sources
• time spent on site
• number of visitors (search engines excluded)
• activity on the site (events)

The following requirements should be met:

• For users who are not logged in, cookies should not be used and the tracking should be anonymous
• Any privacy-protection tool or browser setting that is useful for the users should be supported
• For logged in users, any data recording that is not necessary should be optional, but cookies can obviously not be avoided in this case
• The project doesn't have any stable founding right now, and I also want to minimize any costs, so a solution that would cost (a lot) of money will probably be discarded

We might also create a completely separate deployment for a separate version that has all the tracking features removed from the binary code. This might be achievable with a build tool, maybe there's a webpack plugin that let's you mock files/dependencies with a something that doesn't actually do anything. This might be overkill though, since this isn't exactly the most privacy-sensitive app ever made :smile_cat:

It might be also nice if some aggregated/anonymized data could be released publicly, so that data analysts could analyze it.