Local account records
Email, password hashes, optional Google identity ID, activation/session token hashes, access term, payment references and approval audit are kept on the RamPath PC. Broker passwords and payment PINs are not requested.
PRIVACY
Data needed to provide personal accounts and payment verification.
Last updated
Operated by DEENDAYAL
Email, password hashes, optional Google identity ID, activation/session token hashes, access term, payment references and approval audit are kept on the RamPath PC. Broker passwords and payment PINs are not requested.
The website routes authenticated requests to the PC. Connection configuration and website content may be stored by the host; market snapshots and customer account records remain on the PC.
Signed-in Index Options Disha, MCX Disha and account dashboard activity is recorded on the operator PC. This includes daily visits, broad product and section views, recent viewing status and estimated active time from visible-page heartbeats and recent interaction. Active time pauses while hidden or after 2 minutes without interaction; concurrent tabs are not double-counted. A new visit begins after 30 minutes of inactivity. Only authenticated administrators see account-linked usage, retained for up to 90 days. We do not record keystroke contents, screenshots or trading-account credentials.
First-party website analytics use a browser identifier, broad page categories, selected link clicks and referral categories to report traffic and navigation patterns to admins. The website analytics store omits page query strings, form entries, emails and payment references. Browser identifiers last up to 90 days. Signup and payment totals come from the account database. Google sign-in uses only identity, email and basic profile information.
Contact the operator for privacy or account-record requests.