Privacy Policy

Effective date: 22 October 2026

This policy covers Tender Radar. For Spec Sheet Normaliser, read the Spec Sheet Normaliser privacy policy.

This policy describes how the Tender Radar Chrome extension ("Tender Radar", "the extension"), published by Priyank Rajput, handles your data. Tender Radar has no server. The extension itself sends nothing to the developer. The only data the developer ever receives is what Dodo Payments shares with a seller when you buy a Pro license: your name, email address and purchase details, used to support that purchase and nothing else.

1. What data the extension accesses

• Page content on bidplus.gem.gov.in. On GeM's bid listing pages the extension reads the bid cards (bid number, items, quantity, department, end date and the bid document link) to highlight those that match your keywords. To run "Scan all of GeM" it also reads the security token the GeM page itself uses for its search requests. It runs on no other website.
• Public bid documents. When you click "Extract", the extension downloads that bid's PDF from bidplus.gem.gov.in and reads 20 fields from it (such as end date, EMD amount and turnover requirements).
• Your keywords and settings. The keywords you enter, the ID of the spreadsheet the extension created, and, if you use the Advanced option, your Apps Script web app URL.
• Tracked bids. Bid number, items, end date and document link of the bids you track, used for deadline reminders.
• The one spreadsheet it creates. If you click "Connect Google Sheets", the extension uses Google's drive.file permission, which lets it access only files it created. It creates one spreadsheet named "Tender Radar" in your Google Drive, reads its bid-number column to find existing rows, and writes bid rows to it. It cannot see any other file in your Drive.
• A Google access token. Chrome's identity API holds the sign-in token used for the Google Sheets API. The extension uses it only to call that API and never stores it itself.

The extension does not access your GeM account details, your name, email address, location, browsing history or any other website.

2. Where data is stored

• In Chrome storage on your computer. Keywords, the spreadsheet ID and the Apps Script URL are kept in Chrome's sync storage. If you have turned on Chrome Sync, Chrome copies them to your other Chrome browsers through your Google account, as it does for any extension's settings. Tracked bids are kept in Chrome's local storage on this computer only. Search results and extracted fields are held in memory and are gone when you close the side panel, unless you send them to your sheet.
• In your own Google Drive. Bid rows you send are stored in the spreadsheet in your Drive (or in the Google Sheet behind your own Apps Script URL). You own and control that spreadsheet.

3. What is transmitted, and to whom

• To GeM (bidplus.gem.gov.in). "Scan all of GeM" sends your keywords as search requests to GeM's own bid listing endpoint, from the GeM tab open in your browser and with that page's session, the same requests the page sends when you search it yourself. Scans are rate-limited: one request at a time, at most 10 result pages per keyword and 100 requests per scan. "Extract" downloads public bid PDFs from GeM.
• To Google. When you send a bid to your sheet, its row (the bid's card details, document link, the 20 extracted fields and the time sent) goes to the Google Sheets API (sheets.googleapis.com), written to your own spreadsheet. If you instead saved an Apps Script URL under Advanced, the row is posted to that URL, which is a script you deployed in your own Google account.
• "Add to calendar". If you click it, Google Calendar opens in a new tab with the bid's number, items, department, end time and document link filled in as a draft event. Nothing is saved unless you save the event.
• To the developer: nothing from the extension. It has no server, sends no data to the developer, and contains no analytics, tracking, advertising or crash-reporting code. If you buy a Pro license, Dodo Payments shares your name, email address and purchase details with the developer as the seller.

Deadline reminders are shown by Chrome's own notification system on your computer.

Tender Radar Pro. When you activate a Pro license, the extension sends the license key and a device label ("Tender Radar for Chrome") to Dodo Payments, the merchant of record that sells Pro, to validate the purchase. It sends the key again to re-check it about once a week, and when you click "Remove key". The key is kept in Chrome's sync storage with your other settings. No other data goes to Dodo. Buying Pro happens on Dodo's own checkout page, under Dodo's privacy policy, and Dodo shares the order, including your name and email address, with the developer as the seller.

4. No sale or sharing

Your data is not sold, rented or shared with anyone. It is not used for advertising, for purposes unrelated to the extension's single purpose, or to determine creditworthiness or for lending.

5. Google user data: Limited Use

Tender Radar's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Information received from Google APIs is used only to create and update the Tender Radar spreadsheet in your Drive. No person reads it, and it is not transferred to anyone.

6. Your choices: revoking access and deleting data

• Disconnect. In the side panel, "Disconnect" makes this browser forget the spreadsheet and clears Chrome's cached Google tokens.
• Revoke Google access. Remove Tender Radar from your Google account's third-party connections at myaccount.google.com/connections.
• Delete the spreadsheet. Delete the "Tender Radar" spreadsheet from your Google Drive like any other file.
• Delete everything else. Uninstall the extension from chrome://extensions. Chrome then deletes its stored keywords, settings and tracked bids.
• Apps Script option. Delete or un-deploy your own Apps Script web app in your Google account.

7. Children

Tender Radar is a business tool for GeM suppliers and is not directed at children.

8. Changes to this policy

If this policy changes, the new version will be posted on this page with a new effective date. Any change in how the extension uses your data will be made only after updating this policy.

9. Contact

Priyank Rajput, darpan1871@gmail.com