DebugPilot Privacy Policy

Policy version: 1.7.0
Last updated: October 16, 2026
Contact: sanjkakkoi@gmail.com

1. Purpose and scope

DebugPilot is a local web debugging recorder and evidence collector. You select a webpage and click Start to begin a debugging Session. Stop ends the Session. DebugPilot does not continuously monitor every browser tab or collect browsing history outside an active Session.

This policy describes DebugPilot 1.7.0. Recording, storage, comparison and analysis occur on your device. There is no DebugPilot backend, cloud storage, account, analytics, telemetry or advertising. DebugPilot does not sell debugging data or automatically upload it to its developer or third parties.

2. Evidence recorded during a Session

Depending on what Chrome and the webpage make available, DebugPilot may process and store:

The extension reads only evidence needed for the active debugging Session or local reports you open. Selected saved Sessions can be read for comparison. It does not use this information for advertising, credit decisions, unrelated profiling or background monitoring of other tabs.

3. Request Data, Response Data and full URLs

Request Data can include query name/value pairs and HTTP request bodies already supplied by Chrome DevTools Protocol: JSON, URL-encoded forms, text and readable multipart text fields. Multipart file parts are omitted. If Chrome does not provide a readable request body, it remains unavailable.

For an HTTP request that finishes loading, DebugPilot may request the body for that exact Chrome request ID. Response Data can contain bounded JSON, text, HTML, form-like content or a binary hexadecimal preview. Unavailable bodies and truncation carry a reason; they are not automatically classified as request failures.

WebSocket text/JSON and bounded binary previews may be retained. Where sufficient exact local protocol/schema evidence is available, bounded binary payloads may also be decoded into structured request or response fields. Unknown formats remain raw or unavailable rather than receiving guessed fields. A nearby received message is not assumed to be a response to a send merely because of time or ordering.

Full URLs and captured payloads are not automatically redacted by field name. Passwords, tokens, usernames, identifiers, secrets, API keys, authorization-like values or cookie-like values contained in a URL, request/response body, WebSocket message, log or screenshot can therefore be retained. Captured website content can also contain personal, financial, health, communications, location or other sensitive information, depending on the page you debug.

4. Mechanisms DebugPilot does not use

DebugPilot does not directly read password/input/textarea/select values, contenteditable user content or the clipboard. Action capture does not read placeholders, field names, autocomplete attributes, general page text or arbitrary DOM attributes to build evidence. Short labels come from the selected interactive control, not an entire menu or page.

DebugPilot does not read the browser Cookie Jar or collect full request/response headers, Cookie headers, Set-Cookie headers or Authorization headers as header records. Content-Type may be used transiently to decode a request. A cookie-like or authorization-like string inside a captured body, URL, Console message or screenshot is still possible; the exclusion of header and input mechanisms does not mean sensitive information can never appear.

Console handling uses safely converted Chrome-provided parameters. It does not fetch arbitrary RemoteObject properties with Runtime.getProperties. New Function Trace records do not capture function arguments or return values, or recursively inspect arbitrary thrown-object properties.

5. Actions, Function Trace and Source Preview

During recording, automatic Actions use canonical DOM/Canvas actions and short correlation windows to retain nearby evidence. WebSocket send instrumentation can provide a real observed send stack where available. A send attempt or likely relation is not proof that the server received or processed a message, and time proximity is not proof of causation. Inaccessible frames or cached native function references can limit observation. These limitations and suppressed evidence are retained where known.

Advanced Function Trace is user enabled and off by default. It can retain target/method names, call relationships, synchronous timing, return type, bounded exceptions and available Call Stack locations. It does not record function arguments or return values. Thrown objects, arrays and functions are opaque summaries. A natively identified Error retains bounded own data name/message fields, an allowed primitive or summarized cause, and the separately captured Call Stack; getters, arbitrary properties and Proxy internal fields are not read. Historical development records remain viewable without being rewritten.

Source Preview is user initiated. It retrieves requested JavaScript source through the attached page's Chrome debugger interface, not by fetching the source URL. Source can itself contain confidential application code or embedded sensitive literals. It is kept only in bounded temporary memory, not persisted in Session IndexedDB and not included as source code in exports. The temporary cache may disappear on eviction, Service Worker restart or extension reload. After Stop, only cached source is available; DebugPilot does not reattach to retrieve missing source.

