The Oracle IP (161.115.177.32) was present before video was enabled, and the Amazon EC2 node (44.224.75.233, us-west-2) appeared specifically when video started which is precisely how LiveKit SFU routing behaves. On the ToS point: LiveKit's DPA, not their generic user ToS, explicitly classifies LiveKit as an independent controller for operational metrics, including call detail records. That means Proton's own DPA constraints don't govern that data.
LiveKit can respond to a US CLOUD Act request for those records without notifying Proton.
The article contains live network captures run with `ss -tnup` during an actual Proton Meet call, DNS resolution and ASN lookups performed in real time, a line-by-line read of LiveKit's DPA identifying them as an independent Controller for call detail records, and CSP headers pulled directly from meet.proton.me.
If you found a factual error, name it.
"I don't like the animations" is not a methodology critique.
Fair point on the methodology. The ss output and CSP headers are concrete. The LiveKit Controller distinction is the part worth debating-independent Controller vs Processor changes the privacy story significantly. Has Proton responded to that specific claim?
So not factually incorrect? Saying it's drama and childish is name calling, is that not the very think you're saying you're against?
I noticed you didn't point out where it's factually wrong.
Brave has a feature (free) that lets you hit a button and literally remove every animation if you want.
The White House app tracker list comes directly from Exodus Privacy's independent audit, verifiable by anyone.
What the cards look like on mobile has nothing to do with it.
A number showing up in someone's SMS inbox and a government form explicitly pairing your name to your number with no retention policy are different data collection events.
An app published March 27th has no prior-administration version history. The other 7 apps in the piece span back to Obama the article treats this as a bipartisan failure.
reply