Privacy policy

This policy applies to the AskNivesh website, pages, and read-only market-data views. It covers how the app handles data connected to visitors, error reports, and ordinary service operation. It does not cover third-party websites, exchanges, regulators, brokers, or data providers linked from the app.

The core product is built from public exchange files, regulator releases, issuer records, company filings, and named APIs. These market records are about instruments, issuers, exchanges, indexes, holidays, prices, and corporate events. They are not personal information about site visitors.

The current web app may receive limited information when you use it:

• Standard server and security logs, such as request path, timestamp, response status, IP address, user agent, referrer, and error traces.
• Feedback you choose to send, such as a symbol, ISIN, source URL, screenshot context, email address, or correction details.
• Browser-level information needed to render the app, route requests, cache pages, and prevent abuse.

The public web app is designed as a read-only market-data interface.

• It does not ask web users for brokerage credentials.
• It does not collect bank account details or card numbers.
• It does not collect orders, trade instructions, or transaction history.
• It does not place trades or execute transactions for users.

Visitor and feedback information is used only for operational purposes:

• Serving pages, search routes, and read-only market-data views.
• Monitoring uptime, latency, application errors, and suspicious traffic.
• Investigating reported data issues and source discrepancies.
• Improving page structure, navigation, performance, and reliability.

A deployment may use cookies, local storage, cache headers, or privacy-conscious analytics to keep the site working, remember basic preferences, understand aggregate usage, and protect the service. You can limit cookies through your browser settings, but some routing, caching, or preference behavior may be affected.

AskNivesh does not sell visitor information. Limited data may be processed by hosting, logging, analytics, security, and support providers that help operate the site. Information may also be disclosed when required by law, to enforce site terms, to protect the service, or as part of a business transfer involving the app.

Operational logs should be kept only as long as needed for debugging, security, abuse prevention, and service reliability. Feedback records are kept while the related source question, correction, or product issue remains useful. Data that is no longer needed should be deleted or aggregated.

Reasonable technical and organizational safeguards should be used to protect operational records, including HTTPS, access controls, dependency maintenance, least-privilege service credentials, and restricted access to logs. No internet service can guarantee absolute security, so avoid sending sensitive financial account information through feedback channels.

You may request correction or deletion of feedback information you provided by using the instructions on the contact page. Requests may require enough detail to identify the relevant record and may be limited where retention is needed for security, legal compliance, or integrity of public market data.

This policy may be updated as the product changes. The updated version is effective when posted on this page, and the last-updated date above should show the latest material revision.