Metadata-only browser state for safer reports

IssueProbe uses a fixed metadata-only rule for browser state in its first release. Cookie, form, and local-storage values do not enter a report.

What the report can contain

Each browser-state item can contain only these facts:

• A name.
• A presence state.
• A size.

This small shape can show that a field or local setting exists without collecting its value. The browser and server reject undocumented fields and value-like fields.

What the report cannot contain

The browser-state section cannot contain a cookie value, form value, local-storage value, request header, request body, or response body. A website setting cannot add one of these fields.

A website owner can disable the browser-state category. If the owner enables it, the same fixed metadata-only shape applies on Free and Pro.

Why this rule matters

Browser values can contain passwords, payment data, account credentials, personal messages, and private customer records. A broad evidence switch would create unnecessary risk.

Metadata can still help an owner ask a precise source question. For example, the presence of a named form field can support a report about a missing step. It does not prove the cause by itself.

Review the complete evidence policy

The widget also supports a visitor-approved screenshot, bounded console errors and warnings, and failed or slow request metadata. Each category has a separate limit and can be disabled by the website owner.

Read the widget privacy rules for the exact fields. Read what browser evidence helps for practical examples.