1. Who we are and our two roles
GSTRadar is operated by Tax One Advisory (OPC) Private Limited, CIN To be published before launch, GSTIN 37AAMCT7977Q1ZX, registered office To be published before launch (“we”). We act in two roles.
Data Processor for the CA firm, accountant or business that holds a workspace (the “Customer”). When a Customer uploads purchase registers, GSTR-2B and other files, or connects a taxpayer's GST portal account, the Customer decides why and how the personal data in that material is processed. We process it only on the Customer's documented instructions, under our Data Processing Addendum.
Data Fiduciary for the personal data of our own users and website visitors: account, billing, security, support and website data. If you are an individual whose data appears in a Customer's workspace (for example a proprietor or a supplier), please contact that Customer first. We will forward your request to them and help them respond.
2. Data we process
- Account data: name, email address, password hash, Google sign-in identifier, role, workspace membership, and login and security events.
- Customer content: uploaded GSTR-2B files and purchase-register rows, reconciliation results, exceptions, follow-ups, freeze snapshots and exports; client names and GSTINs; supplier names, GSTINs, invoice numbers and amounts.
- GST portal data, only after the taxpayer authorises access with an OTP: filed GSTR-1, GSTR-3B, GSTR-2A and 2B, GSTR-9 and 9C, e-invoice data, cash and credit ledgers, notices, IMS documents, filing status, and the portal username. We do not collect or store GST portal passwords, and we do not store the OTP. Access is read-only, lasts up to 6 hours by default or the longer period (at most 30 days) the taxpayer agreed, and the taxpayer can end it by disabling API access on the GST portal. We keep the data to show the Customer its reconciliations, findings and reports, for the periods in section 7.
- Consent records: for each connection of a GSTIN to the GST portal, who confirmed the taxpayer's authority, the exact wording shown, the time, the duration and the IP address.
- Health Check outputs: scores, findings, estimates of tax at risk, interest and late fees, and reports in Excel and printable form.
- Client-portal invitee data: the name and email address supplied by the Customer.
- Billing data: billing name, GSTIN, address, plan, order and payment identifiers, amounts, tax split, and mandate and invoice records. We do not store card, UPI or bank credentials.
- Technical data: IP address, device and browser information, request metadata and the audit trail of sensitive actions.
- Support and contact messages and any attachments you send.
3. Why we process it
To provide the service the Customer asked for (reconciliation, Health Check, compliance monitoring, reports and the client portal); to authenticate users and keep workspaces separate; to bill and issue tax invoices; to prevent fraud and secure the service; to give support; to meet legal obligations (tax, accounting and cyber-incident reporting); and to improve reliability using aggregated technical metrics that do not include Customer content.
We do not use Customer content or GST portal data to train models, to profile or market to individuals, or to sell or share with third parties for their own purposes.
4. Legal basis and consent
We rely on the Customer's instructions (as processor) and, for our own data, on the user's consent given at sign-up or in the product and on the uses permitted by the Digital Personal Data Protection Act, 2023. When a Customer connects a GST portal account, the Customer confirms that it has the taxpayer's authorisation and the taxpayer gives the OTP voluntarily. You may withdraw consent at any time by disconnecting the portal, deleting data, or writing to us. Withdrawal does not affect processing already done.
5. Sub-processors and recipients
We use the providers below to run the service. Our GST Suvidha Provider (GSP), PeriOne, carries every call to the GST portal. The location column shows where each provider processes data; an entry reading “To be published before launch” is a detail we have not yet confirmed and will publish before the service opens to the public.
| Provider | Purpose | Data | Location |
|---|---|---|---|
| GST Suvidha Provider (PeriOne)Legal entity: To be published before launch | Reads the taxpayer's filed data from the GST portal after OTP authorisation, and relays optional IMS actions you separately confirm | Portal username, GSTIN, the OTP exchange, filed returns, ledgers, notices and IMS documents | To be published before launch |
| Server hosting provider | Runs the application, its PostgreSQL database and the private storage of uploaded files and reports, on one server | All workspace data, uploaded files and reports, and request logs | To be published before launch |
| Cloudflare | Domain name service; where enabled, the encrypted off-server copy of our backups (R2) | Encrypted backups, which Cloudflare cannot read | To be published before launch |
| Razorpay | Payments and recurring mandates | Order, payment and mandate identifiers, billing contact | India |
| Resend | Transactional email | Email address and message content | To be published before launch |
| Sentry | Error and performance monitoring (personal data scrubbed; session replay off) | Technical error data | To be published before launch |
| Sign-in (OAuth), only where you choose it | Email, name and Google account identifier | Global |
We notify Customers by email at least 30 days before adding or replacing a sub-processor that handles Customer content. We disclose data to authorities only when the law requires it, and we tell the Customer where we are allowed to.
6. Cross-border transfers
Some providers above may process data outside India. We transfer personal data only to the extent allowed by section 16 of the Digital Personal Data Protection Act, 2023 and any restriction the Central Government notifies, under written contracts that require equivalent safeguards.
7. Retention
We keep data only as long as the purpose needs it.
- Cached GST portal data: no longer than 90 days from the date it was fetched.
- Portal call logs: 12 months. The portal username is cleared 30 days after a GSTIN is disconnected or access expires.
- IMS working runs and action records: 12 months.
- Consent records: for the life of the workspace and 3 years after.
- Health Check reports, uploads and reconciliations: while the workspace is active. After a workspace is closed we offer a 30-day export window and then erase Customer content within 90 days.
- Audit log: 3 years, after which IP address and user agent are removed.
- Billing records and tax invoices: 8 years, because the law requires us to keep them.
- Security and infrastructure logs: at least one year, and at least 180 days within India as the CERT-In Directions require.
- Provider backups are overwritten within To be published before launch days.
Where the law requires us to keep something longer (for example billing records), we keep only what the law requires.
8. Security
We use encryption in transit (HTTPS); tenant-scoped access so a signed-in user reaches only their own workspace; hashed passwords; role-based access; a hash-chained audit log of sensitive actions; private object storage; rate limiting; scrubbed error telemetry; and limited, audited staff access. We describe encryption at rest only once our providers' settings have been verified. No system is perfectly secure. We hold no security certification at the date of this policy.
Report a security concern to To be published before launch.
10. Breach notification
If a personal data breach affects data we process for a Customer, we tell the Customer without undue delay and within 24 hours of confirming it, so the Customer can meet its own duties. We report to CERT-In and, when the rules apply, to the Data Protection Board of India, as the law requires.
11. Your rights
Where you are the data principal and we are the fiduciary, you may ask for a summary of your data, ask us to correct or erase it, withdraw consent, nominate another person to exercise your rights, and have a grievance redressed. Where a Customer is the fiduciary, we pass your request to the Customer within 3 business days.
Email To be published before launch. Until that mailbox is published you can write to taxoneadvisory@gmail.com. We acknowledge within 24 hours and respond within 15 days, and no later than the law allows. If you are not satisfied, you may complain to the Data Protection Board of India once it is operational.
Signed-in users can also create a deletion request from Settings. A request is checked for identity, ownership and legal holds before anything is erased.
12. Grievance Officer and data protection contact
- Grievance Officer
- To be published before launch
- Designation
- To be published before launch
- Address
- To be published before launch
- To be published before launch
- Phone
- To be published before launch
- Hours
- To be published before launch
- Questions about your data
- To be published before launch · To be published before launch
13. Children
The service is for professionals and businesses and is not directed at anyone under 18. We do not knowingly collect data of children. If a Customer's data includes a child's data, the Customer is responsible for obtaining parental consent.
14. Changes to this policy
We post changes here with a new version and date, and email account owners before a material change takes effect. This is version 2026-11-22.