Privacy Policy — Trace Viewer for LangSmith

Trace Viewer for LangSmith (the “Extension”) is a browser extension that opens and renders traces from a LangSmith instance selected by the user. It also offers an optional, user-initiated workflow for sending a selected trace to an evaluation service to compare model replays. This policy explains what information the Extension accesses, how it is used, where it is sent, and the choices available to users.

Summary

Ordinary trace viewing happens between the user’s browser and the LangSmith instance the user configures. Trace Viewer has no advertising or analytics. If the user explicitly starts an evaluation, the Extension sends the selected trace and evaluation settings to the evaluation service configured by the user. The evaluation service may retain the submitted trace and generated evaluation artifacts.

Information the Extension accesses

To display a user-selected trace, the Extension may access:

• LangSmith organization, project, run, and trace identifiers;
• trace inputs and outputs, including messages, reasoning content, tool calls, and tool results;
• run metadata, tags, status, errors, timestamps, duration, token usage, and cost information; and
• the URL and structure of the configured LangSmith page, as needed to add Trace Viewer controls and identify the selected trace.

Trace content may contain website content, personal communications, personally identifiable information, confidential business information, or other sensitive information if that information was recorded in LangSmith by the user or the user’s organization.

Ordinary trace viewing

The Extension uses the user’s existing authenticated browser session to request trace data from the exact LangSmith origin the user configures and approves. Trace data is rendered locally in the browser. Ordinary viewing does not send trace content to the Extension publisher or to the evaluation service.

The Extension does not use the Chrome cookies API, inspect authentication cookies, or store usernames, passwords, API keys, or session cookies. The browser may automatically attach the relevant session credentials to requests made to the configured LangSmith or evaluation-service origin.

Optional “Eval trace” feature

The evaluation feature is optional and runs only after the user opens the Eval trace dialog and submits an evaluation. When the user does so, the Extension sends an HTTPS request to the evaluation-service origin configured in the Extension’s settings. The default evaluation-service origin in version 0.4.0 is https://trace-evals.vibe-box.ai.

The submitted evaluation request includes:

• the complete set of raw runs for the selected trace;
• the models selected by the user;
• the trace title and project name;
• the repository URL and starting Git commit, when available; and
• the evaluation turn limit.

The evaluation service uses this information to create an evaluation arena, prepare isolated repository checkouts, run the selected models, and display the resulting comparison. To perform that work, the evaluation service may communicate with the specified GitHub repository and with the selected AI model services. Data sent to those services is also governed by their respective terms and privacy policies.

Storage and retention

The Extension stores the configured LangSmith origin and optional evaluation-service origin in Chrome’s local extension storage until the user changes them, clears extension data, or uninstalls the Extension. Trace content used only for viewing is held in browser memory as needed to display the active trace and is not persisted by the Extension in Chrome storage.

When the user starts an evaluation, the configured evaluation service may persist the submitted request, reference trajectory, arena state, candidate trajectories, model outputs, logs, repository workspaces, and related evaluation artifacts. The current service does not enforce an automatic deletion period. These artifacts remain until removed by the evaluation-service operator or the underlying service storage is deleted. Users should not submit a trace for evaluation unless they are authorized to send and process its contents.

How information is used

Information accessed by the Extension is used only to:

• add an open-in-viewer control to LangSmith trace rows;
• retrieve, render, search, filter, and navigate the trace selected by the user;
• remember the user’s selected LangSmith and evaluation-service origins; and
• when explicitly requested by the user, create and display a multi-model trace evaluation.

The Extension does not use accessed information for advertising, profiling, creditworthiness, lending, or purposes unrelated to trace viewing and user-requested evaluation.

Sharing and sale of data

The Extension does not sell user data. It does not send trace data to advertising networks, data brokers, or analytics providers. Data is transmitted only to the user-configured LangSmith origin for trace viewing and, when the user explicitly starts an evaluation, to the configured evaluation service and the service providers needed to perform that evaluation.

Analytics and tracking

The Extension contains no analytics, telemetry, tracking, or advertising code.

Permissions

• Optional site access: Requested only for origins chosen by the user. It is used to add trace controls, make same-origin LangSmith requests, and communicate with the configured evaluation service.
• Tabs: Used to locate the configured LangSmith tab, open or focus the packaged Trace Viewer, avoid duplicate viewer tabs, and open an evaluation arena.
• Scripting: Used to register the Extension’s packaged content scripts on the user-approved LangSmith origin.
• Storage: Used to save the configured LangSmith and evaluation-service origins locally.

All executable JavaScript and CSS used by the Extension is included in the submitted package. Network responses are treated as data; the Extension does not fetch or execute remote JavaScript or WebAssembly.

User choices and controls

Users can decline site-access requests, change configured origins, revoke site access in Chrome, avoid using Eval trace, clear the Extension’s stored settings, or uninstall the Extension. Without access to a LangSmith origin, the Extension cannot add trace controls or retrieve traces from that deployment.

Security

Trace Viewer limits site access to origins approved by the user and relies on each configured service to enforce authentication and authorization. No software or network transmission can be guaranteed to be completely secure. Users should review trace contents and their organization’s policies before starting an evaluation.

Children’s privacy

Trace Viewer is a developer tool and is not directed to children under 13. The publisher does not knowingly collect personal information from children.

Changes to this policy

This policy may be updated when the Extension’s functionality or data practices change. The “Last updated” date will be revised, and material changes will be reflected in the published policy and, when appropriate, the Chrome Web Store listing.

Contact

Publisher: Swair Shah
Email: swair.shah@circle.com