You can always set up your own OpenVPN server on some inexpensive VPS (e.g., Scaleway.com) if you don't want to deal w/ a commercial OpenVPN provider. The good and bad should be obvious.
On the good side, you control everything, including logging. The likelihood of VPS snooping, while not impossible, seems less likely to me. And you can use if for reverse tunneling back into your home network, thus obfuscating your home public IP. And of course, just having a VPS allows to do other things on that server.
On the bad side, YOU now have to maintain it. And not every VPS is reliable. Uptime seems to vary quite a bit. And at least the inexpensive VPS providers often have substantial limitations on bandwidth and total capacity per month (caps). You can easily exceed the cost of a commercial OpenVPN provider when rolling your own if you expect similar performance and capacity.
One last thought. Although this about to be corrected in the next Merlin release, most routers do NOT block unsolicited, inbound requests over the OpenVPN client tunnel.
https://www.snbforums.com/threads/openvpn-client-security-enhancement.56328/
By using your own OpenVPN server on the VPS, you can at least block that side of the tunnel, which is particularly important if you screw up the firewall on the public facing network interface of the VPS! Of course, there's still the possibility of someone at the VPS messing around w/ your own VPS, but that seems highly unlikely. I'm more concerned about commercial OpenVPN providers because I can't see what's happening on their side of the tunnel. Bringing that side of the tunnel in-house at least gives you a view (and control) into what's happening.