LeetGitSyncPro Extension

Privacy Policy

Item Name: LeetGitSyncPro — LeetCode GitHub Sync (ID: hnodlnenefihpeddipeidjhkailjmjli)

Developer: Garam Softwares • Last Updated: August 27, 2026 • Effective Date: August 27, 2026

Summary: LeetGitSyncPro is an open-source, client-side developer productivity extension built with a strict privacy-by-default architecture. All authentication credentials, repository configurations, and problem data are stored locally on your device with AES-256-GCM encryption. We operate zero telemetry, zero advertising trackers, and never transmit, store, sell, or monetize your personal data on any remote developer server.

1. Introduction & Developer Identity

This Privacy Policy explains the privacy practices and user data handling protocols for LeetGitSyncPro — LeetCode GitHub Sync ("LeetGitSyncPro", "we", "us", "our", or "the extension"), developed and maintained by Garam Softwares (Developer Contact: garamsoftwares@gmail.com, Website: https://synccode-pro.pages.dev, Jurisdiction: India).

This policy applies to your installation, access, and use of the LeetGitSyncPro Chrome Extension downloaded from the Google Chrome Web Store. By installing or using LeetGitSyncPro, you acknowledge that you have read and understood the practices described herein.

2. Single Purpose & Core Functionality

In accordance with Google Chrome Web Store policies, LeetGitSyncPro has a single, clear purpose: to automatically commit and synchronize accepted coding problem solutions and structured Markdown documentation from supported competitive programming platforms to a user's personal GitHub repository.

Supported coding platforms include LeetCode (leetcode.com, leetcode.cn), Codeforces (codeforces.com), GeeksforGeeks (geeksforgeeks.org), HackerRank (hackerrank.com), InterviewBit (interviewbit.com), CodeChef (codechef.com), and CodeStudio / Code360 (codingninjas.com, naukri.com).

3. User Data Collection (What Information We Collect)

LeetGitSyncPro adheres to the principle of data minimization and collects only the minimal data strictly required to deliver its core synchronization functionality:

Data Category Specific Data Elements Collection Mechanism Where Stored
Authentication Credentials GitHub Personal Access Token (PAT), GitHub Username, Target Repository Name, Target Branch. User explicitly enters this information in the extension setup / options dashboard. Stored 100% locally in chrome.storage.local with AES-256-GCM encryption.
User Content & Code Accepted source code snippet, programming language (e.g. C++, Python, Java), problem title, slug, difficulty rating, topic tags, runtime (ms), memory (MB), and execution percentiles. Extracted locally from the active coding webpage DOM upon an "Accepted" submission verdict. Cached temporarily in local browser memory and chrome.storage.local until pushed to GitHub.
Website Content & Tab URLs Active tab URL on supported coding domains to identify the problem statement and verify submission status. Accessed via Chrome extension content scripts and activeTab API when visiting supported coding URLs. Processed in real-time in local browser memory; not stored permanently.
User Preferences & Config Selected directory naming structure, commit message format, auto-sync toggle state, and solved problems count. User configures preferences in the extension popup and options page. Stored locally in chrome.storage.local.
Optional Integration Data DSATracker API key and progress timestamps (only if the user explicitly enables DSATracker Cloud Sync). User enters DSATracker API key in settings. Stored locally in chrome.storage.local.

3.1 Categories of Data We DO NOT Collect

For absolute clarity, LeetGitSyncPro NEVER collects, accesses, or processes:

  • Personally Identifiable Information (PII): We do not collect your real name, email address, physical address, or phone number.
  • Financial or Payment Information: We do not collect or process credit card numbers, debit cards, bank account details, or payment credentials. Any optional supporter subscriptions on our website are handled externally by authorized third-party payment gateways (e.g. PayPal, Razorpay).
  • General Browsing History: We do not track websites you visit outside of the explicitly declared coding platform domains.
  • Personal Communications: We do not read, intercept, or access emails, messages, chats, contacts, or calendar entries.
  • Biometric or Health Data: No biometric, medical, or health-related data is collected or handled.

4. User Data Handling & Purposes of Use

We use the information collected exclusively to deliver the user-requested features of the extension:

  1. Authenticating with GitHub API: Using your encrypted Personal Access Token to authenticate requests made directly from your browser to https://api.github.com.
  2. Creating Repository Commits: Formatting your accepted code solutions and problem descriptions into organized folders (e.g., LeetCode/0001-Two-Sum/solution.cpp and README.md) and committing them to your selected GitHub repository.
  3. Displaying Local Progress: Calculating your solve count and displaying recent submissions on your local extension popup dashboard.
  4. Offline Queue Management: Retrying failed sync attempts automatically when your internet connection is restored.
  5. Optional Roadmap Sync: Forwarding problem solve status to dsatracker.in if you have explicitly configured a DSATracker integration.

4.1 Strict Prohibitions & Non-Permitted Uses

In accordance with Google Chrome Web Store User Data Policies:

  • We do NOT sell, rent, license, trade, or monetize user data to third parties under any circumstances.
  • We do NOT use or transfer user data for personalized advertising, retargeting, promotional marketing, or user profiling.
  • We do NOT use or transfer user data to evaluate creditworthiness, financial standing, or for lending purposes.
  • We do NOT use user data for any purpose unrelated to the core GitHub sync functionality.

5. User Data Storage & Security Measures

We take the security of your data seriously and enforce multi-layered client-side safeguards:

  • Local Sandboxed Storage: All credentials, solved problem counters, and settings are stored entirely on your local device inside Chrome's sandboxed storage (chrome.storage.local).
  • Client-Side AES-256-GCM Encryption: Sensitive credentials (such as your GitHub Personal Access Token) are encrypted at rest using industry-standard AES-256-GCM cryptography implemented via the native browser Web Crypto API. The decryption key is generated and stored locally in isolated extension storage.
  • Encryption in Transit (HTTPS / TLS 1.3): All network communications between the extension and external endpoints (e.g. GitHub REST API) are conducted strictly over encrypted HTTPS connections using modern TLS 1.3 encryption.
  • Zero Remote Developer Servers: Garam Softwares operates no central servers, intermediate proxies, or remote databases that receive, log, or store your tokens or source code. All operations occur client-side in your browser.

6. Data Sharing, Transfer & Third-Party Disclosures

LeetGitSyncPro does not share, sell, or transfer your personal data to third-party data brokers, advertising agencies, or marketing companies. Data is transmitted strictly to the external services necessary to execute your requested actions:

Third-Party Service Endpoint / Domain Data Transferred Purpose & Justification
GitHub REST API https://api.github.com Encrypted GitHub PAT (as Bearer token in request header), source code payload, commit message, and README file content. Required to create and update files in the user's specified GitHub repository.
Coding Problem Platforms leetcode.com, codeforces.com, geeksforgeeks.org, hackerrank.com, interviewbit.com, codechef.com, codingninjas.com Active page DOM content (read-only in your local browser). Required to detect submission verdicts and extract problem descriptions.
DSATracker (Optional) https://dsatracker.in Problem slug, difficulty rating, and completion status. Only sent if user explicitly enables DSATracker Cloud Integration.

LeetGitSyncPro contains no third-party telemetry, no Google Analytics, no tracking scripts, and no analytics SDKs.

7. Data Retention & User Data Deletion Rights

Because all data is stored locally in your browser:

  • Retention Period: Data remains stored locally in your browser for as long as the extension remains installed, or until you clear your browser data or disconnect your accounts.
  • Immediate Data Deletion: You can delete all stored access tokens, configuration settings, and submission logs at any time by clicking "Disconnect GitHub" or "Reset All Settings" in the extension options page.
  • Uninstalling the Extension: Uninstalling LeetGitSyncPro from your browser (via chrome://extensions) immediately and permanently purges all local storage and sandboxed data from your machine.
  • GitHub Repository Data: Commits pushed to your GitHub repository remain in your GitHub account under your full control. You may edit or delete repository contents directly on GitHub at any time.

8. Global Privacy Rights (GDPR & CCPA/CPRA Compliance)

We respect user privacy rights globally, including the European General Data Protection Regulation (GDPR) and the California Consumer Privacy Act / California Privacy Rights Act (CCPA/CPRA):

  • Right of Access & Transparency: You have the right to know what data is collected, stored, and processed (as detailed in this policy).
  • Right to Rectification: You can modify or update your repository names, folder formats, or tokens at any time in the settings.
  • Right to Erasure ("Right to be Forgotten"): You can wipe all stored data instantly by clearing extension data or uninstalling the extension.
  • Right to Data Portability: All synced code solutions and documentation are already stored directly in your personal GitHub repository in open Markdown and source code formats.
  • Non-Discrimination: We will never discriminate against you, restrict features, or alter quality of service for exercising your privacy rights.
  • "Do Not Sell My Personal Information": We do not sell or share personal information as defined by the CCPA/CPRA.

9. Permissions Justification (Chrome Web Store Least Privilege)

LeetGitSyncPro requests only the browser permissions strictly required to execute its single purpose:

  • storage: Needed to store user settings, folder preferences, and locally encrypted GitHub tokens.
  • alarms: Needed to schedule background retry intervals for queued submissions during temporary network interruptions.
  • activeTab: Needed to inspect the active problem page DOM and extract solution code upon user submission.
  • host_permissions (api.github.com, leetcode.com, codeforces.com, geeksforgeeks.org, hackerrank.com, interviewbit.com, codechef.com, codingninjas.com, dsatracker.in): Required to communicate with the GitHub API to push commits and read problem statement markup.

10. Children's Privacy (COPPA Compliance)

LeetGitSyncPro is a developer productivity tool intended for software engineers, students, and competitive programmers. The extension is not directed toward or intended for children under the age of 13. We do not knowingly collect, request, or maintain personal information from children under 13 years of age.

11. Google Chrome Web Store User Data Policy Compliance

Limited Use Disclosure: LeetGitSyncPro's use and transfer of information received from Google APIs / Chrome Web Store APIs to any other app will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

12. Changes to this Privacy Policy

We may update this Privacy Policy from time to time to reflect enhancements to our extension or modifications to applicable legal standards. When revisions occur, we will update the "Last Updated" and "Effective Date" at the top of this page. We encourage users to periodically review this Privacy Policy.

13. Contact Information & Privacy Support

If you have any questions, comments, feedback, or inquiries regarding this Privacy Policy or our user data practices, please contact us: