What you bring
You give Loom the components your site is already built from, and you say which settings each one accepts. After that the AI can rearrange those components and change those settings. That is all it can do. It cannot write new code into your page, because a change can only ever name a component and its settings.
If you would rather not build any, a starter set comes with it and this site is made out of that set.
What leaves your server
When a person asks for a change in their own words, your server sends the model you chose an outline of the page. It also sends the list of pieces that model may use. It does not send your code, your data, or anything about who is reading.
The ready-made changes on the How it works page do not send anything at all. They are worked out on your own server, which is why they still work on a deployment with no model configured.
What this page counts
This site counts which parts of a page people reach, how long they stay, and what they press. It does not know who you are, set a cookie, or send any of it anywhere but the server you are already talking to.
It is switched off on this deployment, so nobody reading this page has been counted.
It is there because a page that adapts should be able to tell whether the change helped. That is a question about parts of a page, not about people.
Next
The site you are reading is a Loom application itself. It is an ordinary app with the package installed, built from the starter components anybody gets, and everything you have watched it do happened on the machine serving it.
What to read next