Privacy and your local data
In the hosted browser edition, language-model inference runs on your device. The inference runtime processes prompts, generated text, activation measurements, conversations, and fitted artifacts locally. Browser agents can read workspace data when given access, and their providers handle that information separately. The site also makes network requests to load software, download models, and perform specific online actions.
What stays in this browser
Saved conversations, settings, downloaded models, and fitted artifacts use browser-local storage. The hosted inference runtime does not upload prompts or transcripts for cloud generation or application telemetry. Local saves do not create an account backup or sync across devices.
Select Protect storage where available and download a backup of important work. Clearing site data, closing a private browsing session, or browser cleanup can remove local files. Deleting a local chat does not delete backups you previously exported or copies you shared.
Downloads and external services
The model catalog, model weights, and compatible instrument packs are downloaded from Hugging Face and its delivery infrastructure, then checked against the signed catalog and artifact hashes. Hugging Face receives each file request; it does not receive your prompts, chats, or activations. Searching for remote manifold packs sends your search query to Hugging Face.
SAE feature descriptions use bundled data when available. Opening a feature that has no bundled description can send an optional lookup to Neuronpedia. The request contains only the model name, SAE source, and feature number, without cookies, a referrer, your prompt, or your transcript. External links use the destination site's policies.
Hosting and network error reports
Drowse's website is hosted on Cloudflare. Opening a page requests its files from Cloudflare, which processes ordinary request metadata such as your network address, browser user agent, and the requested URL. Drowse does not use analytics, advertising, or tracking cookies.
Cloudflare's network error logging (NEL) asks your browser to report failed connections to Cloudflare. These reports describe the failure, such as the URL, error type, and timing. Successful requests are not reported.
Contact messages leave your device
Submitting the contact or feedback form sends its fields and a submission reference to Drowse's contact endpoint, a Cloudflare Worker. This includes your message and optional reply email; chats and model data are not automatically attached. The Worker sends the message through Cloudflare Email to Drowse's contact inbox when delivery is enabled and accepted. Your reply email is used only as the reply address.
The contact implementation uses rate limits and delivery receipts. Receipts store a content hash, status, and provider message identifier, and expire after seven days. Application logs record references and error codes, not your message or email address. The inbox retains delivered message contents under its own retention policy. Contact drafts remain in page memory. The form reports whether sending was confirmed.
Browser agents, exports, and Python servers
A browser agent with access to Drowse's WebMCP tools can read relevant workspace data and perform exposed actions. Operation records use tab-local session storage for recovery. Information that the agent reads is also subject to that agent provider's handling. Review exported files and explicitly chosen messages before sharing them.
In the Python edition, prompts and measurements pass between the dashboard and your configured Drowse server. If that server runs on another machine, it receives the data. Its operator controls the model, storage, and access settings.