Skip to content

Data collection and visibility

Understand what the CLI sends to Prism and what you, administrators, and Team viewers can see.

Read this page before connecting Claude Code or Codex. Prism needs the text of your work as well as usage measurements to provide evaluations and summaries. The terms and the privacy policy are linked at the bottom of the sign-in and sign-up screens.

The CLI and the plugins read the session records of Claude Code and Codex on your computer and send them to Prism in batches. A hook of either tool only notes that something happened; a background process then reads the records and sends them.

Information What is sent
Text you wrote Your prompts, your messages sent while Claude is working, and your answers to Claude’s questions
Text Claude wrote Claude’s replies and questions, the items of its to-do lists, and the descriptions of the tasks it hands to sub-agents
Usage and timing Models, token counts, request timing, and API errors
Tool activity The kind of each action (for example an edit), whether it succeeded, how long it took, and the repository-relative paths of files it edited
Test, build, and run runs The class of a shell command (test, run, build, lint, or type check) and its pass or fail result and counts, never the command text
Repository information The repository’s host, owner, and name, your branch names, commit identifiers, and for changed files their repository-relative paths, content hashes, and line and language statistics

The CLI does not send the text of shell commands or tool output, and it does not send the contents of your files. It keeps changed file contents in a private folder inside the Prism folder on your computer (objects; see CLI settings and files) to compute statistics, and prism uninstall removes that folder.

Prompt and reply text can contain code, paths, and anything else you typed or Claude printed. Text is sent as written, except for the masking below.

Before a text leaves your computer, the CLI or the plugin replaces recognized secrets with [REDACTED]. It recognizes private key blocks, API keys and tokens of several providers (Anthropic, OpenAI, GitHub, AWS, Slack, Google, Stripe), JSON web tokens, bearer tokens, passwords inside web addresses, and values assigned to names such as secret, token, password, or api_key. Masking follows these patterns. A secret in another form is not recognized, so avoid typing secrets into a prompt. A text longer than 2 MiB is cut to its first 2 MiB.

Your branch names are part of the repository information the CLI sends. The links Prism derives between a piece of work and a branch keep only a hash of the branch name, computed from the repository and the branch.

Available data depends on the connection and on what Claude Code writes. Records that cannot be sent wait on your computer and are sent later. The CLI and the plugins drop waiting records that are older than 14 days or that exceed 256 MiB in total, and prism status shows the unsent count. A retry does not guarantee that every item reaches Prism.

Collection and visibility are separate. The CLI sends the information above for your account; the web app decides who sees which part.

Who What they see
You Your own activity, prompts and replies, evaluations, usage, and coaching on your screens
An organization owner or admin Team screens of every Team in the organization, and the organization overview
A member with view access to a Team The Team screens of the Teams they were granted view access to
A member without view access No Team screens of that Team

Team screens show values for the Team and for each member: for example Prompt Score, task states, completion, cost, and usage. No letter grade is shown next to a person, and Team Performance does not read prompt text. The Team report does not show individual prompt text or repository paths. The Team Work screen can show the reviewer of a change and the file paths a task edited. An organization admin can switch those two items, and the quality mark, off in the organization’s Work display settings. Your own items are always visible to you.

See Team Console for the screens. Cost and score values on Team screens are estimates and proxies; they do not measure a person’s skill or contribution.

Prism records each opening of a Team screen with who opened it, which screen, and on what basis (Owner, Admin, or View access). Owners and admins read this under Organization → Records → Access log for the last 90 days.

Prism operators can ask you for consent to read your original text for a sample audit, appeal handling, or labelling. You see requests under Settings → Consents, and you can approve, decline, or revoke. A request can cover one case or the whole organization.

When you leave an organization, your Teams and view access end. The text of the sessions you ran there, its task titles and summaries, and its coaching are no longer shown to you.

  • One session: start Claude Code or Codex with PRISM_OFF=1, for example PRISM_OFF=1 claude or PRISM_OFF=1 codex. The hooks record nothing for that session.
  • Stop for now: run prism logout. It signs this device out on the server, deletes the stored token, and discards records that were waiting to be sent. Nothing is sent until you run prism login again, and what you do while logged out is not sent afterwards. The Devices tab in Settings also lets you log out a device; records received after a log-out are not stored.
  • Remove the hooks: run prism setup remove. Run prism setup to register them again.
  • Remove everything the CLI put on your Mac: run prism uninstall. See Install and update.

These steps stop later collection. They do not delete data that Prism already received.

Open Profile in the web app.

  • Withdraw closes your account. You leave your organization, and sign-in sessions, devices, and external sign-ins are cut off. Personal records are erased by the deletion process. Records left in the organization stay there. Withdrawing asks for your password and signs you out at once. An organization owner must transfer ownership or close the organization first.
  • Request deletion of all data asks to erase everything, including records left in the organization. After the request is approved you are signed out, and a mail tells you when the deletion is done.

For the terms that apply to your account and data handling, read the Terms of Service and the Privacy Policy linked at the bottom of the sign-in and sign-up screens.