S Setu

Privacy Policy

Last updated 4 October 2026 · Applies to the Setu Chrome extension and the setu-relay local server.

Setu does not collect your code, your prompts, or the pages you visit. The element you pick, the change you describe, and the edits your agent makes never leave your computer. They travel between the extension and your coding agent over a server running on your own machine.

We do collect anonymous usage statistics, so we can tell which features people actually use. Two feedback boxes send whatever you type into them. Nothing else you type is collected.

What stays on your computer

All of the actual work Setu does is local:

This information travels from the extension to setu-relay, which runs on localhost — your own computer, not a server we control. We cannot see any of it, and none of it reaches us or any third party.

Setu only activates on localhost, 127.0.0.1, and local file:// pages. It does not run on public websites.

What we do collect

We use PostHog for product analytics. Events are tied to a random identifier generated in your browser the first time you use Setu. That identifier is not linked to your name, email, or any account, and we cannot use it to contact or identify you.

Anonymous usage events

We record that a feature was used, and sometimes a count or a category:

EventWhat it carries
element_pickedthe element type (e.g. button) and detected framework (e.g. React)
pick_stagedhow many picks are queued, and whether you used natural language or structured mode
picks_senthow many picks were sent
theme_changedwhich theme you chose
panel_approve / panel_rejectthe internal id of the pick — a random value meaningful only on your machine

The two feedback boxes

Two places in Setu send text you have typed:

Both are optional and both are labelled in the interface. Because you control what goes into them, please do not paste source code, credentials, or anything confidential.

What we never collect

Where the data goes

Usage events go to PostHog, on their US cloud infrastructure, where they act as our data processor. Their terms are at posthog.com/privacy.

We do not sell data, we do not share it with advertisers, and we do not use it for advertising or for training machine-learning models.

Permissions, and why Setu needs them

PermissionWhy
activeTab, scriptingTo draw the picker and panel on the page you are working on, and to read the details of the element you click.
storageTo remember your staged picks, history, and theme between sessions, in your browser.
tabsTo know which tab has the panel open, so messages go to the right place.
alarmsTo keep the connection to your local relay alive while the panel is open.
clipboardWriteFor the Copy buttons.
localhost, 127.0.0.1, file:///*The only pages Setu runs on. file:// is included so Setu works on local HTML files opened directly, without a dev server.

Setu asks for no permission on any public website.

Your choices

Children

Setu is a developer tool and is not directed at children under 13. We do not knowingly collect data from them.

Changes

If we change what we collect, we will update this page and the date at the top. Material changes will also appear in the extension's release notes.