Privacy Policy for CP Sync
Effective Date: July 28, 2026

This Privacy Policy describes how the "CP Sync" browser extension ("the Extension") handles your data. CP Sync is designed with strict privacy principles: it does not collect, transmit, or store any of your personal data on external servers owned by the developer.

1. Data We Collect and How It Is Used
   To function properly, the Extension requires certain information to be provided by you and accessed within your browser:

GitHub Personal Access Token & Account Details: To push code to your repository, the Extension requires your GitHub username, repository name, and a GitHub Personal Access Token (PAT). This data is used exclusively to authenticate API requests directly to GitHub.

Submission Data: The Extension reads problem metadata (such as problem name, ID, and URL) and your submitted code from supported competitive programming websites (e.g., Codeforces, LeetCode, CodeChef, etc.) when you receive an "Accepted" verdict. This data is used solely to construct a commit and push it to your connected GitHub repository.

1. Data Storage
   All settings, including your GitHub Personal Access Token, repository details, and push history, are stored locally on your device using your browser's native storage API (chrome.storage).

No Developer Access: The developer of CP Sync has no access to your token, your code, your local storage, or your push history.

Data Export: If you choose to use the "Export settings" feature, your Personal Access Token is deliberately excluded from the exported file to prevent accidental sharing or leaks.

1. Third-Party Services
   The Extension communicates directly with third-party services to fulfill its core functionality:

GitHub API: Your submission data and authentication token are transmitted securely via HTTPS directly to the GitHub API (api.github.com) to create commits in your repository. You are subject to GitHub's Privacy Policy when interacting with their services.

Supported Platforms: The Extension runs content scripts on supported competitive programming platforms to read the public problem data and your solution code.

1. Data Sharing and Telemetry
   No Telemetry: The Extension does not include any analytics, tracking scripts, or telemetry. We do not track how you use the Extension.

No Data Sharing: We do not sell, rent, or share any of your data with third parties. All data transmission occurs strictly between your browser and GitHub.

1. Permissions Justification
   The Extension requests the following browser permissions for these specific reasons:

storage / unlimitedStorage: To securely save your configuration settings and push history locally.

host_permissions (e.g., ://.codeforces.com/, ://api.github.com/*): To read your submission status on supported coding platforms and transmit the code to the GitHub API.

activeTab / scripting: To support the "Autofill" feature in the Manual Push tab, allowing the Extension to read problem metadata from the currently active tab.

notifications: To provide brief, non-intrusive status alerts when a push succeeds or fails.

1. Changes to This Policy
   We may update this Privacy Policy from time to time if the Extension's features change or if required by browser extension store policies. Any changes will be reflected by updating the "Effective Date" at the top of this document.
2. Contact
   If you have any questions or concerns about this Privacy Policy or how CP Sync handles your data, please contact the developer by opening an issue on the CP Sync GitHub Repository.