Privacy policy

Last updated: 19 July 2026.

This policy describes the Chrome Web Store build covered by the date above.

Itra records a task while you narrate it, and turns it into a how-to guide. It does that on your computer.

This version does not require an account or sign-in, does not create a user ID or a device identifier, and collects no analytics. Your recordings, your screenshots and the transcribed text of your narration stay in your browser until you choose to send them somewhere - by exporting a file, or by pasting a recording into your own Jira issue. This version sends no data to Itra.

This policy covers the Itra Chrome extension. It does not cover the websites you record on, which have their own policies.

What Itra records, and only while you are recording

Itra runs on every page you open, and does nothing on any of them until you start a recording. Once you do, on the tab you chose, it records:

• Page addresses. The address of the page you start on, and the address of any page you reach from the address bar, a bookmark, or a route change the site makes itself. An ordinary link click is recorded as the click, not as a second address.
• Clicks and double clicks. A way to find the element again, its visible label or text (up to 120 characters), what kind of element it is, and where it sat on the page.
• Callouts. When you use Callout, Itra stores the page address, the exact path to the element you selected, its label and position, your note or element check, and a short piece of that element’s HTML. It takes the screenshot only when you press Save.
• Values you enter. The final contents of a text field once you leave it, and the state of a dropdown, checkbox or radio button when you change it. Not the keystrokes that got you there.
• Drag and drop. The item you dragged and where you dropped it.
• Some keypresses. Enter, Escape, and shortcuts held with Ctrl, Alt, Shift or Cmd. Plain typing, Tab and the arrow keys are never recorded.
• Screenshots. A JPEG of the visible part of the tab, taken as each step happens, with the element you are acting on outlined.
• Your narration, if narration is switched on. The guide audio pauses throughout Callout mode; pressing Record narration captures one temporary clip for that Callout note instead.
• The size of your browser window, so a replay can reproduce it.
• Your browser and system, once per capture. The browser’s name and version, the operating system’s name and version, and the window size - read from the browser’s client hints, never from the full user-agent string. Not your language, and not your timezone: neither is collected. Itra stores this with the capture and shows it nowhere. It leaves your computer only inside an export, and only when you switch Include my browser/OS info on. That switch is off unless you turn it on.

Itra records nothing on a tab you are not recording. While a recording is paused, it records no page actions or screenshots; a Callout box that was already open can still save its note or check.

One thing happens outside a recording. Itra reads the address of the tab you are looking at so it can show you a count of the recordings you already made for that page. It compares the address in memory and stores nothing.

Where it is stored

Everything lives in your browser, on your computer, in three places.

An IndexedDB database named itra. It has three stores. recordings holds the steps - addresses, selectors, labels, the values you entered, Callout notes, checks and short HTML pieces, the transcribed text of your narration, and pause/Callout timing windows - and the browser and system line described above. screenshots holds the images. audio holds the narration recording, as WebM/Opus, only until transcription succeeds or you delete the capture.

Extension local storage. Four preferences: whether narration is on, replay playback speed, and the two export defaults - whether exports show narration, and whether they include your browser/OS info.

It also holds two things that are not preferences. When you choose Copy for Jira, Itra writes the steps and their screenshots there, and leaves them until you paste them into a Jira issue or discard them. Nothing is sent at that moment. And when a replay finishes, Itra keeps a timing record of it - the last five runs, and no more. It holds how long each step took and which part of it took the time, the name of each step, and the addresses of the pages the replay visited. It holds no screenshot, no narration, and nothing you typed. It is a diagnostic, for the question “why was that replay so slow?”, and it is shown to you on the replay page. It is never sent anywhere unless you copy it and paste it somewhere yourself.

Extension session storage. Which tab is recording or replaying, how far a replay has got, whether each step of the last replay passed, and the timing record of the replay in progress. Chrome clears all of it when you close the browser.

None of it expires or is cleaned up on a schedule, except narration audio after successful transcription. A recording is kept until you delete it. Deleting a recording deletes its steps, every one of its screenshots, and its narration audio, together and immediately. Uninstalling Itra removes all three stores.

The microphone

Itra asks for your microphone only when you start a recording with narration switched on. Opening Itra does not turn the microphone on. The Test mic button does, and releases it after six seconds, or sooner if you press Stop test.

The guide narration recording is saved to your browser and transcribed there. When you stop Callout narration or press Save, its complete temporary clip is transcribed locally once and is not saved as a separate audio recording. Transcription runs a Whisper speech model inside the extension, compiled to WebAssembly. In this version, your audio stays inside the extension and is not uploaded. During Callout, the microphone is silent while you select an element, type a note or add a check. It turns on only after you press Record narration, unless you pressed Mute, and turns off again when you stop or Save.

For guide narration, once transcription succeeds and the transcribed text has been saved, Itra deletes the raw audio from local storage. Only the transcribed text is kept, and only that text ever leaves in a .itra export. If transcription fails, the audio stays in the audio store so that you can try again. It is also deleted when you delete the recording.

The requests Itra makes

This version makes no network request unless you ask it to. The Whisper speech model and the WebAssembly runtime that uses it both ship inside the extension, so transcription is fully offline from the first use.