6. WebSocket simulation and traffic controls

During recording, Send to Server transmits the payload you enter through the selected webpage's existing OPEN WebSocket connection to that website's actual server. This is an explicit user-directed transmission, not an upload to the DebugPilot developer. Sending successfully does not establish that the server accepted or processed the payload.

Inject to Client creates a simulated local message event for the webpage's client handlers. It is marked simulated and is not sent to the server. Outgoing/Incoming Normal, Block and Delay settings are application-level message controls, not TCP throttling, bandwidth throttling or device-level network latency.

Control changes, simulations, blocked/delayed messages, deliveries, pending-queue cancellations and resets can be saved as local Session evidence. Incoming interception is available only where the observer was installed early enough to control delivery safely; pre-existing or otherwise unverified connections do not receive a false claim of incoming control. Stop and lifecycle invalidation reset or invalidate controls and cancel pending queues. A fail-open lease stops modifying traffic if the extension loses contact. In restricted page environments an inert pass-through wrapper may remain until reload; this is not continued traffic control.

7. Local comparison and deterministic analysis

Session Comparison, Failure Timeline and Possible Causes operate on bounded snapshots of selected local Sessions. They do not add new capture, change original records or send data to external AI. Comparisons identify observed changes and explicitly retain missing/truncated evidence limitations. Possible Causes are explanations to validate, not guaranteed diagnoses. A missing event is not automatically proof that it did not happen.

8. Copying, exporting and sharing

Copy and export operations are initiated by you. Full-Fidelity reports are not automatically anonymized or safe for public sharing. Review the entire copied text or file, including collapsed details, before sending it to anyone. Share only with people you trust. DebugPilot does not choose recipients or automatically publish reports.

Export scope depends on the operation:

Exports show their limits and omissions. Unavailable, not captured, truncated and omitted evidence are different conditions, not automatically a successful or failed request. Provenance distinguishes the captured version, when reliably known, from the exporting version; unknown historical capture versions remain UNKNOWN. Event Time is distinguished from Observed/Processed Time where available. An offline file does not contain every original local record simply because it is called a report.

Exported HTML and JSON files are ordinary user-controlled files, not password-protected or encrypted by DebugPilot. Avoid recording or sharing production credentials or confidential content you are not authorized to handle. Removing the extension does not delete files or copied text you previously exported.

9. Local storage, limits and deletion

Settings, recent successful trace targets and Session metadata use Chrome extension-local storage. Evidence and Screenshot JPEG Blobs use extension-owned IndexedDB. These are local browser stores, not a DebugPilot cloud. DebugPilot does not add its own encryption layer to those stores; protect access to your device, browser profile and exports.

The latest 10 terminal Sessions are retained locally. Older terminal Sessions and associated IndexedDB evidence are pruned locally. Recording warns at 1 hour 50 minutes and stops at 2 hours or the estimated 200 MB Session limit. The 100 MB screenshot budget pauses new screenshots without deleting existing ones. Per-store, payload, message-frequency, action-window and export caps can limit retained or exported data; known suppression, truncation and stop reasons are disclosed.

Examples of current bounds include up to 500 Function Trace records per Session, bounded Request/Response structured output and binary previews, and a temporary Source Preview cache of at most 16 MiB/32 sources/64 previews. Limits protect local performance; recording and analysis are not guaranteed to observe every event. Uninstalling removes extension-owned local data according to Chrome behavior. Exported copies remain under your control.

10. Data use, security and contact

Debugging evidence is used only for DebugPilot's disclosed local debugging, evidence organization, comparison and report features. It is not sold, used for advertising or monetization, or automatically transferred to the developer. Websites you debug and servers you explicitly send to remain governed by their own policies and transport security. DebugPilot does not turn an existing insecure HTTP or WebSocket endpoint into a secure one.

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

This policy may be updated to reflect material changes. Questions about DebugPilot privacy may be sent to sanjkakkoi@gmail.com. Do not email private reports or credentials unless you intend to share those specific details.