The answer would be… kind of. So n8n desktop uses local tunnel which opens an outbound connection to a broker service that listens for connections and routes them down the tunnel your desktop instance opens.
Because it needs some kind of domain to use to make it available it easier to do it from a domain we control rather than the normal localtunnel.me domain.
As for logging I suspect there will be some kind of anonymous data for connections so maybe an ID and a date / time but no request body information, @sirdavidoff may have more information on that side of things.
I was impressed with it when it was released as well, It wasn’t exactly what I was hoping for but it is a solid base and it provides a fantastic way to get started with making workflows or even use your desktop as a dev environment before exporting the workflow and pushing to a production instance to run.
I really like using it when I want to take a screenshot for another member in the n8n community (this way I don’t fill up my server with demo flows : )
I was even thinking of using the program for one time big heavy flows I want to test out. So I would not need to upgrade my n8n server but still have a VERY powerful n8n flow that runs on my PC when needed (I can even have my server flow execute a flow that runs on my PC app : )
My Pi that I still use for my personal projects is full of demo flows, Splitting it up and using desktop for examples / community is a great idea.
I set up a cheap Nuc that I got off eBay to run n8n in worker / queue mode and I have not yet put anything on it but the plan is to use that for my main workflows and retire the Pi for a bit so I may use Desktop for community stuff although it is a couple of versions behind.