Last updated 16 September 2026 · applies to the GitScribe Chrome extension and the GitScribe MCP server
There is no GitScribe server. We operate no backend, no account system and no analytics, so there is nothing of ours in the path to collect anything with. Your settings stay in your browser profile. One feature — generating a README — sends the code you selected to a model provider you choose, and it is the only one that sends your code anywhere.
Nothing. GitScribe has no telemetry, no crash reporting, no usage metrics, no advertising identifiers and no cookies. We do not see which repositories you open, what you select, or that you installed it at all. We do not sell or share data, because we never receive any.
Everything GitScribe saves lives in your own browser profile, through
Chrome's storage API. It is readable only by this extension, is
removed when you uninstall it, and is never uploaded.
| Stored | Why |
|---|---|
| Forge access tokens (GitHub, GitLab) | Optional. Raises rate limits and reaches private repositories. Sent only to the forge the token belongs to, and never attached to any other URL. |
| Model provider API keys | Optional. Used for exact token counts and README generation. Sent only to that vendor. |
| Selections, exclusion presets, recent repositories | So a selection survives navigating around a repo. History is capped at 20 entries. |
| Model choice and theme | Preferences. |
Digests and generated READMEs are held in memory in the background worker and are lost when it restarts. Nothing is written to disk unless you press Save as file.
GitScribe talks to these hosts, and no others:
api.github.com and codeload.github.com — repository metadata, trees, files, pull requests. GitHub receives the request under its own privacy policy.gitlab.com, or the self-hosted GitLab host you configure — the same, for GitLab.127.0.0.1 — only if you enable Ollama. This never leaves your machine.Generating a README sends your selected source code to the model
provider you picked. Everything else in GitScribe keeps your code on your
machine; this feature cannot — the model has to read the code to describe it.
You are shown the file count and the estimated cost, and nothing is sent until
you confirm. Your code is then handled under that provider's privacy
policy and data-retention terms, not ours. If that is unacceptable, run the
analysis against a local Ollama model, which never leaves 127.0.0.1,
or use the raw digest, which needs no model at all.
storage — the settings listed above.sidePanel — the entire interface is a side panel.tabs — reads the URL of the active tab, so the panel can tell which repository you are looking at. It is not used to build a browsing history, and no URL is transmitted anywhere. Chrome offers nothing narrower that works: under activeTab, chrome.tabs.query() returns url: null. Decline it and the extension still works — paste a repository URL instead.GitScribe injects no content script into any page, and loads no remote code — everything that runs is inside the published package.
Digests are scanned for credential-shaped strings, which are redacted before the output is assembled, and what was redacted is reported so the redaction is visible rather than silent. This is a safety net, not a guarantee: review a digest before pasting it somewhere public.
GitScribe is a developer tool, is not directed at children, and collects no personal information from anyone.
Material changes will be published here with a new date, and — because the policy ships in the repository — visible in its git history.
Questions or a suspected privacy problem: open an issue at github.com/OWNER/gitscribe/issues.