Your Jira comment, when you ask for one. Choosing Copy for Jira sends nothing. Only when you then open a Jira issue and press Paste into <KEY> does Itra upload the steps and the screenshots you staged, to that Jira site and nowhere else. It goes as an attachment upload and a comment, over the Jira session you are already signed in to. The access to websites that Itra asks for at install already covers your Jira site, so there is no extra permission step, and Itra stores no Jira token, no site address and no credential of any kind. The screenshots are the ones the recording captured, unredacted - see below.

This version contacts no other host. Replaying a recording does make your browser load the sites in that recording, exactly as it would if you opened them yourself.

What redaction does, and what it does not

Itra applies three safeguards as the step is captured, in the page, before the content reaches the rest of the extension.

• Password fields. The value is replaced with ••••••••. The real password never leaves the page. When the recording is finalised, a password field - and the username field immediately before it - are turned into User Input steps: they carry no value at all, and replay pauses for each person to enter their own credentials. The editor tells you which steps these are, and lets you change them back to a typed value on purpose if you want one baked in.
• Email addresses. Text that looks like an email address is masked to its first character, so ada@example.com becomes a•••@•••. This applies to values you enter, labels Itra reads off the page, and the short HTML piece stored for a Callout, in fields that are not a converted username.
• Input values in Callout HTML. Itra removes every input value from the short HTML piece before storing it, including values on hidden inputs. The piece is also capped at 1,600 characters.

Other content is not redacted.

That means a recording can contain a name, a postal address, a phone number, a card number, an account number, an API key or a session token, if you entered it into an ordinary field. Page addresses are recorded whole, including the query string, which on some sites carries an access token. Screenshots are not redacted at all: whatever was visible in the tab at the moment of a step is in the image. The narration audio is not redacted, and neither is the text transcribed from it.

There are three ways to keep something out of a recording, and any of them is enough. Pause the recording before you do the thing, and Itra captures nothing until you resume. Edit a step’s text or its recorded value in the editor. Delete the step, which deletes its screenshot with it.

Do it before you export, because an export is a copy.

Why Itra asks to read every site

Itra asks for access to all sites, and it needs it.

A recorder cannot know in advance which site you will want to record, and a recording that starts on one site and finishes on another has to follow you across. Access to all sites is what lets Itra watch the page while you record it, take the screenshot, and drive the page again when you replay. The screenshot is also why the access has to be this broad: the browser’s screenshot function is only available to an extension that holds it.

Itra uses that access on the tab you are recording or replaying, and to read the address of your current tab for the badge count. It uses it nowhere else. On every other page its code is loaded and idle: each of its event handlers checks whether this tab is the one being recorded, and stops there when it is not.

What leaves your device

In this version, nothing leaves your device until you ask for it, and no data is sent to Itra.

This version has two ways to ask, and no others.

Exporting writes a file to your computer, the way any download does. This version does not upload the export. If you then send that file to someone, you are the one who sent it, and Itra is not involved.

Pasting into Jira does upload, to your own Jira site and nowhere else, and only when you press Paste into <KEY> yourself. It is described under The requests Itra makes above. Choosing Copy for Jira on its own sends nothing.

The formats do not contain the same things.

Format	What is in it
.itra bundle	The steps: page addresses, the way to find each element, the values you entered, the written instructions, and the transcribed text of your narration. No screenshots, no audio, and no browser/OS info.
.html web page	The written instructions, which include the values you entered, the transcribed narration, and the screenshots. No audio.
PDF	The web page above, printed by your browser. Same contents.
.docx Word file	The written instructions, the transcribed narration, and the screenshots. No audio.
AI prompt copied to your clipboard	Callout notes and checks, page addresses, element paths, the sanitized short HTML pieces, and the names of the screenshots. Text only: no screenshot file and no audio. Itra does not contact an AI.
AI feedback packet (.zip)	The AI prompt above and each Callout screenshot. No audio. Itra downloads it to your computer and does not upload it.

Two switches on the export screen change what the .html, PDF and .docx exports carry, and what Copy for Jira stages. Show narration is on unless you switch it off; switching it off removes the transcribed narration from the export. Include my browser/OS info is off unless you switch it on; switching it on adds one line - browser and version, operating system and version, and window size. The defaults for both switches are set in the extension’s options; the .itra bundle has no switches and never carries the browser/OS line.

The narration audio never leaves your browser in any format. The .itra bundle leaves the screenshots out on purpose, because they are the part most likely to hold something you did not mean to send. Whoever imports it captures their own screenshots on their first replay.

A recording someone sent you

Replaying a recording opens a real tab in your browser, with your logins. Its clicks and its navigations act with your authority.

So a recording you did not make is, in effect, a request to run something in your browser. Itra will not do it silently. Before the first replay of an imported recording it shows you every site that recording will open and the full source of any JavaScript or console checks in it. The Chrome Web Store version does not run those code checks: it reports each one as unsupported and skips it without failing the replay.

That protects your browser session. Nothing about the recording, and nothing about your decision, is reported anywhere.

Children

Itra is not directed at children and does not knowingly hold data about them.

Changes to this policy

If this policy changes, the date at the top changes with it. A change that alters what Itra stores or sends will be described in the extension’s listing before the version that makes it is published.

Contact

Questions about this policy, or about what Itra stores: privacy@itra.app.