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
Disha account privacy.
Data needed to provide personal accounts and payment verification.
Website connection
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 product usage
Signed-in 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.
Usage measurement
Anonymous browser identifiers, broad page categories, tagged referral source and performance measurements help us understand demo use and returning browsers. We link signup and payment-stage facts to that browser cohort on the PC; emails, payment references and support text are not sent in browser analytics events. Browser identifiers last up to 90 days. Google sign-in uses only identity, email and basic profile information.
Requests
Contact the operator for privacy or account-record requests.