The choice to enable auto-updates is prominently present to users on onboarding. So while default off, it is one click away from being turned on for every new u

The choice to enable auto-updates is prominently present to users on onboarding. So while default off, it is one click away from being turned on for every new user using Orion. Also there is a question of the real risk. WebKit and macOS are generally very secure. We had to intervene only once in the last 4 years with a (medium) security related WebKit update (and we shipped it a week sooner than Apple did with Safari). We believe that the two facts highlighted above minimize any security risk. On the other hand every telemetry, including auto-update pings, sends personal information (at the very least user's IP address) to the browser vendor. Almost every other browser on the market is ad-supported (directly or indirectly). Telemetry and ad-supported businesses can be a problem. We do believe that browsers do not have the right to do this (at least if they want to call themselves privacy-respecting). In our view it should be on users to decide if they want to trust the browser (browsers are "user agent" after all) and every telemetry, including this, should be opt-in. Simply put, if a browser is not zero-telemetry it can not be called privacy respecting, and any browser using telemetry by default should at least disclose it to users on the first run.