What Berry records, and when it leaves your browser.

Last updated 17 July 2026

Berry is a browser extension for creating replayable bug reports. It does not require an account and does not upload a recording until you choose to create a share link.

Data Berry records

While Berry is active on a webpage, it may keep a rolling record of the following information in that tab:

DOM content, page changes, page title, URL, viewport, and browser information.
Clicks, key presses, scroll positions, and ordinary form values.
Console logs, warnings, errors, failed assertions, and unhandled exceptions.
Network request URLs, methods, timing, status, headers, request bodies, response headers, and text or JSON response bodies.
An optional screen or window video, only when you explicitly start video capture and approve the browser's screen-sharing prompt.

The rolling DOM record covers approximately the previous 30 seconds. It stays in the tab's memory unless you choose to share it, and is discarded when the tab closes or reloads. After you explicitly start a recording, Berry temporarily keeps recording segments in local extension storage so the recording can continue across page loads and site navigation. Those segments are cleared after the report is created or the recorded tab is closed.

Redaction

Berry masks password fields and redacts credential-like values such as authorization headers, cookies, API keys, session identifiers, and tokens. Binary response bodies are not recorded, and text bodies are size-limited. Redaction is a best-effort safeguard: ordinary text, form values, page content, and response bodies can still contain personal or confidential information.

When data is uploaded

Nothing from a recording is uploaded until you press Stop & create report or Save the last 30 seconds. Berry then uploads the capture to create the share link you requested.

Storage and sharing

Capture files are stored privately in Vercel Blob. Short-lived capture metadata is stored in Upstash Redis. These providers process the data only to host and deliver Berry's service.

Berry creates a high-entropy share URL and does not add a login screen. Anyone who receives that URL can view the capture, so treat it like a secret. Capture access metadata expires after seven days by default, at which point the share URL stops working.

How Berry uses data

Recorded data is used only to create, store, and display the bug report you asked Berry to produce. Berry does not sell recorded data, use it for advertising, or use it to build advertising profiles.

Permissions

Berry requests access to webpages so it can record the DOM, console, network activity, and user actions for bug reports. It uses tab access to start and stop recording in the selected tab, local extension storage to remember recording state and retain active recording segments across navigation, and scripting access to collect page-level debugging information.

Your choices

You can avoid uploading data by not creating a share link, close or reload a tab to clear its rolling in-memory replay, close the recorded tab to clear an active recording, uninstall Berry at any time, and avoid recording pages containing information that should not be shared.

Children

Berry is a developer tool and is not directed to children.

Changes and contact

We may update this policy when Berry's behaviour or providers change. The latest version will remain at this URL. Privacy and support enquiries can be sent to dev@decodifi.uk.