Privacy Policy

Last updated: August 2026

TL;DR — CodeLedger never sees your code, your AI keys, or your GitHub token. Everything lives in your browser and your own GitHub repo.

1. Data Collection

By default, nothing is collected on our servers. CodeLedger runs entirely inside your browser. There is no account, no profile, and no advertising or tracking infrastructure.

There is exactly one thing that can be sent to us, and it is off unless you turn it on. If you enable Anonymous Usage Stats in Settings → Advanced, then each time a solved problem is committed the extension sends a single counter hit to counter.vkrishna04.me containing only the platform name and the extension version — for example { "platform": "leetcode", "version": "x.y.z" }. It carries no code, no problem, no token, no account, and no identifier of any kind, and nothing is sent while the setting is off.

The extension stores the following data only in your browser's local storage and IndexedDB:

So a second browser can pick up where the first left off, some of this is also written into your own repository, in a .codeledger/ folder beside your solutions: sync.json and config.json hold your settings and your friend list; behaviour-bank.json holds solve times, attempt counts, hint views and short summaries of what an AI review flagged, and Settings → Advanced turns that recording off; roadmaps.json and knowledge.json hold the roadmaps and insights written in the Behaviour Bank tab. Your GitHub token, your AI API keys and your vacation state are deliberately excluded and never leave local storage. Everything else in that folder is as public as the repository you chose.

2. Data Handling & Usage

Your data is processed strictly to provide the extension's core functionality: pushing code to your GitHub repo and requesting AI code reviews using your provided API keys. CodeLedger does not track your browsing activity, sell your data, or use advertising SDKs.

3. Data Storage & Security

All data remains on your device under your control, isolated by the browser's extension storage boundary — other sites and other extensions cannot read it. It is not separately encrypted at rest, so anyone with access to your operating system profile can read it, exactly as with the rest of your browser profile. You can delete all of it at any time by uninstalling the extension or clearing its local data.

4. Data Sharing & Third-Party Disclosure

We do not sell or share your data. Data is only transmitted to the third parties you explicitly configure:

Separately from anything sent to a third party: if your ledger repository is public — which is the point for most people, since it is a portfolio you did not have to write — then your solutions, your solve history, your streak badges and the generated GitHub Pages site can be read by anyone with the link. Making the repository private keeps all of it to you and anyone you invite.

The extension shows you this same list live under Settings → Privacy, computed from your actual configuration rather than written down here, so it cannot fall out of date with what the extension does.

5. Children's privacy

CodeLedger is not directed at children under 13. We do not knowingly collect information from children.

6. Changes to this policy

If we make material changes, we will update the "Last updated" date above and note it in the CHANGELOG.

7. Contact

Questions? Open an issue on GitHub or email github@vkrishna04.me.