Jam Documentation
LoginTwitterHelp
  • Welcome to Jam
  • Get Started
  • Company
    • Mission and values
    • Security, privacy and compliance
  • Product Features
    • Instant Replay
      • Performance
      • Privacy
      • iFrame & canvas support
    • Video Screen Recording
      • Desktop Recording
      • Video blur
      • Video annotations
    • Screenshot
      • Full screen screenshot
      • Screenshot hover states
    • DevTools
      • Security
      • Network req/resp bodies
      • GraphQL
      • Jam.Metadata
    • Jam for Incognito
    • Mobile inspector
    • Keyboard shortcuts
    • Team Workspaces
      • Manage Seats in Jam
      • Workspace Discoverability
    • Security and compliance features
      • How to configure SSO for your organization
    • Jam for Customer Support
      • Getting started with Jam.js
    • Jam AI
      • AI policies
      • AI debugger
  • Integrations
    • Asana
    • ClickUp
    • Figma
    • GitHub
    • GitLab
    • Jira
    • Linear
    • Notion
    • Sentry
    • Slack
    • Azure DevOps
    • Fullstory
    • LogRocket
  • Downloads and Browsers
    • Browser support
  • Configuration
    • How to auto-deploy Jam organization wide
    • Configuring Jam for AI apps
    • How to run Jam only on some websites
    • How to ignore logs from Jam in the developer console
    • How to use Jam with local files
Powered by GitBook
On this page

Was this helpful?

  1. Product Features
  2. DevTools

Security

PreviousDevToolsNextNetwork req/resp bodies

Last updated 1 year ago

Was this helpful?

Why do I see "JAM_DOES_NOT_SAVE_SECRETS"?

We understand sensitive information can be present in network requests, which is why Jam scans all network requests for any possible sensitive information including tokens, cookies and PII. We filter out these fields on the client side so they never reach Jam's servers.

We remove any potentially sensitive fields from request headers, and (if in JSON), request bodies. This is done prior to Jam creation, so the Jam data you see on the page (with the JAM_DOES_NOT_SAVE_SECRETS strings as the values of these headers) has already been filtered before leaving your laptop. It does not reach Jam's servers.

In the resulting Jam, you will see JAM_DOES_NOT_SAVE_SECRETS in place of any possible secret information.

We prefer to over-filter than under-filter and are taking the route of being overly cautious, so sometimes you will see information filtered out that probably should not have been. Please help us improve our filtering accuracy by sending your feedback to hello@jam.dev.