Privacy Policy

1. Summary

Studio and the on-device bench do not require an account. Experiment files, thumbnails, theme preferences, and game progress stay locally. Signing in with GitHub is optional and used only if you send a scheme to Abyss. Loomrume does not track you across apps or websites for advertising.

2. Data that stays on your device

• Optical experiments and library content you create or import
• Preview images generated on device
• Editor and canvas preferences
• Level progress for the native game mode

Under Apple App Store and Google Play privacy labels this is treated as Data Not Collected when information is not transmitted off the device in a way that allows Loomrume to access it.

3. Agents and models

Browsers are beginning to offer pages an agent interface (WebMCP). Loomrume uses it only if you ask: the “Enable WebMCP” switch in Studio settings appears only when your browser has such an interface, and it stays off until you turn it on. While it is on and a scheme is open, an agent you control can read and change that scheme through our editing tools. Registration happens inside the page: we do not send your scheme anywhere and we cannot see your conversation with the agent. The tools reach only the scheme you have open — not the rest of your library, not other schemes, not your browser storage. Changes an agent makes are saved exactly like your own edits. Keep in mind that an agent is usually connected to a model provider you chose, so whatever it reads may leave your device under that provider’s terms. Turning the switch off removes the tools again.

Studio also has an assistant panel of its own, and it stays inert until you supply a key. You pick a provider and paste your key; from then on requests go from your browser straight to that provider, never through our servers, so we see neither the key nor the conversation. Those requests carry the scheme being worked on, so treat it as leaving your device under that provider’s terms. The key is held in memory only for as long as the tab is open and is never written to disk — closing the tab or pressing “Forget key” drops it. Which provider and model you picked is remembered on your device like any other editor preference; the key never is. Edits the assistant makes are saved exactly like your own, and undo reverses them.

You can also point the panel at a model server running on your own machine — Ollama, LM Studio, or anything else speaking the same API. Then nothing goes to a provider at all: the request travels from the browser to your own process, and the scheme never leaves the device. Only addresses on this machine are accepted, because a page may not reach further; your browser will ask you once before letting it through, and the server has to be told to accept requests from this site.

The panel can also take dictation, and it asks your browser for recognition that runs on this machine — the microphone is open only while you leave the button on, no recording is kept, and the audio is never sent to us or to anyone else. The recognised words land in the input box for you to read, and nothing is sent until you press send. One caveat about the first use: the browser has to fetch its own speech model for that language, so it downloads one from its vendor and keeps it — that download tells the vendor a model was fetched, and after it your voice stays on the device. Where your browser cannot recognise speech locally, the microphone button is simply absent.

4. What we do not do

• No advertising identifiers collected for tracking
• No analytics SDKs that upload your experiments
• No account signup required for the on-device bench

5. This website

The website at https://www.loomrume.com is a public information page. Hosting providers may process standard technical request logs (for example IP addresses) as part of delivering the site. We use Vercel Web Analytics for aggregate page metrics (such as page views, referrers, and rough geography) and Vercel Speed Insights for aggregated performance metrics (Core Web Vitals). Both are privacy-oriented and do not use cookies to identify you across sites; they do not upload optical experiments or editor content. The site does not embed third-party advertising trackers. A GitHub session cookie is used only if you sign in to send a scheme to Abyss; see GitHub and Abyss below.

6. GitHub and Abyss

Studio still works without an account. GitHub sign-in is optional and only for “Send to Abyss”. GitHub then gives us your numeric user id, login, and the public profile the API returns for the authorized user. We do not request your email or permission to write to your repositories. The session is an encrypted cookie on this site; we do not keep a user database. The scheme JSON, a JPEG preview, the title, your description, and your login go to GitHub as a public pull request in the loomrume/abyss repository and remain there under GitHub’s terms. Signing out clears our session; it does not delete a pull request that is already open.

These cookies are strictly necessary for the Abyss sign-in you start yourself. They are not used for advertising or cross-site tracking, and they are not set until you choose Sign in with GitHub. Signing out clears them. We do not show a separate cookie-consent banner for them: the click is the consent.

How GitHub processes your account is described in their Privacy Statement: GitHub Privacy Statement

7. Contact

Questions about privacy: hello@loomrume.com