AdalatPulse for eCourts — Privacy Policy

Last updated 7 September 2026

What the extension does

You look up a case or a cause list on an Indian court website yourself, including typing the court's CAPTCHA. The extension adds a small panel to that page. When you press a button in that panel, it sends what is shown on the page to your own AdalatPulse account. Nothing is sent without your press. The extension never fetches court pages on its own and never solves CAPTCHAs.

What it sends, and only when you press

• The visible text and HTML of the case page or cause list you opened, and its address.
• The order PDF you opened, when you press "Save the open order PDF".
• The time you pressed the button.

It sends this to the AdalatPulse server address you configured, using an access token you created in your AdalatPulse Settings.

What it stores in your browser

Only your AdalatPulse server address and your access token, in Chrome's extension storage. Remove the extension or revoke the token in Settings to end access.

What it does not do

• No browsing history, no cookies, no keystrokes, no data from any site other than the court page you are on.
• No advertising, no analytics, no third-party services. Data goes only to your AdalatPulse server.
• No automatic CAPTCHA solving, no background crawling of court websites.

Permissions, explained

• services.ecourts.gov.in and *.dcourts.gov.in: to show the panel on court pages and read what you opened there.
• storage: to remember your server address and token.
• activeTab: so the one-click setup can read the connect page you clicked the icon on.
• Optional host access to your AdalatPulse address: requested once, when you connect, so the extension can talk to your own server.

Contact

Questions about this policy: write to the address shown in your AdalatPulse Settings, or to the developer contact on the Chrome Web Store listing.