Skip to main content

SEBI Project Jagrook 2026: Stock Broker Website and App Compliance Checklist

Author: Finin2min Editorial Desk

Reviewed by: Ravi Sisodia

Published: 2 October 2026

Finin2min 2-Minute Summary

Current position

SEBI issued the Project Jagrook circular on 1 October 2026. The implementation is deliberately phased. During 5-31 October, broker websites are required to display the specified investor-awareness messages together with the prescribed risk disclosures, while display on trading apps is voluntary during the transition window. From 1 November 2026, the framework moves into its continuing state: websites must carry the investor-awareness messages on the relevant landing interface and trading apps must alternate investor-awareness messages and risk disclosures in the manner directed by SEBI. The exact message text and display logic should be taken from the operative circular and exchange implementation guidance rather than recreated from memory.

Why this matters for brokers

A compliance team can easily underestimate this circular because the visible output is only a message on a screen. In practice, the control spans legal interpretation, content management, application release management, website deployment, mobile-app versioning, testing and evidence retention. A broker may satisfy the text requirement on one platform but fail because a banner is hidden behind another pop-up, an older app version does not rotate the message correctly, or a website cache serves the wrong sequence. The regulator-facing question is therefore not merely whether the wording exists somewhere in the codebase, but whether the required message was actually displayed to the intended users at the required time.

Implementation workflow

Start by mapping every customer-facing entry point: public website, login page, web trading terminal, Android app, iOS app and any white-labelled interface. Assign one owner for regulatory text and another for technical release, with a single implementation matrix that states effective date, channel, placement, frequency and evidence. Build the message content as a controlled component so compliance can update wording without an uncontrolled redesign. Test desktop, tablet and mobile layouts, light and dark modes, logged-in and logged-out states, and older supported app versions. Where messages alternate with risk disclosures, test the sequence across repeated sessions rather than checking only the first screen.

Worked example

Assume a broker has a website and two mobile apps. On 5 October the website release goes live, but the Android app remains on the older build until 10 October. That can still be consistent with the transition period if app display is voluntary during October, provided the website requirement is met. The position changes from 1 November: the app logic must then comply with the continuing mandatory framework. The broker should preserve screenshots dated around each go-live, release notes, code/configuration references and a test record showing the rotation logic. This evidence converts a visual feature into a defensible compliance control.

Investor lens

For investors, Project Jagrook is designed to make risk information harder to ignore as participation in cash and derivative markets expands. The presence of an awareness message does not mean a product is safe, unsuitable or recommended. It should trigger the opposite behaviour: read the contract note, product and margin disclosures, understand leverage and loss potential, and verify whether the intermediary is registered. A regulatory message is a prompt to pause and assess risk, not a quality certificate for a trade.

Controls to preserve

Keep the operative circular, exchange or depository implementation notice, approved message copy, release ticket, screenshots, automated test results, change approval, app version number and incident log. If a display failure occurs, record its duration, affected channel, root cause and remediation. This file should be capable of showing not only what the broker intended to display but what was actually live.

Common mistakes

The main mistakes are treating 5 October and 1 November as the same effective date; assuming a website fix automatically covers mobile apps; altering the regulator-specified message for marketing tone; placing the message where it is technically present but practically invisible; and keeping no evidence after deployment. Another risk is a temporary October implementation that must be rebuilt in November. Building the final-state control first and using configuration to manage the transition is usually more robust.

Governance checkpoint

The compliance owner should sign off a channel-by-channel matrix before each effective date. Product teams should not be permitted to suppress the message for campaign banners, personalised offers or app experiments without a compliance review. If the broker operates APIs or partner interfaces, confirm whether those interfaces fall within the circular's customer-facing scope and document the conclusion. Monitoring should continue after go-live because a later application update can accidentally remove or hide a previously compliant component.

FAQs

Does every stock broker need to check the circular? Yes, brokers within the circular's scope should map the requirement to each customer-facing channel. Is app display mandatory during the October transition period? The SEBI communication provides a phased treatment; use the circular's exact dates and channel rules. What changes from 1 November 2026? The continuing website and app obligations apply according to the circular. Can a broker rewrite the message? Do not assume so; use the regulator-specified text and implementation instructions. What evidence should be retained? Screenshots, release records, message configuration, app versions, test results and approvals. Is this an investor recommendation? No. The message is an awareness and risk-disclosure control, not personalised advice.

Official Sources

Finin2min conclusion

For SEBI Project Jagrook 2026, use the cited official instrument, the relevant effective date and a documented evidence trail. A portal screen, news headline or internal checklist should not replace the operative regulatory source.

Disclaimer

General educational information for India. Regulatory requirements can change. Verify the latest official instrument and obtain case-specific professional advice before acting on material rights, money or compliance decisions.

Related tools and reading