Privacy · Chrome extension
What Bini Verifier sees, and what it sends.
Short version: the extension works only on LeetCode and GeeksforGeeks problem pages. It tells Bini when you solved the question you started, and it saves your accepted code to your notes. It never asks for your passwords, it doesn't look at the rest of your browsing, and it sells nothing to anybody.
Last updated: 17 November 2026
What this policy covers
This policy covers the Bini Verifier extension for Google Chrome. It works together with the Bini app, and everything it sends is stored in your Bini account. The app's own Privacy Policy covers that account, including how to delete it. Where the two overlap, they say the same thing.
The extension is built and run by Utkarsh Mathur, an individual developer in India. For anything in this policy, write to bini.dsa.app@gmail.com.
Where it runs
The extension can only read pages on leetcode.com, www.geeksforgeeks.org and practice.geeksforgeeks.org. Chrome itself enforces this limit. It can't see any other website you visit, your other tabs' content, your bookmarks or your browsing history.
What it sends to Bini, and why
Your pairing. You connect the extension by typing a one-time code generated in the Bini app. The code is exchanged for a device token, which the extension uses to identify your account from then on. The server also records when the extension was paired, when it last checked in, and its version number, so the app can show that it's connected.
Problem page addresses. When you start a question in Bini, the extension opens its problem page. When you submit, the extension sends the address of that page with the result, so Bini can check it was the right problem. If Bini didn't yet know the page for a question, the address you land on is saved to a shared list of question links. That list holds only the question and its public link, never who added it, so the next person goes straight to the right page.
The result of your submission. On LeetCode, the extension asks LeetCode, using your existing session in this browser, whether you made an accepted submission of this problem since starting it. That way a run of the sample tests is never counted. On GeeksforGeeks, it notices when you click Submit and reads the verdict GeeksforGeeks returns for that submission: the result, and how many test cases passed. It reads nothing else from that traffic. Bini stores the outcome, when it happened, and the short verdict text, such as "Accepted" or "63 / 63 test cases passed".
Your accepted code. When a submission is accepted, its code is saved to your notes for that question, along with the language and the runtime and memory the site reported. It comes from LeetCode's record of your submission, or from the code editor on the page. Code from failed submissions isn't saved.
Your solved LeetCode problems, only when you ask. If you choose to import your history in the Bini app, the extension reads the list of problems you have solved on LeetCode, using your existing session in this browser. It sends Bini only the problems' identifiers, such as two-sum. Other details in LeetCode's reply, such as titles, difficulty and totals, never leave the extension.
What it never does
- It never asks for, reads or stores your LeetCode or GeeksforGeeks password.
- It never sends your cookies or sign-in to Bini. Requests to LeetCode go out from your own browser, under your own sign-in, with the same security token LeetCode's own page uses, and the reply stays in the browser except for the items listed above.
- It never reads pages outside LeetCode and GeeksforGeeks.
- It never records keystrokes, mouse movements or your screen.
- It never runs ads, tracks you for advertising, or uses analytics or profiling tools.
- It never runs code downloaded from the internet. Everything it runs ships inside the extension.
What stays in your browser
The extension keeps a few things in Chrome's storage on your computer: your device token and account ID, the question you're working on and the tab it opened, when your last solve was verified, and the IDs of your recently finished questions. Pressing Disconnect deletes all of these except the list of finished question IDs. Removing the extension from Chrome deletes everything.
Who else handles the data
- Supabase — Bini's backend. It stores your account data and delivers the instant notice that a question was started. That notice contains no data: it only tells the extension to check with Bini.
- LeetCode and GeeksforGeeks — the extension talks to these sites from your own browser, as you, the same way the sites' own pages do. Bini sends them nothing.
We do not sell, rent or share data from the extension with anyone else. It is used only to verify your solves and keep your notes, never for advertising, including ads inside the Bini app, and never to decide creditworthiness or for lending.
The use of information received from this extension follows the Chrome Web Store User Data Policy, including its Limited Use requirements.
How long it is kept
Your verified solves and saved code are part of your Bini account and are kept while the account exists. The shared list of question links holds no personal data, so it isn't tied to any account.
Disconnecting and deleting
- Disconnect: press Disconnect in the extension, or disconnect it from the Bini app. The device token is cancelled on our server straight away, and the extension stops sending anything.
- Remove: uninstall the extension from Chrome to delete what it stored on your computer.
- Delete your data: in the app, go to Profile → Help & Support → Delete my account, or email bini.dsa.app@gmail.com. This deletes your pairing, your verified solves, your saved code and your import history, along with the rest of your account, as described in the app's Privacy Policy.
Security
Everything the extension sends goes over encrypted connections. The device token only lets the extension act on your own questions, and the database checks that on every request. If you think your token has been exposed, disconnect and pair again, and the old one stops working.
Children
Bini and its extension are not intended for children under 13.
Changes
If the extension starts collecting anything new, this page will be updated before that version is released, and the date at the top will change.
Not affiliated with anyone
Bini Verifier is an independent project. It is not affiliated with, endorsed by or connected to LeetCode, GeeksforGeeks or Google.
