Perseus Cloud / Telemetry

Small, bounded client-error telemetry.

The public site sends a limited error record only to help the operator diagnose broken routes and browser failures. It is not conversation, memory, advertising, or behavioral analytics.

Effective date: 2026-08-23 · Owner: Perseus Computing LLC

Fields sent

When the browser error beacon is enabled, it may send the error message, source, page path, line number, and user-agent string. The endpoint truncates message, source, page, and user-agent fields before relay. It is designed not to receive passwords, API keys, memory bodies, cookies, or authentication headers.

Do not put secrets in browser errors. A thrown exception or custom error message can contain information supplied by a page or extension. The beacon is bounded, not a guarantee that arbitrary browser error text is harmless.

Limits and destination

  • requests are accepted only from the public Perseus origin allowlist;
  • the request body is capped at 4 KiB;
  • each source IP is limited to 20 records per rolling minute; and
  • the API relays accepted records to the operator-controlled notification service when configured.

If the relay is unavailable, the page does not retry indefinitely and the error record may be dropped.

Opt out

Set localStorage key perseus-telemetry to off before browsing the site, or use the control below. The setting is local to that browser profile.

What this is not

This is not product-usage analytics, a session recording, an advertising tracker, or a substitute for the Cloud privacy policy. Authenticated Cloud request logging and billing records are covered by the service boundary, not by this browser beacon.

Questions

For telemetry questions or a deletion request, contact [email protected]. Do not include secrets or customer data in email.