Weft Tasks browser extension: privacy policy

Last updated: August 30, 2026

The Weft Tasks extension shows pending human-input tasks (approvals, forms) from a Weft runtime you operate, and sends the answers you type back to it. This page describes everything it stores and everything it sends.

What it stores

The extension keeps three things in your browser's local extension storage: the connect tokens you paste in, the runtime addresses those tokens belong to, and your notification preference. Nothing else is stored, and none of it ever leaves your browser except as described below. Removing the extension deletes all of it.

What it sends, and to whom

The extension makes requests only to the runtime addresses you configured: it polls them for pending tasks, and it submits the answers you type. Your connect token travels in a request header, never in a URL. If you configure no address, the extension makes no network requests at all.

It sends nothing to WeaveMind, Inc. and nothing to any third party. It collects no analytics, no telemetry, no crash reports, and it sets no cookies.

Permissions

storage holds the tokens, addresses, and notification preference above. notifications shows a browser notification when a new task arrives, and can be turned off in the popup. alarms wakes the extension every thirty seconds to poll your runtimes.

The extension asks for no site access up front. When you add a runtime address, the browser asks you to grant access to that one host, and the grant is handed back when you remove the last token on it. The extension can only ever reach hosts you approved this way, and it reads no page content anywhere: the grants are used solely for the polling and submitting described above.

Questions

The extension's source is public, in the weft repository (under extension-browser/). For anything this page does not answer, write to contact@weavemind.ai.