What is
recorded.

• Who runs it. 32dots in Heidelberg, Germany, on a rented server of the company Hetzner.
• No cookies. The pages set none.
• No list of visits. Your browser’s request reaches the server with your internet address, as every request on the web does. Neither the web server nor the program in front of it writes requests down.
• Page views are counted. A counting program named Umami runs on the same server. It notes the page, the page you came from, your browser, your system, your screen size, your language and the country your address belongs to. It sets no cookie and does not keep your address. A browser that sends “Do Not Track” is not counted. The hand-in page is not counted at all.
• The curriculum chat. The page /chat/ is not linked yet. Your question and the conversation so far go to a language model that the project runs on its own computers, not to another company. A question the chat could not answer from the curriculum is kept with the day’s date, cut to 2,000 characters, without a name or an address. With “web search” switched on, the question also goes to a search program on the project’s own computer, which asks search engines on the web.

• What is sent. When you press “Hand it in”: the course code, your name, how to reach you if you wrote that, your three notes and the recipe. Nothing is sent before you press the button.
• What is kept. Everything but the course code, in a folder on the server that only the Desk team can read, with the time it arrived.
• For how long. Until somebody on the team has looked at it and deletes it. The box holds 100 hand-ins at most.
• Who is told. A message goes to the team’s own chat, on the same server. It names the app and the hand-in’s number, not you.
• Nothing is published from the form. An app reaches the shelf only after a review, and then without your notes.

The Desk has no account and no sign-in. It counts nothing and reports nothing. These are all the times it reaches the internet:

• A newer version. From 0.2.0-alpha.8: thirty seconds after its menu starts and then once a day, it fetches one small text file from this website. It sends nothing with the request. When you press “Update now” it fetches the new version from this website.
• A shelf. Only when you press “Show more apps” or “Look again”, or use the commands for it, it fetches the list of each shelf you named and the recipes on it. The Desk’s own shelf is on this website; another shelf is wherever its keeper put it.
• An app’s program. When you install an app, Podman downloads the app’s image from the place its recipe names: n8n’s and Gitea’s own servers, GitHub for Open WebUI, Docker Hub for Ollama. Those servers see your internet address, as for any download.
• Podman itself. On Windows, “Set up Podman” fetches Podman with Windows’ own package manager.
• “First steps” on a card opens this website’s help page in your browser.

The Desk’s window is a page built into the program. It loads nothing from the internet.

Each app is its makers’ program. It runs on your computer and keeps your work there. What it sends is its own matter; this is what we know.

• n8n. Left alone, n8n reports to its makers how it is used and asks them for news of newer versions. From 0.2.0-alpha.8 the Desk switches both off. n8n’s pages can still load its list of templates from its makers’ server.
• Gitea. Its check for newer versions is off unless you tick it on the first page.
• Open WebUI and Ollama. A model you pull is downloaded from Ollama’s library on the web. Your chats with a model on your computer stay on your computer.
• What you connect. When you give an app a mail account, a key for an AI service or a web address to call, the app sends your data there. The Desk has no part in that.
• An app from a shelf is whatever its recipe runs. The Desk shows the image and the address before you install it, and marks apps the Desk team has not reviewed.

Questions about any of this: ask whoever runs your course.