00:00Security & privacy
What we record, what we hide, and where it goes.
A recording can contain whatever was on screen, including other people's data. This page explains how we keep that to what you need, in plain words.
Masking
Masking hides sensitive text inside your browser, before anything is uploaded. The replay keeps the page layout, and the hidden text shows as dots or asterisks. Workspace admins choose the level.
Standard
DefaultHidden
Passwords, card numbers, one-time codes and fields that look like tokens. Secrets in page addresses, such as token=, key=, code=, session= or email=. Card-like numbers you type anywhere.
Good for
Most reviews: marketing sites, staging apps with test data.
Strict
For real customer dataHidden
Everything you type. All text on the page: the layout and buttons still replay, but words become ***. Screenshots are turned off, because they would show what masking hides. Console messages are cut to their first line.
Good for
Admin tools and back offices full of real people's data.
Custom
Set by adminsHidden
Standard, plus CSS selectors your admins choose to mask or leave out entirely.
Good for
Teams that know exactly which parts of their app are sensitive.
For site owners. Add data-fbr-mask to an element to mask its text and values in every recording, at every level, or data-fbr-block to leave it out entirely.
Allowed domains. Admins can limit recording to your own sites, for example *.staging.yourco.com. Elsewhere the Start button is disabled.
Never captured at any level: request and response headers and bodies, other tabs, and anything before Start or after Stop.
Where a recording goes
01In your browser
The extension records only the tab where you pressed Start, only until Stop. Masking runs here, so masked text never leaves your computer. While you talk, audio streams to our server for live captions.
02Upload
On Stop, the recording uploads over TLS to private storage in Germany. The copy in your browser is deleted once the server confirms it.
03Transcription
Our server sends the audio to ElevenLabs for the final transcript.
04Summary
A text version (transcript, page titles, element text, errors) goes through OpenRouter to an AI model, which writes the issue list. No audio or screenshots.
05Replay and sharing
Recorded pages replay on a separate domain with scripts disabled, so a recorded page can't reach your account. Share links can be limited to your workspace, can expire and can be revoked.
06Your agents
AI tools you connect read recordings through the MCP server with a token tied to one workspace and read-only access. Admins can turn this off.
Who processes it
| Hetzner (Germany) | Servers, database and recording storage |
|---|---|
| ElevenLabs | Live captions and transcripts (audio) |
| OpenRouter and the model provider it routes to | Issue summaries (text only) |
| Stripe | Payments and tax |
| Email provider | Sign-in codes, invitations and billing emails |
None of them may use your data to train models. We exclude AI providers that train on prompts.
How long we keep it
| Recordings | 1 year by default; 30 or 90 days if your workspace chooses |
|---|---|
| Deleted recordings | 7 days in the trash, then gone |
| Raw uploads | Deleted 7 days after processing |
| Trial without a subscription | Recordings deleted 30 days after the trial ends |
| Deleted account or workspace | Everything deleted within 30 days |
Security
- Encrypted in transit and at rest. TLS everywhere; storage is private and only reachable through links that expire within 15 minutes.
- Separate replay domain. Recorded pages are untrusted HTML, so they replay on a different site with a strict content policy and no access to your session.
- Short-lived tokens. The extension's sign-in token expires quickly and the refresh token rotates. Web pages and the recorder scripts never see either.
- No staff browsing. Our team can open a recording only if you grant support access to that recording, and each grant is logged.
- Read access is logged. Every read by an AI tool is recorded per recording: who, which tool, when.
- Admin access needs two factors. Our platform admin console requires two-factor sign-in.
Chrome Web Store Limited Use
Voicetrail's use of information received from the browser extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
We use the data only for the extension's single purpose: recording a narrated review of a web app and turning it into a replay, transcript and issue list. We don't sell it, use it for advertising or credit decisions, or transfer it except to the service providers above to provide that purpose, or when the law requires it. People at LEETLABS PTE. LTD. don't read it unless you grant access to a recording, it's needed for security, or the law requires it.
Questions or a security report: contact@leetlabs.ai.