Security
How GSTRadar protects your GSTIN data
Each account sees only its own businesses. Portal access is approved with an OTP from the GST portal. Every sensitive action leaves a trail you can show a reviewer.
GST portal passwords are never stored, and every sensitive action is written to a tamper-evident audit log.
Portal access at a glance
- Who approves access
- The person connecting, with the OTP the GST portal sends to the registered mobile and e-mail.
- GST portal password
- Never asked for, stored or used.
- Session length
- Six hours by default, then it expires. You can disconnect at any time.
- Returns filed
- None. Filing stays on the GST portal, with you.
- Saving to the portal
- Only IMS actions, only if an administrator enables it, and each save is confirmed.
What the person connecting confirms
Before an OTP is sent, the user chooses how they are authorised and confirms the consent statements for that GSTIN. The text is stored with the connection.
The statements name your account, the GSP partner, what is read and how long access lasts. A longer session needs a second confirmation.
The consent register for each GSTIN can be downloaded as a CSV from the Health Check page.
Controls, area by area
Each control has a practical job: keep businesses separate, keep portal access consented and time-limited, preserve evidence and make sensitive changes reviewable.
| Control | What it means |
|---|---|
| GST portal access | |
| OTP consent, no portal password | Portal access, for every software, is authorised with the OTP the GST portal sends to the registered mobile and e-mail. GSTRadar never asks for, stores or uses GST portal passwords, and records the consent statement confirmed for each connection. |
| Filed data read through a GSP partner | Filed data is read through our GSP partner and checked. We never file returns or change registrations. If an administrator enables IMS saving, each IMS action is separately confirmed, recorded and attributable to a named user; otherwise IMS actions are exported for you to apply on the portal. |
| Time-limited portal sessions | A portal session lasts six hours by default and expires on its own. A longer session, where it is enabled, needs the taxpayer's separate agreement, which we record. You can disconnect at any time. |
| Access to your account | |
| Each account sees only its own businesses | Every read and write is limited to the signed-in account. Platform admins and View only logins use separate access paths. |
| Guarded authentication | Google sign-in where configured. E-mail passwords are stored as a one-way hash, sessions are signed and suspended accounts are blocked during access checks. |
| Evidence | |
| Tamper-evident activity history | Sensitive actions such as uploads, freezes, portal connections, admin changes and configuration updates are recorded with request metadata and chained hashes. |
| Immutable freeze snapshots | A frozen month preserves the approved reconciliation state. A later change becomes a visible, reasoned revision rather than a silent overwrite. |
| Storage and transport | |
| Private file storage | Uploaded GSTR-2B and purchase-register files are kept on our own server, not on a public link. Every download goes through the app and its access checks, so a file is never publicly readable. |
| Verified transport | All traffic is served over HTTPS, and production database connections require certificate verification. |
| Deletion | |
| Tracked deletion requests | Signed-in users can raise a deletion request from Settings. Each request is reviewed for identity, ownership, retention and legal holds before handling is confirmed. |
What a frozen month keeps
A defensible close keeps the source, the reconciliation result, the review decision and the activity trail linked together, months after the work was done.
A frozen month is more than a status badge: these four records stay together.
- 1. Identity
- A signed session and a role inside your account
- 2. Evidence
- Files, matches, decisions and exports
- 3. History
- Append-only, hash-chained sensitive actions
- 4. Freeze
- The approved state preserved as a snapshot
Plain statements about what we claim
- GSTRadar is independent and is not affiliated with, endorsed by or connected to GSTN or the Government of India.
- We do not claim security certifications we do not hold. Ask us anything about the control model before you connect a GSTIN.
- Sub-processors, including our GST Suvidha Provider PeriOne, database, storage, e-mail, monitoring, payments and hosting providers, with their locations, are listed in the Privacy Policy.
- Where each provider hosts data is set out in the sub-processor table in our Privacy Policy.
Review the control model before you connect a GSTIN.
Tell us about your team, retention or access needs and we will answer plainly.