Privacy & consent
A useful report starts with a message. Screenshot and replay capture are optional, and declining them keeps the message-only path available.
What a message includes
Every submitted message includes browser context, even when the tester declines both captures: the page URL, title, user agent, viewport, language and up to 20 recent console warnings and errors from the page (the widget's own warnings are left out). Screenshot and replay attachments have their own consent choices. Opening the widget does not grant either permission.
Redaction
The widget cleans the browser context before it is sent or queued, and the server applies the same rules before anything is stored or passed to AI analysis and coding runs.
- URL parameters: the values of
token,access_token,id_token,refresh_token,code,state,key,api_key,secret,password,session,sid,auth,sig,signature,otpandemail, and of names ending in token, secret, signature, password, apikey, sessionid or email, becomeredacted. Names match regardless of case, underscores and dashes. - URL fragments and credentials: the part after
#is dropped unless it is a hash route without parameters, such as#/settings. A user name and password in the URL are removed. - Secrets in text: in the URL, title and console text, JWTs,
BearerandBasiccredentials, email addresses and long hex or random-looking token strings become[redacted]. URLs inside console messages follow the URL rules, and so does any name=value pair with a listed name, such as/api/me?token=…or a cookie'ssession=…, along with quoted JSON values such as"password":"…". Parameters inside an encoded parameter value, such as aredirectaddress, are redacted too. - Length: the URL and each console entry are shortened to 2000 characters, the title and user agent to 500.
- Hidden characters: invisible Unicode in messages, titles and console text (tag characters, zero-width characters, bidirectional controls and runs of variation selectors) is shown as a visible marker such as
[U+202E], so hidden instructions can't reach your team or AI tools unnoticed. Characters that languages and emoji need stay intact: emoji sequences, joiners between letters of scripts such as Persian, Hindi or Sinhala, and single direction marks next to right-to-left letters.
Redaction is pattern based. It can hide a value you wanted, such as a state parameter, and it can't recognise every secret, so keep secrets out of console messages and page titles.
Choose a consent presentation
The project controls how the choices appear: a guided wizard, inline checkboxes or separate prompts. The wizard is the default. These are available on every plan in Widget customization.
Screenshot consent
When screenshot capture is allowed, the widget captures the visible part of the page when the report is sent. When permission is denied or still pending, no screenshot is attached. The choice is remembered in this browser, in localStorage under testosaurus:screenshot-consent, until the tester changes it in the widget.
The feedback widget is left out of the screenshot. Values typed into inputs, textareas and selects, and text in editable regions (contenteditable), are replaced with bullets, including fields inside web components with an open shadow root. Other visible page text appears as shown, so mark personal data on the page:
data-testosaurus-maskreplaces an element's text with bullets.data-testosaurus-blockleaves the element out entirely.- The
rr-maskandrr-blockclasses work the same way.
The same markers apply to session replay. If a screenshot can't be captured or attached, the report is still sent without it, the browser console shows a warning, and the report records the reason.
Replay consent
Replay recording starts only after consent is granted. That choice is remembered in this browser under testosaurus:replay-consent. Form values and rich-text typing are masked in replay, and the widget is never recorded; read Session replay for masking, recording and buffer behavior.
Test sessions
Test-session tokens show a full-screen consent card when the page loads. It replaces the project's consent presentation, which applies to standard tokens only. Every report still includes the browser context described above. Accepting adds a screenshot and a replay of recent page activity (typed text is masked); declining keeps feedback available without them.
The choice is remembered in this browser under testosaurus:active-consent. The widget keeps a Screenshot and replay on · Change control, so a tester can reopen the card at any time, and declining stops replay recording.
Revisit a choice
Consent is remembered in this browser, for the application where the widget runs, until the tester changes it in the widget: the capture summary below the message (Screenshot on · Replay off, with Change) reopens the choices, and on a test-session token the same control reopens the consent card. With the inline checkboxes style there is no summary: the checkboxes under the message are the choice. Changing a project's presentation style does not itself grant consent.
If the browser blocks site storage, the widget still honors the choice for the current page and asks again on the next visit.
Access and export
Reports and media belong to the project. Authorized dashboard users and account access keys can retrieve them. Every plan includes JSON export of project data with a manifest of stored attachments. See Export and the Privacy Policy.