Data on Storj is by default end-to-end encrypted with keys only the data owner controls (with optional support for sharing features). Only the data owner can decide who to share the keys with and who can see the data. Put another way, Storj can't access data without the data owner sharing keys and access!
If you're interested in our encryption and security design decisions, there are a lot more details over at https://www.storj.io/disclosures. Glad you're all paying such detailed attention!
Encryption is all well and good, but only when paired with anonymization. It's worth comparing the Storj privacy stance linked above, which describes numerous ways in which IP addresses might be logged and associated with accounts by their analytics providers, as opposed to e.g. https://www.privateinternetaccess.com/vpn-features/no-logs-v... .
Of course it's a different business model, and I can't vouch for PIA actually standing by those commitments. And I empathize with wanting to use best in class tooling to optimize your site experience. But prioritization of privacy, and commitments to minimizing log retention, are things you should consider revising to the extent you are legally able to do so. Don't feel you need to respond here, of course, to that point!