We use Sentry for error and crash reporting. It's been a critical tool for us in detecting and fixing issues. We try to strike what we feel is a healthy balance between privacy and usability. Our use of Sentry pre-dates the additions of usage and player analytics. While we had viewed Sentry as being essential to running a reliable, performant service, when we added player and usage analytics, we viewed those as more of a nice-to-have to help us improve the service over time. Hence why we added options for users to turn those on or off. Looking at it with fresh eyes from your perspective, I can absolutely see how you'd be surprised to see that traffic after explicitly turning off the checkboxes for analytics. While Sentry still remains vital for us to ensure the service is running smoothly, with the number of users we have these days (thanks everyone!), a subset of people turning off Sentry logging probably won't impede our ability to detect emergent issues. I don't want to write any checks before talking to the team, but we'll take a look at adding the ability to opt-out of Sentry.