Privacy Policy
SolveBase uses only the information needed to detect accepted submissions and save them to the GitHub repository you choose.
Effective August 17, 2026
Data SolveBase uses
SolveBase stores your selected coding-platform usernames, enabled-platform settings, GitHub repository name, synchronization state, and GitHub authorization token in Chrome extension storage on your device.
When you submit a solution, SolveBase reads the accepted submission's source code and basic problem metadata from the supported coding platform so it can create or update the matching file in your GitHub repository.
How data moves
Accepted solution source code is sent directly from the extension to GitHub through GitHub's API. SolveBase does not send source code to its own backend and does not use it for analytics, advertising, profiling, or model training.
SolveBase never sends coding-platform cookie values to GitHub or to the SolveBase OAuth service. Chrome supplies those cookies only to requests made to the same coding platform that created them.
The OAuth service at solvebase.dev performs the GitHub authorization exchange. OAuth state expires after five minutes, and the encrypted one-time token exchange expires after sixty seconds. The service also keeps short-lived rate-limit records to prevent abuse.
Browser permissions
Storage keeps settings and synchronization state. Identity opens the GitHub authorization flow. Cookies and scripting let SolveBase verify your signed-in sessions and read accepted source code on the supported coding sites. Alarms and notifications check GitHub authorization health and warn you when reconnection is required.
Sharing and sale
SolveBase does not sell personal data, share data with advertisers, or transfer data for unrelated purposes. Data is sent only to the coding platforms you use, GitHub for the requested repository updates, and the temporary OAuth service required to connect GitHub.
Control and deletion
Disconnecting GitHub removes the saved GitHub authorization token from the extension. Resetting SolveBase removes its local settings, cached synchronization state, and connection data. Files already committed to GitHub remain in your repository until you delete them there.
You can revoke SolveBase at any time from GitHub Settings under Applications.
Contact
For privacy questions or deletion help, open a support issue in the SolveBase GitHub repository.