09
Website and browser-extension diagnostics, API error monitoring, and service logs
Public website analytics is described in the section above. Separately, where error monitoring is enabled, a browser error that reaches the marketing error hook is reduced to a fixed route category, a generic error label, and bounded code stack locations before it is sent. Form and input values, request and response content, headers, cookies, query strings, and prompt or response text are excluded, and reports are sent without cookies or credentials. Where Sentry is configured for the Control API, standard server-side request error monitoring can process error messages and stack traces, request methods, route and path details (which can include query strings), route metadata, request headers that may include authentication or cookie values, and parsed cookies. The Sentry SDK can filter some network identifiers, but the Control API currently applies no application-owned header allowlist or before-send scrubber. The exact context depends on the error and SDK processing.
Our servers write operational logs to operate and troubleshoot the Services, and the application logger sends them to Better Stack when that integration is configured. The gateway logger rejects fields named for content, messages, responses, credentials, and similar sensitive values; other service code is designed to log operational facts while excluding customer content. Where Promptwatch crawler logging is enabled, the marketing server forwards requests presenting a recognised AI crawler user-agent. These records contain the request time, method, path, response status and content type, crawler IP address, hostname and user-agent string. Query strings and referrers are excluded.
When a user explicitly chooses Send diagnostic report in our browser extension, the extension sends us a one-off report containing its version and current enrolment, protection mode, policy, and upload-queue status. We associate the report with the authenticated organisation and browser installation and record the source network address. Prompts, responses, page addresses, and file contents are excluded. We use the submitted report to investigate support issues and improve service reliability and security.