TezGateway Helper

Chrome Extension Privacy Policy

Last updated: 08 Sep 2026 · Applies to the "TezGateway Helper" Chrome extension only. See our website privacy policy for tezgateway.com itself.

TezGateway Helper is a companion tool for merchants who already run a TezGateway account. It automates a task merchants otherwise did by hand: copying an authentication cookie or token from a payment platform they are already logged into, and pasting it into their TezGateway dashboard so that platform can be monitored from TezGateway.

What the extension reads, and when

The extension only reads data from a merchant-connected platform when the merchant explicitly triggers a "connect" / "fetch" action from the extension popup, or when the merchant clicks "Login with Gateway" to sign in. It does not run this collection silently or on a schedule without a matching stored request.

Authentication cookies / session tokens — from TataNeu, Amazon Pay, Google Pay, Paytm, PayNearby, and PhonePe, but only for the merchant's own account, on that platform's own site, at the moment the merchant asks the extension to connect it.
TezGateway login session — a user ID and session token issued by tezgateway.com when the merchant logs into the extension (via OTP-less "Login with Gateway", or scanning a session from an active tezgateway.com login).
Browser profile email (read-only) — used once, only during a Google Pay connect, to confirm the signed-in Chrome profile matches the merchant's registered email before capturing that session. The extension never modifies or signs into any Google account.
Extension preferences — theme (dark/light) and the configured gateway URL.

Everything above is sent to tezgateway.com only, over HTTPS, tied to the merchant's own TezGateway account. We do not sell this data, share it with advertisers or data brokers, or use it for any purpose other than operating the merchant's own dashboard.

What we do not collect

No browsing history outside the specific payment platforms listed above.
No passwords, keystrokes, form autofill, or personal files.
No microphone, camera, location, or contacts access — the extension never requests these.
No advertising identifiers or tracking pixels.

Why each permission is needed

Permission	Purpose
cookies	Read the merchant's own session cookies on a connected payment platform after they ask the extension to fetch them.
storage	Save the extension's login session and fetched data locally before it is sent to tezgateway.com.
notifications	Tell the merchant whether a connect/fetch action succeeded or failed.
activeTab / scripting	Run the fetch on the merchant page they explicitly opened, and detect logged-out states so we can prompt them to log in instead of failing silently.
alarms	Periodically check with tezgateway.com whether a merchant-initiated sync task is waiting, so the merchant isn't left in a stuck state after tab closes.
identity / identity.email	Read-only Chrome profile email check described above — Google Pay connect only.
Host access (tataneu.com, amazon.in, google.com, paytm.com, paynearby.in, phonepe.com, tezgateway.com)	Limited to the specific payment platforms this tool integrates with, plus tezgateway.com itself.

Data retention & deletion

Locally fetched data is kept in the browser's extension storage until replaced by a newer fetch or removed. On the server, data is tied to the merchant's TezGateway account and removed when they disconnect a merchant/platform, log out, or request account deletion by emailing us below. Uninstalling the extension clears all of its local browser storage immediately.

Your controls

Disconnect any single platform from the TezGateway dashboard's merchant management page at any time.
Log out of the extension from its popup, which revokes the extension session on our servers.
Uninstall the extension from chrome://extensions at any time — no residual background access remains once removed.

Contact

Questions about this policy or a data request: support@tezgateway.com