Privacy Policy

Last updated 26 July 2026

The short version. Copilot Prompt Analyzer has no server, no account and no telemetry. Your chat history is read from local VS Code storage and stays on your machine. The only time any of it leaves is when you ask for a feature that needs a model, and that request goes through your own GitHub Copilot subscription — never through us.

Who this covers

This policy covers the Copilot Prompt Analyzer VS Code extension and this website, prompts.deb0.com. Both are published by Debajyoti Saikia as a personal, free and open-source project. It is not a GitHub or Microsoft product.

What the extension reads

The extension reads GitHub Copilot Chat history from the local storage that VS Code already keeps on your disk. That includes the prompts you wrote, the replies you received, timestamps, the model and mode used, tool-call counts, and the file paths referenced in a session.

It reads this data in order to group your prompts by topic and produce reusable prompts, reports and dashboards from them. Derived results are cached in VS Code's own extension storage on the same machine.

What leaves your machine

Feature Leaves your machine?
Reading and indexing chat history No
The dashboard and its 21 visualisations No
Prompt quality, repeated questions, paste hygiene No
Filtering, search, exports to disk No
Classifying prompts into areas Yes — to a model, via your Copilot subscription
Generating a working prompt or an AI report Yes — to a model, via your Copilot subscription
Asking a question about your history Yes — to a model, via your Copilot subscription

Model requests are made through the language-model API that VS Code exposes to extensions. The request is billed to, transported by, and governed by your GitHub Copilot subscription and its terms. The extension author never receives that data and has no way to see it.

Prompt text is truncated before it is sent, and the extension shows you the estimated token cost before each request so nothing is sent by surprise.

What we collect

Nothing. The extension has no analytics, no crash reporting, no usage counters, no unique identifier and no phone-home. It does not require an account and it does not ask for one.

The VS Code Marketplace reports aggregate install and rating counts to publishers. Those figures come from Microsoft, are not tied to individuals, and are governed by the Microsoft Privacy Statement.

This website

prompts.deb0.com is a static site. It sets no cookies, embeds no analytics, loads no third-party fonts or scripts, and has no tracking pixels. The single script on the page stores your chosen colour theme in your browser's own localStorage; that value never leaves your device and is not readable by anyone else.

The site is hosted on GitHub Pages. As the host, GitHub processes standard request data — including your IP address — to serve pages and protect the service. That processing is covered by the GitHub General Privacy Statement. Videos and images are served from the same origin, so watching the demo does not contact any other party.

Your data, your control

  • Everything the extension derives lives in VS Code's extension storage on your machine. Uninstalling the extension removes it.
  • There is nothing to request from us and nothing to delete on our side, because we hold nothing about you.
  • Because we operate no database of personal data, rights such as access, correction, portability and erasure have no records to act on. Requests about model usage should go to GitHub, and requests about site logs to GitHub Pages.
  • To clear the stored theme preference, clear site data for prompts.deb0.com in your browser.

Children

This is a developer tool and is not directed at children. We do not knowingly collect anything from anyone, of any age.

Exports are as sensitive as the originals

Generated prompts, instruction files and reports are distilled from your real chats, so they can contain code, file paths and anything you once pasted into a chat window. If you commit them to a repository or share them, read them first. Filtering to a single project before generating is the easiest way to keep scope tight.

Changes

If this policy changes, the date at the top changes with it, and the edit is visible in the public commit history of this page.

Contact

Questions about this policy? You can get in touch via the contact form on deb0.com, or open an issue on GitHub.