You are clearly not the ideal customer profile.. my guess is that the Fig team are going after corporate developers who won’t be as concerned about privacy so much as they are concerned about convenience and productivity.
Even still, your purported "corporate developers" would probably be more interested in privacy than your typical client, considering that corporations literally pay tens of thousands of dollars for proprietary tools like this, just so they have someone to hold liable if it breaks.
In either case, privacy is not a choice when you're working this low on the stack. You need to be operating with the lowest possible performance and telemetry options, or else you start to compromise the value proposition of your product. I wouldn't be surprised if this comment section acts as a good wake-up call to the core development team to switch their priorities, because developers don't agree with their current paradigm.
I haven't looked into how this works, but if it's sending keystrokes or command lines to the cloud (one of the founders is here, please do correct me if I'm wrong!), it has no chance of being used in your average corporate environment.
Any tool that is sending any information to the cloud is DOA for our org.