|
|
|
|
|
|
by DoingFedTime
66 days ago
|
|
|
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. |
|
|