dotpush – Privacy Policy
Last updated: 20 May 2025
dotpush is a Chrome extension that lets you push your own LeetCode® solutions to a repository in your GitHub® account.
We respect your privacy and collect no personally-identifiable information beyond what is strictly required for that single purpose.
1. What data does dotpush store?
| Data | Where it's stored | Why it's needed | When it's removed |
|---|---|---|---|
| GitHub OAuth access-token | Chrome Sync Storage (local only) | Authorises the extension to create/update files in your own GitHub repo. | Deleted when you click Logout or uninstall the extension. |
| GitHub username | Chrome Sync Storage | Displayed in the popup so you know which account is connected. | Same as above. |
| LeetCode solution code | RAM only (never persisted) | Sent to GitHub's REST API when you click Push to GitHub. | Discarded from memory after the request completes. |
dotpush stores nothing else (no email, browsing history, analytics, etc.).
2. How is the data used?
- Authentication
The GitHub Device-Flow OAuth returns anaccess_token.
dotpush saves it locally so you don't have to sign in every time. - Pushing code
When you press Push to GitHub, the extension reads the code you're viewing on the current LeetCode tab and uploads it—using the saved token—to the file<slug>.<ext>in yourleetcoderepository. - Repository maintenance
On first use dotpush can automatically create theleetcoderepository (public) if it doesn't already exist.
dotpush never shares, sells or transfers any data to third parties.
3. What data is sent to external services?
The only external calls are to api.github.com:
| Method & Endpoint | Purpose |
|---|---|
| POST /user/repos | Create the leetcode repo (first-run only). |
| PUT /repos/{user}/leetcode/contents/{file} | Create/update each solution file. |
| GET /user | Verify the token and obtain your username. |
All requests are authorised with your OAuth token and occur only when you authenticate or push a solution.
4. Remote code
dotpush does NOT download or execute any remote JavaScript, WebAssembly or other code at runtime.
All executable code is bundled inside the extension package reviewed by the Chrome Web Store.
5. Cookies & Tracking
dotpush sets no cookies, gathers no analytics, and includes no third-party tracking libraries.
6. Your choices
- Logout – Click Logout in the popup to delete the stored token & username.
- Uninstall – Removing the extension from Chrome deletes all stored data.
- Revoke token – You can revoke the token in GitHub:
Settings → Developer settings → Applications → Authorized OAuth Apps → dotpush.
By using dotpush you agree to this privacy policy.