Am I overthinking this as a 1Password security fail, or is this not really an issue?

[dImpetus]

Recently, I got a new Android Pixel phone and used the cloud backup to install my apps while setting up. Once they were all downloaded, the first one I would need to set up and login would be 1password. I had pulled my secret key to set up the application, but there was no need because the Google cloud backup had it. All I had to do was put in my password. I thought that I must have misconfigured the application to allow the key to back up. Still, there are no settings to opt out of having a third party have a copy of my supposedly private secret key, at least to what is implied in their homepage FAQs and other marketing material. This seems like a massive concession of security for convenience.
From looking at it, this also seems to be how it is handled on iOS as well.

As per 1Password documentation

Encrypted copies of your Secret Key are stored in your device backups and keychains to provide data loss protection. If you have iCloud Keychain turned on and lose your Mac, iPhone, or iPad, you can restore from a backup and unlock 1Password with just your account password. It’s the same for Android backups.

 

[PHolder]

Well, I presume the software needs the key to operate at all, so unless you're supplying it every time you want to run it, it must be keeping a copy in the phone right? If it's secure on the device, then it should be about as secure in a backup if the backup is protected in the same way as the data on your phone. Which presumably requires a password which you either supply to unlock the phone, or is stored in the phones secure enclave, and unlocked via your face, fingerprint or unlock PIN. Ideally the software would be more clear about this topic in it's documentation, and I guess it could warn you that it is subject to the backup features of the OS, which it presumably can't exactly override.