Privacy Policy
Effective date: 24 April 2026. Version: 2026-04-24.
Read time: about ten minutes. The plain-English summary immediately below is for convenience; the binding text is the numbered sections that follow.
Plain-English summary
We collect only what we need to compute and file your Income Tax Return. We never sell, rent, or trade your data. We encrypt sensitive identifiers at rest with AES-256-GCM. We retain filing data for the period the Income-tax Act and the GST Act require, then we delete it. You can request access, correction, erasure, or consent withdrawal at any time. India is the place of processing; the Pune courts have exclusive jurisdiction. The text that follows tells you exactly which provisions of which laws apply, what triggers them, and what we owe you when they do.
1. Definitions
- Act
- The Digital Personal Data Protection Act 2023 (Act No. 22 of 2023), enacted by the Parliament of India and notified in the Gazette of India on 11 August 2023.
- Board
- The Data Protection Board of India constituted under Chapter V of the Act.
- Data Fiduciary
- Any person who, alone or in conjunction with others, determines the purpose and means of processing of Personal Data, as defined in Section 2(i) of the Act. We are the Data Fiduciary for Personal Data processed through the Service.
- Data Principal
- The natural person to whom the Personal Data relates, as defined in Section 2(j) of the Act. You are the Data Principal in relation to your own Personal Data.
- Data Processor
- Any person who processes Personal Data on behalf of a Data Fiduciary, as defined in Section 2(k) of the Act. The processors we engage are listed at Section 7.
- Personal Data
- Any data about an individual who is identifiable by or in relation to such data, as defined in Section 2(t) of the Act.
- Sensitive Personal Data or Information
- The category defined in Rule 3 of the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules 2011 ("SPDI Rules"), retained as a transitional reference until the DPDPA Rules are fully notified. We treat PAN, Aadhaar, bank account number, IFSC, and date of birth as Sensitive Personal Data and apply field-level encryption to them.
- Service
- The ElevateFinance web platform, application programming interfaces, mobile interfaces (where deployed), email and document workflows, computation engine, and customer-support channels operated under the brand "ElevateFinance".
- we / us / our / the Company
- ElevateFinance, a sole proprietorship registered as a Micro Enterprise under the Udyam Registration framework administered by the Ministry of Micro, Small and Medium Enterprises, Government of India, having its registered office at Pune, Maharashtra 411058, India, and acting through its sole proprietor Priyesh Mishra.
- you / your / the User
- Any natural person who accesses or uses the Service, whether or not registered for an account, including individual customers, Chartered Accountants empanelled on the Service, and authorised personnel of an enterprise customer.
2. Who we are and how to reach us
3. Scope of this Policy
4. Categories of Personal Data we process
| Category | Examples | Purpose | Protective measure |
|---|---|---|---|
Identity data | name, email address, mobile number, date of birth | account creation, authentication, communication | TLS 1.3 in transit; database access controls at rest; field-level encryption for date of birth |
Government identifiers | Permanent Account Number (PAN), Aadhaar number | Income Tax Return preparation under Section 139 of the Income-tax Act 1961 | AES-256-GCM application-level encryption; access logged on every read; never displayed in full in audit logs or analytics |
Tax-filing inputs | salary breakup, Form 16, Annual Information Statement (AIS), Tax Information Statement (Form 26AS), house-property income, capital gains, deductions claimed under Chapter VI-A | computation of tax liability, generation of ITR XML, generation of Schedule FA / Schedule CG / Form 67 attachments | TLS 1.3 in transit; encrypted database; access scoped to assigned Chartered Accountant and the customer |
Restricted Stock Unit (RSU) grant data | grant identifier, vesting schedule, fair market value at vest, sale proceeds | computation of perquisite under Section 17(2)(vi) of the Income-tax Act and capital gains under Section 45 | TLS 1.3 in transit; encrypted database; sale-side bank-account-number encrypted |
Financial account data | bank account number, IFSC, account holder name (for refund credit) | enabling Income Tax refund credit to your designated account | AES-256-GCM application-level encryption; never transmitted to any party other than the Income Tax Department through the official ITR submission channel |
Document uploads | Form 16 PDFs, investment proofs, rent receipts, salary slips, broker statements | evidentiary review by the assigned Chartered Accountant | magic-byte file-type verification; TLS 1.3 to Cloudflare R2 (AWS Mumbai region equivalent zones); server-side encryption at rest; retention bound to the AY + 7-year window |
Payment metadata | Razorpay order identifier, payment identifier, refund identifier, payment status | order placement, settlement, refund processing, dispute handling | we do not collect or store full card numbers, CVV, UPI PIN, or net-banking credentials; Razorpay is the PCI-DSS-compliant Data Processor |
Audit log data | identifier of the actor, action taken, timestamp, IP address, user-agent string | detection of unauthorised access, fraud prevention, and post-incident investigation, in line with Section 8(5) of the Act | append-only log; access restricted to the Data Fiduciary and to authorised investigators |
Consent records | purpose, version of notice, IP address at the moment of consent, user-agent, timestamp | discharge of the Data Fiduciary obligation to demonstrate consent under Section 6 of the Act | append-only consent ledger; cryptographic time-stamping; retained for the life of the account plus three years |
Usage data | pages viewed, features used, time on page, error events | security monitoring, defect detection, capacity planning | first-party only; no third-party advertising trackers; no cross-site identifiers |
5. Lawful bases for processing
- Consent (Section 6).Account creation, optional uploads, marketing communications, and the use of any feature labelled "optional" inside the Service.
- Legitimate use, performance of a contract (Section 7(a)). All processing necessary to compute, generate, or transmit the Income Tax Return that you have instructed us to prepare. The lawful basis for this processing is the contract you accept on sign-up read with Section 7(a) of the Act.
- Legitimate use, compliance with judgment, decree, or order (Section 7(d)). Disclosures we are compelled to make pursuant to a written notice issued by the Income Tax Department under Sections 131, 133, or 142(1) of the Income-tax Act, by a court of competent jurisdiction, or by a regulator empowered by statute.
- Legitimate use, fraud prevention (Section 7(g) read with the IT Act 2000 due diligence obligations). Audit-log generation, abuse-pattern detection, account-suspension actions, and rate-limit enforcement.
- Legitimate use, employment context (Section 7(i)). Processing of Restricted Stock Unit grant data on behalf of an enterprise customer, where the employer-employee relationship is the relevant lawful basis and the employee remains the Data Principal in respect of their own data.
6. Notice and consent
7. Data Processors and recipients
| Category | Examples | Purpose | Protective measure |
|---|---|---|---|
Razorpay Software Private Limited | order, payment, and refund metadata | payment gateway services | India; PCI-DSS Level 1; RBI Payment Aggregator licensee |
Resend (Resend Inc.) | recipient email address, delivery status | transactional email (sign-in codes, filing notifications, receipts) | United States with EU Standard Contractual Clauses; recipient metadata only; no payload retention beyond delivery confirmation |
Neon (Neon Inc.) | encrypted database storage of all categories at Section 4 | managed PostgreSQL hosting | AWS Mumbai region (ap-south-1); encryption at rest using AES-256; encryption in transit using TLS 1.3 |
Cloudflare (Cloudflare R2 object storage) | document uploads in the categories at Section 4 | object storage for Form 16 PDFs, investment proofs, and similar artefacts | India-located bucket; server-side encryption; pre-signed PUT URLs scoped per upload; magic-byte verification on every put |
Auth.js (the open-source authentication library) + Google LLC | email address, name, profile-picture URL where you sign in via Google OAuth | identity-provider integration | OAuth 2.0; only the openid, email, and profile scopes are requested; no contacts, no calendar, no drive scopes |
Independent Chartered Accountants (where CA review is enabled) | all Personal Data necessary to review the specific filing assigned to them | professional review of the return prior to e-filing, where the User has elected the optional, paid CA-review feature and a Chartered Accountant has been retained for that filing | access scoped to the specific assigned filing; written confidentiality undertaking; ICAI Code of Ethics applies; communication audit-logged. The Service operates in software-only mode by default; CA review is not engaged unless the User elects it for a particular filing. |
8. International data transfers
9. Retention
- Account-level identity data: the life of the account plus one hundred and eighty days, after which the account is fully purged.
- Tax-filing inputs and the corresponding ITR XML: the relevant Assessment Year plus seven years, in line with Section 149 read with Section 139 of the Income-tax Act 1961.
- Payment metadata: eight years from the date of the relevant transaction, in line with Section 36 of the Central Goods and Services Tax Act 2017.
- Audit log: three years, with secure deletion thereafter.
- Consent ledger: the life of the account plus three years.
- Backups: a sliding window of ninety days; after that horizon, deleted Personal Data is unrecoverable from backup.
10. Security of processing
- Transport security using TLS 1.3 for all customer connections, with strong ciphers only and modern cipher suites.
- Application-level field encryption using AES-256-GCM for PAN, Aadhaar, bank account number, IFSC, and date of birth, with a distinct authenticated-encryption key separate from database access credentials.
- Password hashing using Argon2id or an algorithm of equivalent strength.
- Hash-based message authentication on all signed receipts (HMAC-SHA256), enabling independent verification of any computation artefact long after issuance.
- Role-based access control with the principle of least privilege; Chartered Accountant access is scoped to the specific assigned filing.
- Append-only audit logging with immutable, time-stamped event entries.
- Step-up re-authentication on destructive or high-risk operations (PAN edit, Aadhaar edit, role change, payment-order creation), bound to the specific purpose so that a token issued for one purpose cannot be replayed against another.
- Magic-byte verification on every uploaded file, refusing payloads whose declared content type does not match the byte signature.
- Server-Side Request Forgery (SSRF) protection on all server-fetched URLs, with an allow-list of permitted hostnames.
- Sliding-window rate limiting on authentication endpoints, with separate rate buckets for sign-in, sign-up, password reset, and step-up code issuance.
- A safe logger that strips Personally Identifiable Information from application logs prior to write.
- Strict Content Security Policy with per-request nonces for inline scripts.
- Continuous dependency-vulnerability auditing and weekly Dependabot pull requests; gitleaks pre-commit and pre-push secret-scanning.
11. Your rights as a Data Principal
- Right of access (Section 11). A consolidated machine-readable export of the Personal Data we process about you, identification of the Data Processors with whom we have shared it, and the purposes of processing. Acknowledged within forty-eight hours; fulfilled within seven working days.
- Right to correction and erasure (Section 12). Correction of inaccurate data; completion of incomplete data; updating of out-of-date data; erasure of Personal Data that is no longer necessary for the purpose for which it was collected. Erasure is implemented through a seven-day soft-hold, after which the purge is irreversible across primary and backup tiers within ninety days.
- Right to grievance redressal (Section 13). A clear, time-bound, cost-free channel to raise a concern about the processing of your Personal Data. See Section 12 of this Policy for the specific procedure and timelines.
- Right to nominate (Section 14).A Data Principal may nominate any other individual who shall, in the event of death or incapacity, exercise these rights on the Data Principal's behalf. The nomination is captured through the in-product "/settings > Nominate" path.
- Right to withdraw consent (Section 6(4)). Exercisable at any time, with the same ease as the giving of consent; a single in-product action suffices.
- Right to portability. A structured machine-readable export in JSON, plus a human-readable PDF rendering of every Income Tax Return you have generated through the Service.