legal · last updated Oct 2026
Short version: diagnosis history is saved in your browser, while submissions are sent to the backend for analysis. Here's the full version.
Nothing tied to you, personally. Specifically:
localStorage. This data is not uploaded to a DebugAI history database and is not synced between devices or browsers.When you use the debug tool, the requirements, code and console error you paste in are sent to DebugAI's backend — a small Cloudflare Workers function — which forwards them to Cloudflare's AI inference service to generate a diagnosis. That's the entire round trip.
DebugAI does not save your submission to a server-side history database. However, when a diagnosis
completes, the browser's History feature saves a local copy so you can reopen previous results.
Each saved entry can include your filename, requirements, original code, console error, diagnosis
results, a short title, a bug count and a timestamp. History keeps up to 12 entries in the current
browser's localStorage; older entries may be removed as new ones are added. Anyone with
access to your unlocked browser profile may be able to view that history.
You can remove an individual history entry or use Clear all in the History panel. Clearing browser site data or local storage also removes saved history. History is stored on your device, but the code, requirements and console error are still sent to DebugAI's backend for analysis when you submit them. The backend forwards the request to Cloudflare's AI inference service; Cloudflare's handling of that processing is governed by Cloudflare's own privacy policy.
Avoid pasting real secrets — API keys, passwords, tokens — into the code or console fields. If you submit sensitive material, remember that it may also remain in your local diagnosis history until you delete that entry or clear your browser data.
This site is hosted on GitHub Pages. Like any web host, GitHub's servers see standard connection information (IP address, browser type, request timing) as part of serving the page — DebugAI has no access to those logs. See GitHub's Privacy Statement for how they handle it.
This policy may change as DebugAI grows — the date at the top reflects the last update. Questions about it can go to the issue tracker on GitHub.