The structure of the page it is working on

Each step, the extension builds an accessibility-style summary of the page — the interactive and labelled elements, their roles and their visible names — and sends it to Matchai, which passes it to the AI model that decides the next action.

That summary is what the model acts on. It is not stored: the run record keeps only its character count, never its text.

• It does not include your credentials, cookies or session tokens on the site being worked. Those stay in your browser and are never read or transmitted by the extension.
• It does not include the full page source.

A picture of the visible page

Each step also captures an image of the visible part of the tab being worked and sends it alongside the summary, so the model can see what a person would see. Whatever is on screen at that moment is in that image.

These images are sent for that one decision and are not stored by Matchai. They are processed by our AI provider under our commercial agreements and are not used to train their models.

The capture is refused outright when the tab being worked is not the visible one, so a run cannot photograph a tab it is not working.

Files, when you ask for them

Two actions move files, and both are bounded by an explicit decision from you.

• Saving a page. The assistant can keep the page it is on as a PDF in your Matchai account — a deed or a certificate you have paid to view, for example. It arrives private and filed to nothing, visible to no one else.
• Attaching one of your files. The assistant can put a file you already have in Matchai into an upload field on the site. Because that discloses a private document to a third party, it always stops and asks first, naming both the file and the site — and it never presses submit; you do.

Notes about how a website behaves

When a run works out something durable about a website — that a control needs two clicks, that results load inside a frame — it may record that as a short note, which helps the next professional who automates the same site.

These notes describe the site. They are never about you, your clients, or the record you were working on.

What the run record keeps

A run is recorded in your Matchai account so you can see what happened: what you asked for, the site, the address of each page it reached, the intention the model stated for each step, the actions it chose, and what resulted.

It is stored with your account and subject to the web app’s retention practices. You can ask us to delete it at any time.

When you teach it (the Browser Dojo)

In the Browser Dojo you show your assistant a task once, in your own browser, and it writes the steps down as a skill you can run later. You start a demonstration yourself, from Matchai or from the side panel. It watches only the tabs of the orange "Matchai is watching" tab group it opens, and only while you are showing it: never for more than an hour, and never after you save or discard the demonstration.

While it watches, it records which controls you use — the name and kind of each button, link, field, list or group of options, as the page labels it — the address of each page without the values that follow the "?" in it, when you open or switch between the tabs of that group, and any note you type.

• It never records what you type or choose: not the text you enter in a field, not the option you pick in a list or with a radio button (only the name of the list or group you chose from), not the name of a file you attach. The one exception is whether a checkbox ended up ticked.
• A label that looks like personal information — an address, a phone number, an email address, a lot or file number, a date, a search result that names a person or a property — is replaced by a placeholder before it leaves the page.
• It takes no screenshots, reads nothing of the page beyond the labels of the controls you use, and does not use the debugger.
• Nothing is recorded in tabs outside that group, in other windows, or on Matchai itself.

What it records is sent to Matchai over HTTPS, where our AI provider words it into plain steps for you to review and correct. Nothing becomes a skill until you approve it in Matchai. A demonstration you do not save is deleted within 14 days; the recorded steps behind a saved skill within 30 days, while the skill itself stays until you delete it.

How the extension is used (usage analytics)

So we can tell whether the extension works for you, it records a small set of named events about its own controls and sends them to Matchai with your session: a run starting, Stop being pressed, Take over being pressed and how long the page took to hand over, how long you kept the page, a run waiting for you and how it was answered, the extension restarting during a run, and a Browser Dojo demonstration not saving or having a step fixed.

Each event carries only its name, the hostname of the site the run started on (never the page address), the run’s identifier, counts and durations, and a word from a fixed list such as which button was pressed. It never carries page content, anything you type, a page address, a file, or a client’s details. Matchai forwards them to our product analytics provider, PostHog, under your account, as it does for events in the web app. Because they are identifiers, counts and durations only, they are sent whether or not you accepted analytics cookies on matchai.co; that choice governs the side panel’s analytics described next.

The side panel — the extension’s own page, not a website’s — also records which of its controls you use and a replay of the panel with all text and every input masked, but only if you accepted analytics cookies on matchai.co. The code that does this is bundled inside the extension; nothing is downloaded to run it, and nothing like it runs on the websites you visit.

Browser permissions

• debugger — how the assistant reads the page accurately and performs real input. It attaches to the one tab a run is working, only while that run is active. It is released when the run ends, and released again whenever the assistant stands down for you to do something yourself, so nothing privileged is attached while you type a password or a card number. Chrome shows its own banner across any window it is attached to, so the browser tells you independently of us.
• scripting — draws the frame, the cursor and the controls on the page, so a run is visible while it happens, and places a file into an upload field once you approve one. During a Browser Dojo demonstration, it also adds the script that notes which controls you use to the pages that load while the demonstration runs. That script records only in the tabs of the demonstration’s group, and does nothing in any other page. It stops recording when the demonstration ends, and from then on it is added to no page.
• tabs — opens the window a run works in, follows a page the site opens itself, and brings Matchai back to the front when the assistant needs an answer from you. In the Browser Dojo, it tells which tabs belong to the demonstration and when you move between them.
• activeTab — captures the image of the visible tab described above.
• storage — holds the current run’s or demonstration’s state locally so it survives a page navigation. Not transmitted, and cleared when the run or the demonstration ends.
• alarms — ends a run that has been waiting on you for more than fifteen minutes, so an abandoned run does not stay open indefinitely.
• sidePanel — shows the panel that narrates a run beside the page, docked beside the tab the run is working in, so the site is never covered by it. The panel reads nothing from the page: it displays what the run reports and the steps you can already see happening.
• tabGroups — places the tab a run is working in inside a green "Matchai" tab group with a blinking dot, so you can see in the tab strip which tab is live. The group is removed when the run ends. During a Browser Dojo demonstration, the tabs it watches are an orange "Matchai is watching" group instead, removed when the demonstration ends. It creates, labels and removes those groups and reads nothing from any tab.

Site access

The extension requests access to all sites, and we would rather state that plainly than understate it: you choose at run time which site the assistant works, and no list of sites declared in advance would avoid blocking you somewhere we failed to predict.

Access is not use. Nothing is read on any site except the one tab an active run is working, for the duration of that run — and, during a Browser Dojo demonstration you started, the labels of the controls you use in the tabs of its group.

It also requests access to matchai.co, which is how the web app and the extension speak to each other. Only pages on matchai.co can start a run.