Portal Login Filler · Chrome extension
Privacy Policy
Effective 17 October 2026
In short
- RMK Tech Services never receives, stores or sees your client list or passwords. Our licence server receives only your Google account’s email address and ID, to run your free trial and licence.
- Credentials are read from your own Google Sheet or Excel file, kept in memory only, and typed into the login page you have open when you choose a client.
- Your settings (never passwords) are kept in a small file in your own Google Drive, so they reach your other computers.
- No analytics, no advertising, no tracking, and no data is ever sold or shared.
Who we are
Portal Login Filler (“the extension”) is a Google Chrome extension published by RMK Tech Services, Ballari, Karnataka, India - 583101. It fills the User ID and Password on the login pages of GST, Income Tax, EPFO, e-Way Bill, banks, IRCTC, TTD and other ready-made portals (and any other portal you add) from a client list that you control. CAPTCHA, OTP and the Login button are always left to you.
Information the extension handles
Client credentials. The extension reads the Portal, Client, User ID, Password and Active columns from the client list you choose: either a Google Sheet in your own Google account, or an Excel (.xlsx) file you select on your computer. These values are used for one purpose only: when you click a client in the side panel, its User ID and Password are entered into the login form of the page open in your current tab. Passwords are never displayed in the extension.
Google account access. The extension uses the drive.file permission, which reaches only files you pick for it or that it creates for you. It cannot see, list or open any other file in your Google Drive. With it the extension: reads the Google Sheet you choose in Google’s own file picker; creates a sample client-list Sheet in your Drive, only when you click “Create sample Sheet”; and creates and updates one small settings file, Portal Login Filler settings.json, in your Drive (see “Settings” below). It never changes or deletes any other file in your Google account. Chrome manages the sign-in token.
Licence. The free trial and paid licence belong to your Google account, so the extension also asks Google for your email address (the userinfo.email permission). When the side panel needs to check your licence, the extension sends a Google sign-in token to our licence server at rmktechservices.com, which asks Google whose token it is. We store your Google account email address and ID, when your trial started, and when your licence ends. For each purchase we also store the Razorpay payment ID, amount and date. No client list data, passwords or page contents are ever sent. The extension remembers the last licence answer on your computer so it keeps working briefly offline.
Payments. Licences are paid on Razorpay’s secure payment page. Razorpay collects the payment details you enter (UPI, card or bank details, email and phone number) under its own privacy policy; we never see your card, UPI or bank details.
Website information. To know which portal is open, the extension reads the address (URL) of your active tab, and only for portal websites it has been given access to. On a portal’s login page it looks for the User ID and Password input fields, and any extra boxes you set up for that portal (such as a mobile number, filled from a column of your own client list), so that it can fill them. It does not read, collect or store other page content, and it never reads, clicks or fills CAPTCHA or OTP fields.
Keyboard lock status. To show Caps Lock, Num Lock and Scroll Lock indicators, the extension checks whether those three keys are on or off. It never records which keys you press or what you type.
PIN lock. If you turn on the optional PIN lock, the extension checks only whether your computer is in use, idle or locked (Chrome’s idle permission), so that it can lock itself again. Your PIN is never stored: only a scrambled check value (a salted hash) is kept with your settings, as described below.
Settings. Your portal list (the ready-made portals, portals you add, the login-field positions you set up with “Configure Portal”, extra fields and the client-list columns they read from, and Portal-column wordings you match to a portal), your client-list source, the chosen Sheet’s ID, name and tab name, and, if you turn on the PIN lock, its scrambled check value and lock timing are kept in two places: in the settings file Portal Login Filler settings.json in your own Google Drive, so they reach every computer where you use the extension with the same Google account, and in Chrome’s extension storage (synced by Chrome if you have Chrome Sync on). These settings contain no passwords, User IDs or other client-list data, and they never reach our servers. The name of an Excel file you pick, and Chrome’s reference to it, stay on that computer only; the file’s contents are never copied. The extension also remembers, on that computer only, which Settings sections you left open and whether a sample list is still waiting for your clients.
How long data is kept
Licence and payment records are kept while you use the extension and for as long as Indian tax and accounting law requires us to keep payment records. To have your licence record deleted, email us from the Google account it belongs to.
Loaded client records, including passwords, are held only in Chrome’s in-memory session storage. They are deleted automatically after 15 minutes, when you click “Clear loaded data”, or when Chrome is closed, whichever comes first. They are never written to disk by the extension. Settings remain until you change them or click “Reset to defaults”, “Forget file” or “Disconnect Google account”. The settings file and any sample Sheet stay in your Google Drive until you delete them there; deleting the settings file stops sync between your computers.
Sharing and transfer
The extension’s network connections are to Google’s own services, sheets.googleapis.com to read your Sheet (and create a sample Sheet when you ask), www.googleapis.com (Google Drive) to keep your settings file, Google’s file picker (on our pick-sheet page) to choose a Sheet, and oauth2.googleapis.com to revoke access when you disconnect your Google account, and to our licence server, which receives only what is described under “Licence” above. Your email address is shared with Razorpay only when you choose to buy a licence, so Razorpay can send your receipt. After a purchase we email you your licence details and invoice through our email provider, Resend, which receives your email address and those messages only. A User ID and Password reach a portal website only because the extension types them into that website’s login form at your request; you decide whether to submit it.
We do not sell data, use it for advertising, use it to determine creditworthiness or for lending, or allow humans to read it.
Google API Services User Data Policy
Portal Login Filler’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Your choices
- Click “Clear loaded data” in the side panel to remove loaded records immediately.
- Use “Disconnect Google account” in the extension’s settings, or remove access at myaccount.google.com/permissions.
- Click “Reset to defaults” in the extension’s settings to remove your portal changes from all your computers, then remove the extension from Chrome.
- Delete Portal Login Filler settings.json from your Google Drive to remove the synced copy of your settings and stop sync between computers.
How we protect your data
Client credentials and Google Sheet data. Data read from your Sheet or Excel file never leaves your computer except when the extension types a User ID and Password into the login page you chose. It is held only in Chrome’s in-memory session storage, which the extension restricts to its own trusted pages (websites and injected scripts cannot read it), and it is deleted automatically after 15 minutes or when Chrome closes. It is never written to disk, logged, displayed, or sent to our servers or to any third party. The fill script is injected only into the active tab, only when you click a client, and receives only that one client’s User ID and Password.
Encryption in transit. Every connection the extension makes, to Google’s APIs and to our licence server, uses HTTPS (TLS). The extension contains no remotely loaded code.
Google sign-in tokens. Tokens are issued and stored by Chrome’s built-in identity service, not by the extension. Our licence server uses a token only to ask Google whose account it belongs to, rejects tokens issued to any other app, and never stores or logs it. Google’s file picker runs on our page rmktechservices.com/portal-login-filler/pick-sheet, because Google’s picker can’t run inside an extension. The extension hands the token to that page only, inside your browser, so Google can show your Sheets; the page sends back only the ID and name of the Sheet you pick, and nothing goes to our server. The extension uses the access only to read the Sheet you picked, to create a sample Sheet when you ask, and to keep its settings file, and you can revoke it at any time.
Licence records. The few records we keep (email address, Google account ID, trial and licence dates, payment ID, amount and date) are stored in Google Cloud Firestore in Google’s data centres, encrypted at rest by Google Cloud. Database security rules block all access from browsers and apps; only our licence server can read or write them. Payment and email keys are kept in Google Cloud Secret Manager, never in code. Administrative access is limited to the owner of RMK Tech Services.
Your part. Because your client list contains real passwords, keep it private: share the Google Sheet only with people who need it, and store any Excel file in a protected location.
AI and machine learning
We do not use data obtained through Google Workspace APIs (including your Google Sheets data) to develop, improve or train generalised or non-personalised AI or machine-learning models, and we do not transfer it to anyone for that purpose.
Children
The extension is intended for business use and is not directed at children under 13.
Changes to this policy
If the way the extension handles data changes, we will update this page and its effective date before the new version is released.
Contact
Questions about this policy: hello@in.rmktechservices.com
RMK Tech Services, Ballari, Karnataka, India - 583101
