4 ms·
The difference between aggregating traffic for the purposes of internal network management, and sending traffic data to a third party is not hard to see. It's
by paranoidrobot 5y ago
The difference between aggregating traffic for the purposes of internal network management, and sending traffic data to a third party is not hard to see.
It's also a vastly different type of aggregation.
- Mindwipe 5y ago> The difference between aggregating traffic for the purposes of internal network management, and sending traffic data to a third party is not hard to see. Is it? If they send it to a third party technical subcontractor for internal network management is that bad? If they publish a chart publicly of the top ten websites our users visit is that bad? (That's very common). If they pass the data to geofiltering vendors to use for threat intelligence to reduce DDOS attacks is that bad? Fraud? What exactly is the obvious line here that you think exists, other than "I don't like copyright."
- jollybean 5y agoThey are sending it to a third party so that party can use indirect behavioural information to enforce commercial contracts. Imagine McDonald's selling data to your insurance provider so they can help determine your rates etc.. It's definitely out of bounds and worth putting up a fuss over.
- crtasm 5y agoBut they're not sending any customer data in this case. It's a list of IPs of servers that are seeing traffic spikes on their network, not IPs of customers connecting to them.