And if you are referring to in-Spark transactions, the same issue exists in an in-LSP transaction... I.e. the sender and receiver are connected to the same LSP.
Login to reply
Replies (2)
I recommended you a few times in the past not to overhype the privacy state of Lightning. I suggest you align your documentation with this: 
Lightning Privacy Research
Lightning Privacy Introduction | Lightning Privacy Research
An introduction to Lightning privacy
Again, an extreme edge case where one LSP has a private channel with both the sender and receiver, something which is very, very rare in practice.