All are probably telemetry services - by blocking these the app works just fine.
This might not be legal in all countries without consent. GDPR is a beast in terms of what data you can collect out of users. in EU you need to specially ask for permission to do so. This is related to question “are you sending information that can be used to track unique user” - for example ID that doesn’t change during the app usage.
So my suggestion: ask permission from users before sending telemetry data. Before they agree, do not make outbound network connections from the app.
As far as I know, the app does this in a way that ensures that none of these should be sending any trackable information until user has provided consent. I do take privacy seriously so I will review the code to ensure this is still true.
And I’ll see if I can rewrite some parts to prevent connections at all until after the onboarding process where the user is asked for consent.
It doesn’t need to be anything else than in the startup of the app - ask for consent.
As these happen in the background, users typically don’t see these, but as I was launching PoLo on my MacOS my firewall started to ask permissions for connections to listed servers and just wanted to bring this into attention. I know some people might react in bigger scale to these kind of home calls/telemetry-connections without consent.
