I currently limit its use to an account on my computer that doesn't do the things where I care as much about security (and limit JS use), and the pledge/unveil

I currently limit its use to an account on my computer that doesn't do the things where I care as much about security (and limit JS use), and the pledge/unveil OBSD stuff prevent it from reading or writing in directories not explicitly named as allowed. Still, you make a good point and I plan to think about it. Maybe the question is which is more risk: a local and limited compromise to a low-privilege account on OBSD, or sharing more info with Google (sounds like Google is the lower risk maybe -- hard to say...). (On the other hand, it is becoming easier to upgrade packages on OBSD between releases and so if Iridium started releasing more often it could take advantage of that--but that is just speculative.)