This Privacy Policy explains how the DevClash app ("the app", "we", "us") handles information. DevClash compares developers using data those developers already publish on GitHub, Codeforces and LeetCode. The same text is shown inside the app under Settings → Privacy policy.
1. What we collect about you
Nothing. There is no sign-in, no user profile, no analytics, no advertising, no crash reporting, and no tracking or advertising identifier. DevClash operates no server and receives no data from your device.
2. What is stored on your device
The app keeps a small amount of state so it is useful the next time you open it. All of it lives in the app's own private storage on your device:
- Your optional GitHub personal access token.
- The handles you have recently compared.
- The Analytics cohort you have saved.
- The card you build on the Profile tab.
- Your choice of coding platform on the Code and Analytics tabs.
This is removed when you uninstall the app or clear its data. None of it is sent to us, because there is no "us" to send it to — DevClash has no backend.
3. What leaves your device
Only requests to the services whose public data the app is reading:
| Service | Why |
|---|---|
api.github.com | Public profile, repository and activity data for the GitHub tab. |
codeforces.com | Codeforces' public, documented API for the Code tab. |
alfa-leetcode-api.onrender.com | A community wrapper used for LeetCode, which publishes no official API. |
leetcode.com | LeetCode's own GraphQL endpoint, used as a fallback when the wrapper is unavailable. |
As with opening any website, those services can see your IP address and the request itself. They are operated by other people under their own privacy policies. The app sends them nothing about you beyond the request — no identifier, no device profile, and no account, because it has none.
4. Your GitHub token
It is stored on this device, sent to api.github.com in an
Authorization header and nowhere else, and never sent to us. You can remove
it in Settings at any time.
5. The people you compare
DevClash reads only what GitHub, Codeforces and LeetCode publish to anyone — the same data you would see logged out in a browser. Nothing about a compared developer is kept beyond a short-lived in-memory cache, which exists to respect rate limits and is gone when the app closes. The only thing that persists is the handle itself, in your own recent list on your own device.
6. Cards you share
A battle card or profile card is rendered on your device and handed to the system share sheet, so it goes only to the app you pick. DevClash does not upload it anywhere.
7. Permissions
The app requests internet access, and nothing else. It does not ask for your location, contacts, camera, microphone, photos or files.
8. Children
DevClash is not directed at children and does not knowingly collect anything from anyone, of any age.
9. Changes
If this policy changes, the updated version ships with the app update, this page is updated to match, and the date above changes with it.
10. Contact
Questions about this policy? Email jrevanth101@gmail.com.
DevClash is an independent app. It is not affiliated with, endorsed by, or connected to GitHub, Codeforces or LeetCode, and all trademarks belong to their owners.