Privacy Policy
This policy is our notice to you under India's Digital Personal Data Protection Act, 2023 (DPDP Act). It explains what personal data Tradescan.in collects, the purpose of each use, the legal basis we rely on, how long we keep it, and how you can exercise your rights.
Last updated 16 September 2026
1. Who is responsible for your data
Tradescan.in is operated by Retailblaze, trading as Retailblaze, at [COMPLETE REGISTERED ADDRESS WITH CITY, STATE, PIN — OWNER INPUT REQUIRED]. For the purposes of the DPDP Act we act as the Data Fiduciary for the personal data described below, and we determine why and how it is processed.
Privacy contact: [DATA PROTECTION CONTACT — OWNER INPUT REQUIRED]. Grievance Officer: [GRIEVANCE OFFICER NAME & DESIGNATION — OWNER INPUT REQUIRED] at [GRIEVANCE EMAIL — OWNER INPUT REQUIRED].
2. What we collect and why (purpose notice)
- Account data — email address, display name and authentication identifiers. Purpose: creating and securing your account and signing you in. If you sign in with Google, we receive your email, name and profile picture from that sign-in.
- Profile data you choose to add — phone number, stated experience level and bio. Purpose: personalising the interface and support. These fields are optional.
- Subscription and payment data — plan, status, period and the payment provider's customer, order and subscription identifiers, plus amounts. Purpose: giving you paid access, issuing receipts, handling refunds and meeting tax and accounting obligations. Card and bank credentials never reach our servers.
- Data-feed credentials — if you connect a broker account for live market data, that access token is encrypted before storage. Purpose: fetching market data for your session only. We never place orders and never read your holdings or funds for any other purpose.
- Product data — watchlists, alerts and interface preferences. Purpose: providing the features you set up.
- Consent records — the fact, time, method and version of the terms you accepted at sign-up. Purpose: proving a valid consent record as the DPDP Act requires.
- Technical logs — timestamps, error traces and request metadata. Purpose: keeping the service available, debugging faults and preventing abuse.
We rely on your consent, given at sign-up and at each optional step, for account, profile and data-feed processing, and on the performance of our contract with you and our legal obligations for billing, tax and security records.
3. What we do not do
We do not sell your personal data. We do not share it for third-party advertising. We do not use your broker connection for anything other than retrieving market data. We do not send your personal data to the AI models that generate written commentary — those models receive only market figures such as symbol, sector, price change and computed scores.
4. Processors and where data is handled
We use service providers who process personal data only on our instructions: a managed cloud database, authentication and storage provider; a payment processor; hosting and edge infrastructure; an AI inference gateway for written commentary; and the market data or broker API you connect. Each receives only what it needs for its function.
Some of this infrastructure may process or store data outside India, in jurisdictions permitted under the DPDP Act and applicable government notifications. Transfers are covered by contractual data-protection terms with each provider.
5. How long we keep it
Account, profile and product data are kept while your account is active. Broker tokens are deleted when you disconnect the feed or when they expire. Consent records and payment, invoice and tax records are kept for the period Indian law requires us to retain them, even after account deletion. Technical logs are kept for a short operational period and then discarded. When a purpose is exhausted and no legal retention applies, the data is deleted.
6. Your rights under the DPDP Act
You have the right to access a summary of your personal data and how it is processed, to correction and completion of inaccurate data, to erasure, to withdraw consent at any time, to nominate someone to exercise your rights in the event of death or incapacity, and to a readily available grievance-redressal mechanism.
Submit any of these requests from Data Rights or from Settings inside the app. We verify each request against the email registered to your account before acting on it. Withdrawing consent stops the processing that depends on it, which will end your ability to use features that require that data, and does not by itself entitle you to a refund.
7. Security
Access to your records is restricted at the database level so an account can read only its own rows. Broker tokens are encrypted before storage with a server-held key, all traffic is served over HTTPS, privileged operations run server-side, and privileged administrative actions are recorded in an audit trail. No system is perfectly secure, so use a strong, unique password and tell us promptly if you suspect misuse of your account. If a personal data breach affects you, we will notify you and the Data Protection Board of India as required.
8. Cookies and browser storage
We use storage that is strictly necessary for the service — keeping you signed in, remembering interface preferences and protecting against abuse. Anything non-essential is off unless you switch it on, and you can change your choice at any time. See our Cookie Policy.
9. Children
Tradescan.in is intended only for users aged 18 and above, and we ask you to confirm this at sign-up. We do not knowingly process the personal data of children. If you believe a child's data has reached us, write to [GRIEVANCE EMAIL — OWNER INPUT REQUIRED] and we will delete it.
10. Grievances, changes and contact
If you are unhappy with how we handle your data, contact our Grievance Officer through the Grievance Redressal page. If your grievance is not resolved, you may complain to the Data Protection Board of India.
If this policy changes materially, we will notify you by email or in-app notice before the change takes effect, and where the change requires it, ask for your consent again.
