LeetCode to GitHub Sync gizlilik ilkeleri
LeetCode to GitHub Sync geliştiren: sandysam
LeetCode to GitHub Sync gizlilik ilkeleri
Last updated: 2026-07-05
This extension does not collect, transmit, or store any user data beyond what is explicitly described below.
The following data is stored only in your browser's local storage (browser.storage.local):
- GitHub Personal Access Token — Stored plaintext in your browser profile. It is never transmitted anywhere except directly to
api.github.comduring API calls. - GitHub Username — Used to construct API URLs.
- GitHub Repository Name — Used to construct API URLs.
- File Path Template — User preference for organizing files.
- Commit Message Template — User preference for commit messages.
- Submission History — A local log of synced submissions to prevent duplicates.
- Rate Limit Data — Internal state to prevent API abuse.
All of this data can be cleared at any time by removing the extension or clearing browser storage.
The extension communicates only with the following domains:
| Domain | Purpose | Data Sent |
|---|---|---|
|
api.github.com | Push code to your repository | Your code, commit messages, GitHub token (via Authorization header) ||
leetcode.com | Detect problem submissions on LeetCode pages | None — reads page content only |No analytics, tracking, telemetry, or third-party services are used.
Used to persist user settings (GitHub token, username, repo, templates) and submission history between browser sessions. Without this permission, users would need to re-enter credentials every time they restart the browser.
Required to run the content script on LeetCode problem and submission pages. The content script:
- Detects when a user submits a solution
- Extracts the problem title, number, difficulty, code, and language from the page
- Sends this data to the extension's background script for syncing to GitHub
The extension does not read or transmit any personal information from LeetCode beyond the problem and submission data needed for syncing.
Required to interact with the GitHub Contents API to create and update files in the user's repository. All requests are authenticated with the user's own Personal Access Token.
This extension uses no third-party services, analytics, or tracking. The only external communication is with GitHub's API, using credentials provided by the user.
- All data is stored locally in the browser and is deleted when the extension is removed.
- Submission history is capped at 500 entries and automatically pruned.
- GitHub tokens are cached in memory with a 5-minute TTL and then zeroized.
For privacy concerns or questions, contact: sandeepp.kumarr@outlook.com