Privacy policy

Your preparation data stays in your browser.

Leet Progress is a local-first LeetCode interview-preparation companion. It does not use a cloud user database. Personal preparation data is processed and stored in your browser profile so the website and extension can show progress, recommendations, plans, revision state and readiness.

Last updated: August 20, 2026

LeetCode data handled locally

  • The current LeetCode problem URL/slug so Leet Progress can show matching company intelligence.
  • Your solved-problem history when you use automatic history reconciliation on LeetCode Progress.
  • A submission result such as Accepted, Wrong Answer, Time Limit Exceeded or Runtime Error so local progress can update automatically.
  • A submission identifier, timestamp, runtime or memory value when LeetCode includes it, used only to deduplicate the same observed submission locally.

Preparation data stored locally

  • Solved and attempted problems, attempts and timestamps.
  • Target companies, interview plans and manual plan overrides.
  • Revision dates, confidence, revisit state and local notes/preferences.
  • Personal readiness and analytics derived from your local progress.

What is fetched remotely

  • The public company/problem catalog from leet.rajeet.in.
  • Catalog version and checksum metadata used to detect safe public-data updates.
  • Normal website resources when you visit leet.rajeet.in.
  • No personal progress is included in the public catalog requests.

Local website ↔ extension sync

  • Sync is limited to the exact Leet Progress website origin in the same browser profile.
  • The website and extension exchange versioned local mutations through the extension bridge.
  • There is no Leet Progress cloud synchronization backend and chrome.storage.sync is not used.
  • Portable backup/import is the user-controlled migration path between profiles or devices.

LeetCode authentication

For solved-history reconciliation, Leet Progress asks LeetCode for your own progress using your existing LeetCode session in the page you already opened. We do not collect your LeetCode password, copy authentication cookies, or send your LeetCode credentials to Leet Progress servers.

The solved-history request is sent to LeetCode itself. The resulting solved problem slugs are reduced to the local progress state needed for Leet Progress and remain in browser-local storage.

Sale, advertising and sharing

Personal preparation data is not sold. It is not shared with advertisers or rented to data brokers.

Leet Progress does not use personal progress for personalized advertising and does not upload hidden progress telemetry or remote user profiles.

LeetCode remains a separate third-party service. Requests needed to read your own progress or observe your own submission result stay within your existing LeetCode browsing session.

Retention and deletion

Local preparation data is kept until you remove it. You can delete extension data by clearing Leet Progress extension storage or uninstalling the extension. Website-local data can be deleted by clearing site data for leet.rajeet.in in your browser.

Uninstalling the extension removes its extension-local storage, but a separately stored website replica may remain until you clear the website's site data. Backups you export are files you control and must be deleted separately if you no longer want them.

Security and public catalog updates

The extension periodically checks leet.rajeet.in for public catalog metadata and downloads a new public JSON catalog only when its version/checksum changes. Downloaded catalog data is validated before it replaces the last known good local snapshot. Catalog data is never evaluated as executable code.

Questions or privacy requests

For privacy questions, data-handling concerns or deletion help, open a support issue in the project repository. Do not include passwords, cookies or other authentication secrets in an issue.

GitHub support issues ↗