TaxSahi · Privacy
TaxSahi Privacy Policy
Last updated: 17 November 2026
In short
TaxSahi helps tax practices prepare their clients' income-tax returns and TDS/TCS statements. We keep what a practice enters or imports for its clients, only to provide that service, in India, behind two-step login and access limited to the practice. We don't sell it, share it for marketing, or use it for anything else. We never keep anyone's income-tax e-filing portal or TRACES password: the TaxSahi Assistant browser extension keeps those on the user's own computer.
Who we are
TaxSahi is a product of SimpleApps.World (proprietor: Gaurav Gupta), 4A, Maharana Pratap Enclave, Near Ram Mandir, Pitampura, New Delhi – 110034. A tax practice (a CA, tax professional or firm) uses TaxSahi for its clients. The practice decides whose data to add and what for, and must have its clients' consent; we process that data on the practice's behalf. Where TaxSahi works with the Income Tax Department's systems as an e-Return Intermediary, we also follow the Department's ERI terms.
What we keep
| Data | Why | Kept until |
|---|---|---|
| Practice members: name, email, sign-in and two-step login settings | To sign in and keep each practice's data to its own members | The account is closed |
| Clients: name, PAN, Aadhaar number (the return asks for it; also a property co-owner's PAN or Aadhaar), date of birth, father's name, contact details, address, bank accounts for refunds | To prepare and check their returns | The practice deletes the client, the client's consent ends, or the client asks us to erase it |
| Return data: AIS, Form 26AS, Form 16, previous returns, computations, challans and their receipts | To prepare the return and match it with the Department's records | As above |
| TDS/TCS data: a deductor's TAN, books entries imported from Zoho, Busy or Tally, deductees' PANs and payments, challans, statements and TRACES's defaults | To prepare, check and correct TDS/TCS statements and pay challans | As above |
| Other portal logins (GST, EPFO, ESIC, MCA, bank), only if the practice saves them | For the practice's own reference | The practice deletes them. Encrypted in the practice's browser before they're saved; we can't read them |
| Consent records: what each client agreed to, how, until when, and withdrawals | To show the client agreed, and to stop when they withdraw | As long as the client's data is kept, then as the law requires |
| Activity log: who changed what, and when | Security and accountability within the practice | As long as the practice's account |
Not kept: income-tax e-filing portal and TRACES passwords (never sent to us), Aadhaar OTPs, card details.
Consent
Before a practice adds a client, it takes the client's express consent in plain terms, separately from any other service, and records it in TaxSahi: what for, how it was given, and how long the data may be kept. A practice can send the client a consent link instead: the client reads the consent on taxsahi.com and agrees by typing their PAN (checked against what the practice entered, not stored again), and TaxSahi records when they agreed. The link works once and for 7 days. A client can withdraw consent at any time through their practice or by writing to us; the practice then stops using the data and deletes it, except what the law requires to be kept.
Where and how it's kept
- In India: the database is hosted by Supabase in Mumbai (AWS ap-south-1), encrypted at rest (AES-256) and in transit (TLS).
- Access: every table limits rows to the practice's own members (row-level security); client data opens only after two-step login.
- Passwords a practice saves are encrypted in its browser with a key only its members hold (AES-GCM); the server stores only what it can't read.
- Portal and TRACES passwords stay in the TaxSahi Assistant extension on the user's own computer (see the extension's privacy policy).
Who else handles it
- Supabase (database and sign-in) and Cloudflare (serving the website), as our processors, only to run TaxSahi.
- Zoho Books, only when a practice connects its own Zoho account: TaxSahi reads its books, read-only.
- A PIN code typed in an address is looked up at api.postalpincode.in to fill the city and state (only the PIN code is sent). Fonts and page libraries load from Google Fonts and cdnjs (no client data is sent).
- No one else, unless a court or the law requires it. We don't sell data, use it for advertising, or share it with group companies or partners.
Your rights
A client can ask, through their practice or directly to the grievance officer below, to see what is kept about them, correct or complete it, erase it, or withdraw consent, as the Digital Personal Data Protection Act, 2023 allows. A practice can do each of these for its client in TaxSahi (edit or delete the client, withdraw the consent). We reply within 30 days.
Security incidents
If personal data is lost, or accessed or disclosed without authorisation, we inform the affected practices and people, the Income Tax Department and the Data Protection Board of India within 48 hours of learning of it, with what happened, what was affected and what we're doing about it.
Grievance officer
Gaurav Gupta, Proprietor, SimpleApps.World — responsible for the personal data TaxSahi processes.
4A, Maharana Pratap Enclave, Near Ram Mandir, Pitampura, New Delhi – 110034
Email: support@simpleapps.world · Phone: +91 98105 12298
We acknowledge a grievance within 2 working days and resolve it within 30 days.
Changes
If what we keep or how we use it changes, we update this page and its date first, and tell practices in TaxSahi.