Constructor for Chrome · Privacy

Updated November 6, 2026

Constructor for Chrome is the browser extension of Constructor, an issue tracker that starts coding agents from issues. You test your project's sites with it: you pin notes to what's wrong, each with a screenshot and what the page said, ask Foreman — Constructor's planning agent — about them, and have him turn them into issues. This page says what the extension reads, where it goes, and what it never does.

Where it works

Only on the sites you turn on: your projects' Stage and Prod sites, as Constructor lists them, each one allowed by you in Chrome's own prompt. It never asks for every site, reads nothing on any other one, and stops on a site as soon as you turn it off in its popup or in Chrome's settings.

What it reads there

While a tab is on a site you turned on, the extension keeps, in your browser alone:

• the page's address and title, the browser and the window's size;
• your last 30 steps on your project's sites: the pages you opened, what you clicked, named by the control's label or words, and that you typed into a field or picked an option, named by the field — never what you typed or picked;
• the last 20 errors the page's console logged;
• the last 20 requests of the page that failed: their method, address without the values of its query, and status, and for the page's own failed requests the first 2 KB of the server's answer — on Prod left out unless you keep it;
• the build the page says it runs, or that its site's check address answers.

When you save a note or send a message, it takes a screenshot of the element, the area or the visible page. Before the screenshot leaves the extension it paints over passwords always, and on Prod — on Stage too, unless you turn it off — every form field, what the site marks private (data-private), embedded frames, and text that reads as an email address or a card number. Emails and card numbers in the names of steps and in console errors are replaced the same way.

Where it goes

Nothing leaves your browser until you act on the page, and then only to the Constructor tracker you connected: constructor.works, or one your organization runs. Start session sends it the address of the page you start on and the build that page runs: the session is made of them, and its chat with Foreman begins with them. A note you save, or a message you send to Foreman, goes with what its chips show — each of which you can leave out, but the page and the screenshot. Your steps, console errors and failed requests go only with a note or a message. In the tracker a session is your project's, a note is an entry of the project's Intake and a message is part of your session's chat, which your project's people and the agents working on it read, as your organization's settings allow. Constructor's agents, Foreman among them, read with Claude, Anthropic's model, as they read everything else in Constructor.

The extension sends nothing anywhere else: no analytics, no tracking, no advertising, no third parties. Nothing it reads is sold, transferred, or used for anything but testing your sites with Constructor.

Your connection

You connect it on your tracker's own consent page, signed in there as yourself. The extension keeps the tokens it gets in its own storage, which no web page can read. They reach your test sessions alone: notes into the Intake of the projects you see, your Foreman in your sessions' chats, and the cards you file from his plans. They can't start agents, change settings or read your other chats. Disconnect in the extension's popup, or under Connected apps in Constructor, and they stop at once.

How long it is kept

In your browser, what a tab recorded goes when the tab closes, when you disconnect or when you connect to another tracker; the connection stays until you disconnect. In the tracker, notes and chats stay as long as your organization keeps them, and its people delete them there.

Contact

Questions about this page or the extension: slupdo09@gmail.com.