Sorry for missing that. I did go through my list of things to be done for "easy to add" items before making this release, but it seems I had forgotten to add this one. But I've added it now so hopefully I'll notice it for the next release.

This has been suggested sometimes, but I'm wary of adding these NOT rules without a concrete use-case for several reasons. Are you sure this NOT location can not be solved by using Default rule? Meaning, specify the rule with actions when you're in location, but in Default rule specify the actions when NOT in the location.

There is a way for detecting if data transfer is going on, at least on mobile network - but it might require C++ code. I'm already using such code in ProfileMatic for not changing mobile network mode if a call or data transfer is ongoing.

Please do report on your experiences on switching the background connections on/off. It is at least useful for people to add to custom action... And if there's a fool-proof way to do it, I might find a way to add it to ProfileMatic as a real action, unless platform security gets in the way. But restarting critical operating system services is something I am really wary of integrating into the UI, as there is bound to be adverse effects causing headache for users who then quite understandably would blame ProfileMatic.