Privacy policy

Trail — workflow recorder
Effective date: October 27, 2026

What Trail handles

During an active recording, Trail captures foreground activity in the starting browser window, including tabs you activate in that window. Captured evidence can include:

• Before-and-after screenshots, click coordinates, interaction targets, scrolling, navigation, and grouped typed text, including IME input.
• Page URLs and titles, visible page text, element labels, roles, selector candidates, frame information, and viewport information.
• Network request URLs, methods, timing, status, sanitized headers, and available bounded text or JSON request/response bodies. Binary and HTML response bodies are omitted.
• Console logs, warnings, errors, workflow notes, names, and goals you enter. File interaction metadata may include filenames; Trail does not independently upload your files.

Depending on the pages you choose to record, this evidence may contain personal identifiers, personal communications, health, financial, location, or other sensitive information. Trail does not seek these categories for a separate purpose. Clipboard contents are not read independently; pasted text can appear as input in a recorded workflow. Trail does not record microphone audio, screen audio, or continuous video.

Why the data is used

Data is used solely to create, review, edit, redact, and export the workflows you request. Network and console evidence helps explain the result of recorded actions. Trail does not sell data, use it for advertising, build advertising profiles, use it to determine creditworthiness, or train AI models with it.

Your controls and consent

Before the first recording, Trail presents a recording disclosure and asks you to allow local recording. Accepting that disclosure does not start capture by itself. You choose when to start, pause, resume, and stop. The recorder follows foreground tabs in the selected window; unrelated windows and unrelated background tabs are excluded. Requests associated with recorded actions can finish in the background.

Recognized password/payment fields, credential values, authentication headers, and cookies are masked or sanitized before persistence. You can add masking selectors, permanently redact screenshot areas, and exclude steps from exports. These measures cannot detect every private value. Pause for private activities and review all exported evidence before sharing it.

Storage, retention, and deletion

Recordings are stored in the extension’s local IndexedDB database. Settings and the disclosure acceptance flag use local Chrome extension storage; Trail does not use Chrome Sync for recordings. Temporary screenshot frame buffers stay in memory; only selected masked images are persisted. Recordings remain until you delete them or remove the extension. Browser restarts may retain committed evidence from interrupted recordings.

You can delete a recording and its stored evidence from the library. Uninstalling Trail removes its extension-local data. Downloaded exports are separate files; delete those separately. Trail does not add its own encryption layer to local recordings or exports. Their protection depends on your device, browser profile, filesystem, and any encryption you configure.

Exports and third parties

ZIP exports include Markdown, structured events, screenshots, page context, network/console evidence, and an offline viewer. Optional WebM exports are silent movies generated locally from screenshots. Exports can contain private information. Trail does not automatically transmit them to its developer, Cloudflare, or an AI service. If you choose to upload or share an export with another service or person, their handling is governed by their own policies and your choices.

The developer cannot access recordings stored on your device. If you voluntarily contact support or share a recording for troubleshooting, the recipient receives only what you choose to send. Avoid sending sensitive recordings.

This website

This website is hosted on Cloudflare Pages. Requests to the site are processed by Cloudflare and may involve ordinary connection and security information such as IP address, request URL, browser information, and timestamps. Website requests are separate from extension recordings. The site includes no advertising, analytics scripts, tracking cookies, remote fonts, or recording upload form. See Cloudflare’s privacy policy for its handling.

Limited use

Trail’s use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Workflow data is used only for Trail’s single purpose: creating and managing recordings you request.

Changes and contact

Changes to this policy will be posted at this URL with an updated effective date. For privacy questions or deletion guidance, use the developer support contact shown in Trail’s Chrome Web Store listing. Do not send recordings containing secrets.