Nephele Wisp · Browser Extension Privacy Policy

What Wisp does

Wisp performs the kinds of request below, each explicitly initiated by you — from the desktop app, or, for the clipper, by your own right-click or keyboard shortcut. None runs in the background or on a schedule you did not start.

1. Publishing a draft

Fills an upload form on a platform you choose and stops at “draft ready” for you to review and publish manually.

• Image bytes you asked to upload — fetched from a local-only 127.0.0.1 server via a one-time, 5-minute-TTL token URL, verified against a SHA-256 hash, then handed to the platform's <input type="file">. Never sent anywhere else.
• The title / caption / topic text you provided — typed into the compose form. Never sent anywhere else.
• The current page URL — used to detect login walls / captcha / wrong page; reported back to the desktop app. Never sent to a third party.

2. Collecting reference images

When you run a reference search, Wisp opens the search page for the source you chose (e.g. Pinterest, Huaban, ArtStation, or another site you search) and reads the results, so the desktop app can show you reference thumbnails — the same thing you would do by searching the site yourself.

• Public image metadata — thumbnail URL, large-image URL, source page URL, title / alt text, and dimensions, read from the search page or the platform's public search API. Returned to the desktop app.
• For Huaban only, the thumbnail bytes — fetched by the extension from Huaban's image CDN (which only serves a real logged-in browser, so the desktop app cannot fetch it directly) and returned to the desktop app for its local reference cache. Never sent anywhere else.

3. Reading your own creator stats

When you ask the desktop app to refresh your dashboard, Wisp opens your own creator-center page on a platform you are logged into and reads the analytics that page loads about your account.

• Your own public creator metrics (views, likes, followers, etc.) and your account ID on that platform — read from the responses your creator-center page already requests, returned to the desktop app and stored locally. Never sent to a third party.

4. Reading a page on your behalf

When you ask the desktop app to read or capture a page (for example, to collect references from a site you are researching), Wisp opens that URL in an ephemeral background tab in your own session, extracts a read-only snapshot, then closes the tab. Page capture is restricted to a fixed whitelist of read-only DevTools methods (screenshot, PDF, DOM/HTML snapshot) — it cannot run code or modify the page.

• Readable text, links, image URLs, optional CSS-selected rows, page metadata, or a screenshot / PDF / DOM snapshot of the requested URL — returned to the desktop app on your machine, held only for the lifetime of the request, then the tab is closed. Never sent to a third party.

5. Saving what you point at — the clipper

When you right-click and choose “Save to Nephele” (or press the clip shortcut), Wisp sends the desktop app a small pointer to the item you selected so the app can save it. The clipper is the one case where Wisp acts on the tab you are currently viewing — but only on the metadata you explicitly pointed at, only on your click or keypress; the extension reads no page content beyond that pointer (the desktop app decides what, if anything, to fetch).

• The image URL, link URL, selected text, page URL, and tab title of the item you clicked (whichever apply) — sent once to the desktop app as a clip event. The extension does not store it, and it is never sent to a third party.

Identifier stored across sessions

A random per-profile ID (wp_<uuid>) generated on first run and stored in chrome.storage.local, sent to the desktop app on handshake so it can recognize repeat connections. Not linked to any platform account, real-world identity, or telemetry system.

What the extension does NOT handle

• Your passwords, cookies, session tokens, or platform credentials — Wisp never reads or stores them.
• Tabs you opened yourself — Wisp's automation (form-fill, stats, page read) runs only in background tabs it opens, never attaching to a tab you opened. The one exception is the clipper, which acts on your current tab — and only on the metadata you explicitly point at, when you invoke it.
• Anything in the background — Wisp does nothing without a request you initiated or a clip you invoked.
• Browsing history.

Where data goes

• All data flows are local. Wisp returns everything to the Nephele Workshop desktop app on the same machine, via Native Messaging (restricted by Chrome to a host you explicitly installed) and the local asset server on 127.0.0.1.
• No servers of our own, no analytics, no telemetry. Although the extension can access any site (<all_urls>), the only hosts it ever contacts are the site you are actively working with — in your session, to carry out a request you just initiated — and the local 127.0.0.1 asset server. It never contacts a server of ours, and never sends your data anywhere off your machine.
• The desktop app's privacy is governed separately at Nephele Workshop's privacy policy. Wisp is the bridge — anything that later leaves your machine does so through the desktop app, under that policy.

The debugger permission

Wisp uses Chrome's chrome.debugger API to drive the upload form. Chrome shows a yellow “Nephele Wisp started debugging this browser” notification bar on every tab Wisp attaches to — this is the visible indicator that automation is happening. Wisp only attaches to tabs it has opened itself; it never attaches to tabs you opened manually.

See the permissions justification for why each permission is required.

Data retention

The only data Wisp retains across browser restarts is the per-profile UUID stored in chrome.storage.local. Image bytes, captions, URLs, scraped metadata, stats, and tab references are held only for the lifetime of the single request that produced them and discarded on completion. Asset transfer tokens expire 5 minutes after issue and are single-use.

Children

Wisp is part of a paid creator tool intended for adult professional artists. The extension itself does not collect age data.

Contact

Source code is open at github.com/CreatorAris/nephele-wisp (MIT). Security disclosures and questions: [email protected].

Changes

Material changes to this policy will be reflected in this document and in the extension's release notes.