[toyg]

I used Cloak but moved away because:

1) There was no real interest in expanding the list of exit points.

2) It seemed to protect only http/https traffic.

3) The whole operation felt like someone's "passive income" business (although, to be fair, the owner responded fairly quickly and honestly when I queried him about other stuff).

To be fair, their OSX client tries hard to be transparent. This approach falls apart in some cases (i.e. some captive portals), but feels very smooth when it all goes right.

[case]

Fwiw Cloak just sold: https://blog.getcloak.com/2016/04/28/cloak-joins-stackpath/

I don't know if it was a "passive income" business for them, but if it were, why would that be a reason to not use it?

It has a fantastic UX on both Mac OS X and iOS devices.

[toyg]

> why would that be a reason to not use it?

Mostly because you can't expect many new features or the product evolving particularly fast. Which is exactly the case for Cloak -- the feature-set was basically frozen for years. It's not a crime: if a product works fine, why mess with it? But I wanted new stuff and it didn't feel like I'd ever get it.