Privacy Policy

1. Controller

Wusel Capture is an open-source project maintained by an individual, not a company. The controller responsible for this website is:

Espen Finnesand
Email: wusel-capture@wusel.app

The full source code is published under the MIT licence at github.com/secretlifeof/wusel-capture. Every claim in this policy can be checked against it.

2. This website

This site is a static set of pages. It sets no cookies, runs no analytics, embeds no trackers, and loads no third-party scripts. Our fonts are served from this site rather than from a font CDN, specifically so that no third party learns your IP address when you read this page. There is nothing to consent to, which is why you see no cookie banner. See the Cookie Policy.

The site is hosted on GitHub Pages by GitHub, Inc. (a Microsoft company). Like any web host, GitHub processes technical connection data — including your IP address, the page requested, and your browser's user agent — in order to serve the page to you and to keep the service secure. We have no access to those logs and receive no reports from them. This processing rests on Art. 6 (1) (f) GDPR (our legitimate interest in operating a functioning website). GitHub is a US provider; transfers are covered by the EU Standard Contractual Clauses and the EU–US Data Privacy Framework. See GitHub's privacy statement.

3. What the browser extension handles

The extension does nothing until you click its toolbar icon and take a capture. When you do, it assembles a capture on your device from the following:

• A screenshot of the page — the visible viewport, the full page, or a region you draw. Images only: no video, no audio, no camera or microphone access.
• Page context — the page URL and title, your browser's user agent, viewport size, device pixel ratio, scroll position, screen size, browser name and version, platform and language.
• Diagnostics — a rolling in-memory buffer of the most recent console errors and warnings, and of failed network requests, so your assistant can see what went wrong. For a failed request we record only the URL, method, status and timestamp. We never record request or response bodies, HTTP headers, cookies, or the contents of page storage.
• Your own input — the note you type and the annotations you draw.

The extension does not log keystrokes, clicks or mouse movement; does not read your browsing history, bookmarks, cookies or passwords; does not read the page's text or form values; and does not track you across sites. It observes only the page you explicitly capture.

Because this processing happens on your device and the result is delivered only to tools you control, we are not the controller for the contents of your captures. You are responsible for any personal data contained in pages you choose to capture.

4. Where a capture goes

Nowhere near us. A finished capture takes one of two local paths, and you choose which:

• Download (default). The annotated image is saved to your own disk through the browser's normal "Save file" dialog. Your editor is then opened via a vscode:// or codex:// link pointing at that local file.
• Native host (optional). If you deliberately install our companion host, the capture is written straight into the matching project folder on your disk and your locally installed editor is opened on it. The host is open source, runs entirely on your machine, and makes no network connections.

5. Your AI assistant is a third party

6. Storage and retention

• IndexedDB (in your browser). Pending captures are held locally, purely to hand a capture from the popup to the editor tab — a full-page screenshot is far too large for extension storage. Automatically pruned to the 10 most recent captures.
• Extension storage. Exactly two UI preferences: which assistant you picked, and an optional Claude Code session id you may type in. No images, no page content, no URLs.
• Your disk. Captures you chose to save or send. They are yours; delete them whenever you like.

Uninstalling the extension removes everything it stored in your browser. Files you already saved to disk remain, because they belong to you.

7. Redaction

Two protections are built in, and both apply before a capture is exported or sent:

• The Redact tool pixelates any region of the image you mark. The pixelation is baked into the exported bitmap, so the original pixels cannot be recovered from the file that leaves the editor.
• Automatic URL redaction. Query parameters in captured request URLs whose names look credential-like — token, secret, password, authorization, cookie, session, jwt, api_key, access — have their values replaced with [REDACTED].

These are safety nets, not guarantees. A screenshot shows whatever was on your screen — review it before you send it.

8. The skill, the CLI and the native host

The Wusel Capture skill and the optional native messaging host run on your own machine. The host writes a capture into a local project folder you configure and opens it in your editor. These components transmit no captures, source code or configuration to us, and make no network connections of their own.

9. Your rights

Under the GDPR you have the rights of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and objection (Art. 21), and the right to withdraw consent at any time (Art. 7 (3)).

In practice we hold nothing to which those rights could attach: your captures never reach us, and we operate no database, no accounts and no logs of our own. You exercise complete control by deleting your saved captures or uninstalling the extension. If you would like to ask us anything about this, write to wusel-capture@wusel.app.

You also have the right to lodge a complaint with a data protection supervisory authority — in particular the one where you live, where you work, or where you believe the issue occurred.

10. Children

Wusel Capture is a developer tool and is not directed at children. It collects no data from anyone, of any age.

11. Changes to this policy

If the extension's behaviour ever changes in a way that affects your privacy, this policy will be updated before that version ships and the date at the top of this page will change. The full revision history is public in the Git repository.