LeetToGit
100% Client-Side – Zero Telemetry
PRIVACY & DATA TRANSPARENCY

Privacy Policy for LeetToGit

Built by developers for developers. We believe your code, credentials, and browsing activity are strictly yours. LeetToGit operates with zero intermediary servers and collects zero tracking telemetry.

Effective Date: September 13, 2026 • Version: 1.1.0 • Architecture: Zero-Backend Client-Side

1. Zero-Backend Architecture (Our Core Principle)

Unlike traditional sync extensions that channel your authentication tokens and code through third-party Heroku or AWS proxy servers, LeetToGit runs 100% inside your browser:

  • Direct-to-GitHub Communication: Every network request originates in your local browser and communicates strictly with official GitHub API endpoints (https://api.github.com).
  • No Intermediary Gatekeepers: We do not operate any backend database, cloud function, or relay proxy. Your data never touches any server owned or operated by us.
  • Zero Man-in-the-Middle Risk: No third party has access to your repository structure, solved problems, or Personal Access Tokens (PAT).

2. Information We Do Not Collect

LeetToGit is architected with a strict privacy-first model:

✓
No Analytics or Tracking Telemetry

We do not track button clicks, popup open counts, IP addresses, user agents, or system fingerprints.

✓
No Third-Party SDKs

Zero advertising trackers, Google Analytics, Sentry, Mixpanel, or surveillance scripts are embedded.

✓
No Browsing History Inspection

We never inspect, record, or store URLs outside of detecting code submissions on the 9 explicitly declared platforms.

✓
No Data Monetization

We do not sell, rent, license, or trade your data to data brokers, recruiters, or commercial partners.

3. How Credentials & Data Are Handled

All configuration and state data is maintained exclusively inside your browser's private sandbox storage:

  • GitHub Personal Access Token (PAT): Your token is stored locally via chrome.storage.local. It is dispatched strictly as a standard Authorization: Bearer <token> header in direct HTTPS calls to api.github.com.
  • Local Solution Database & Statistics: Problem titles, solved timestamps, streaks, and heatmap matrices are saved exclusively on your local device for fast dashboard visualization.
  • Immediate Data Deletion: You retain complete control. Clicking "Disconnect GitHub Account" in the Settings tab instantly erases all stored tokens, repository bindings, and submission records from your computer.

4. Permissions & Host Justification

LeetToGit adheres strictly to the principle of least privilege required to perform multi-platform synchronization:

Permission Classification Plain-English Reason
storage Local Storage Persists your GitHub PAT, repository settings, platform toggles, and 30-day activity stats safely inside your browser.
alarms Background Schedules periodic local checks so queued solutions from temporary network disconnections are pushed once online.
activeTab Interactive Detects if your current tab is on an active problem page to power the context-aware "Manual Sync" button on popup open.
api.github.com/* GitHub API Allows direct REST API commits to your chosen GitHub repository without intermediary proxy servers.
9 Coding Platforms/* Content Script Required to inject DOM observers on LeetCode, GeeksforGeeks, Codeforces, HackerRank, CodeChef, AtCoder, HackerEarth, NeetCode, and InterviewBit to detect accepted code submissions.

5. Third-Party Services & Dependencies

The only external remote service contacted by this extension is the official GitHub REST API:

  • GitHub: Solution files, directory trees, and Markdown READMEs are pushed to GitHub under your user authorization. For details on how GitHub manages repository content, review the GitHub Privacy Statement ↗.

6. Open Source Transparency & Contact

LeetToGit code is completely readable and auditable. You can inspect manifest.json, service-worker.js, and all content scripts in the extension bundle to verify that zero external network connections are made.

For questions, policy clarification, or security audits, visit our developer portfolio at rehan.hindimea.com ↗ or engage with our community at AI Community ↗.