ProductConnect
Browser extensionpreview
Records clicks and timings in Chromium and Firefox, never what you type
Record a flow you walk through. Never what you type.
InOrbit Trails records the pages, clicks, scrolling, timings and script errors of a flow on a site you allow, only after you consent, and keeps them on our own servers. Your account replays them in the console. It never records what anyone types. In early access while it is built.
In early access. A 30-minute call is the way in; there is no SLA during early access.
A broken sign-up or checkout flow is hard to reproduce from a bug report. Session recorders that capture everything also capture what people type.
The recorder runs in your browser; the scrubbing rules run before anything leaves it.
How it works
- 01
Where it runs
- In your browser: Chrome, Edge, Vivaldi, Brave, Opera and Firefox. Scrubbing happens in the browser, before anything is sent.
- 02
What it reads
- Pages, clicks, scrolls, timings and script errors on sites you allow. Never typed values, cookies, storage, bodies or headers.
- 03
What you approve
- Recording, site by site, before anything starts.
Each line says how far it is built today. Live means anyone with an account uses it; preview means it runs in early access or as a pre-release; coming means it is written down and not built yet.
What you get
Records a flow, with consent
Pages, clicks, scrolls, timings and script errors on a site you allow. Nothing is recorded before you say yes.
previewNever what you type
Typed values, page text beyond an element's accessible name, storage, cookies, bodies and headers are never read.
previewReplayed in the console
Your account's recordings, with a scrubber across each one; only your account reads and deletes them.
previewChromium browsers and Firefox
Chrome, Edge, Vivaldi, Brave, Opera and Firefox. Safari and the store listings come later.
previewA trail turned into a test
Replaying a recorded flow as a check, and Trails over MCP. Not built yet.
coming
An account's recordings in the console.
In the console
Recordings
- 01checkout flow · 14 steps · 1 script error
- 02sign-in · 6 steps · 2.1 s to the first page
- 03search and filter · 9 steps
Typed text: never recorded
Example data
Drawn from the console's own layout. The services, times and numbers are made up for the example.
Every claim on this page has its evidence: the documents that define it, the docs that say how to use it, and the API it runs on.
Proof and links
Documents
- RFC 0055 Trails
- RFC 0055.1 Packaged releases and store listings
- RFC 0040.13 Flows in a browser
Not on the public RFCs host yet, so named here without a link.
API
- RESTpreviewList, read and delete your account's recordings.
- MCPcomingTrails over MCP is not built yet.
The evidence rule: a model saying it succeeded is never evidence. What counts is what was measured, by what, and when.
Your data, your call
Nothing is recorded without consent, typed values never, and another account's recordings answer as not found.
Logs record who did what and the outcome, never content. The platform's own models are self-hosted; a third-party model provider is one you connect with your own key, and it bills you directly, with no line or markup from InOrbit. Separately, our own DPAs with model providers are in progress, none signed yet. InOrbit is not certified: no auditor has attested its controls yet, and the known gaps are listed.
Questions, answered plainly
How do I install it?
In early access: after a 30-minute call, the console's Trails page has the install steps for your browser until the store listings are live.
Can it see my passwords?
No. It never reads what anyone types, in any field.
Is the source open?
The extension's repository is public, and its scrubbing rules are the same file as the site script's.
Next step
See it on your own system
Book 30 minutes with an engineer. We look at your system together and, where it fits, open early access for your team.