Optional automatic failure diagnostics

Disclosure version: diagnostics-v1 · Prepared October 20, 2026.

When you enable Automatic failure diagnostics in Settings, Skool Copilot can send limited technical information about unexpected failures to its Supabase backend. This helps authorized support investigate a problem you raise in the Skool community and identify a correction. You do not need to submit another report. This choice is optional and separate for each installation; ordinary features do not require it.

What is recorded

Failure summaries are associated with your Copilot account and installation. They contain a random event ID; feature, technical stage and safe error code; first and latest occurrence times and repetition count; extension build and browser major version; an existing Cloud job ID or random operation ID when available; and a short sequence of technical failure stages. Small technical details may include HTTP status, whether a request was accepted, a count of discarded summaries, and whether a job reference represents only part of a repeated failure.

Diagnostic records exclude message contents, text you type, screenshots, page HTML, browsing history, cookies, passwords, access tokens, raw exception messages and raw request or response bodies. Existing account authentication and installation proof authenticate uploads; their secret values are not saved in diagnostic records.

Only unexpected failures at supported operation boundaries are recorded. Successful activity is not recorded by this feature. Ordinary validation, cancellation and temporary errors successfully recovered by the operation are excluded. There is no general session recorder, console capture or periodic search for errors.

Uploads and access

The first pending failure starts an approximately 15-minute collection window. Reports normally become available within 15–30 minutes while online, authenticated and the service is available. Sleeping browsers, offline devices, unavailable authentication and outages can delay them. Repeated failures are combined; a large queue uses several bounded requests sent one at a time. There is no daily reporting quota.

Summaries are access-controlled technical records, not end-to-end encrypted. Authorized backend processes and support operators can access them. Other browser accounts cannot read them through the diagnostics service. Support investigation happens when needed; receiving a diagnostic does not automatically start AI analysis or an investigation of your Skool activity.

Retention and controls

Pending summaries use separate temporary storage on this device, limited to 100 summaries and 128 KiB. They expire after seven days; local expiry is processed when the extension next handles diagnostics. Accepted server summaries expire 30 days after first receipt and are removed through bounded maintenance, so physical cleanup may occur later. Finite storage and expiry can discard evidence. Diagnostics are excluded from workspace backups, Plan sync and cross-device restore.

Turning collection off in Settings clears pending diagnostics and stops future collection and uploads on this device. An upload already in flight may already have reached the service. Off does not remove previously accepted server records or disable another installation. Logout, account changes and local reset clear pending diagnostics. Your optional disclosure acceptance remains part of the installation record; account-data access includes the diagnostic metadata, and account deletion removes associated diagnostic records.

Limits and delivery safeguards

Not every failure leaves evidence. Failures before login, unsupported operation paths, disabled collection, abrupt process termination, discarded summaries and expired data can leave gaps. Repetition counts can cover several operations; a representative job ID does not identify every affected operation. A missing record is not proof of success.

Diagnostics do not send, retry or reschedule messages, change a delivery outcome, or back up message contents. An uncertain delivery may already have succeeded and must not be automatically retried. Existing Cloud execution history, encrypted schedule retention and backup controls retain their separate purposes and rules.

For this separately enabled feature, this disclosure supplements older statements that no product diagnostics are uploaded. It does not change required account agreements or enable any other optional feature.