⚡ Legit - LeetCode to GitHub Sync

Privacy Policy

Last Updated & Effective: August 25, 2026

Summary: Legit is an open-source, client-side Chrome Extension that synchronizes your accepted LeetCode solutions directly to your personal GitHub repository. We do not operate backend servers, we do not collect or sell personal data, and we do not track or profile users. All network communication occurs directly between your browser, LeetCode, and GitHub.

1. Introduction

This Privacy Policy explains how the Legit browser extension ("the Extension", "we", "our") accesses, uses, and stores information when you use the extension in Google Chrome or Chromium-based browsers.

Legit is hosted publicly on GitHub at Abhishek-Singh-2008/legit-extension.

2. Data We Access and Process

To provide automatic synchronization of accepted LeetCode solutions to GitHub, the Extension accesses the following data:

A. LeetCode Problem and Solution Data

How it is accessed: When you submit code on https://leetcode.com/problems/*, the extension's content script detects the "Accepted" verdict and retrieves the submitted solution and question details directly from LeetCode's public GraphQL endpoint (https://leetcode.com/graphql/) using your active browser session.

B. GitHub Account and Repository Information

3. Data Storage and Local-Only Architecture

All data stored by Legit is retained strictly locally on your computer using Chrome's local storage API (chrome.storage.local). No data is sent to external developer servers, analytics services, or third-party databases.

Data Item Storage Location Purpose
GitHub Personal Access Token (PAT) chrome.storage.local Authenticates direct API requests to the GitHub REST API (v3) to create commits in your chosen repository.
Repository & Branch Settings chrome.storage.local Remembers your target GitHub repository and branch preferences.
Sync History chrome.storage.local Maintains a local log of synced problems, timestamps, and commit links shown on your extension dashboard.
Submission Hashes (SHA-256) chrome.storage.local Local SHA-256 cryptographic hashes of synced code to prevent duplicate commits for identical submissions.

4. GitHub Personal Access Token (PAT) Security

Legit requires a GitHub Fine-grained Personal Access Token (PAT) or Classic Token with repo / contents: write scope to commit code to your repository.

5. Network Requests and Third-Party Services

Legit communicates strictly with two official domains:

  1. https://leetcode.com — To detect verdicts and fetch problem descriptions and your accepted code.
  2. https://api.github.com & https://github.com — To verify token access, list branches, and commit solution files to your repository.

There are no other network requests. The extension does not connect to any developer server, relay server, proxy, or telemetry service.

6. Extension Permissions Justification

Legit requests only the minimum permissions necessary to function:

7. Analytics, Tracking, and Advertising

8. User Rights and Data Deletion

Because all data is stored locally on your machine, you have complete control over your data at all times:

9. Children's Privacy

Legit is a developer utility for LeetCode practice and does not intentionally collect or process personal information from children under the age of 13.

10. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect extension updates or regulatory changes. Any modifications will be posted to this page with an updated effective date. Major changes will be documented in the repository's release notes.

11. Contact and Support

If you have any questions, feedback, or concerns regarding this Privacy Policy or the security of the extension, please open an issue on GitHub:

👉 GitHub Issues: https://github.com/Abhishek-Singh-2008/legit-extension/issues