Rohan Iyer
Risk, Responsible Trading & YMYL Editor
Biography
Rohan is the final reviewer on every YMYL page before it publishes. His role is the inverse of the marketing team's: where a marketer wants to maximise registrations, Rohan's job is to ensure the page would still be useful to a reader who decides not to register. He pushes back on overly confident wording, owns the risk-disclosure block, and signs off on the addiction-help resources visible on every page. Rohan's edits are the reason the portal does not promise win rates, does not call any platform 'safe', and does not bury risk in a footer.
Areas of expertise
- Risk disclosure language for high-risk financial products
- Behavioural research on retail-trading harm
- YMYL editorial standards (Google E-E-A-T)
- Problem-gambling and trading-addiction resources
- Fact-checking methodology
Credentials
- MA Psychology (University of Pune), thesis on retail-trader decision-making
- 14 years in financial editorial roles including fact-checker at two Tier-1 Indian publications
- Volunteer with iCall (a TISS initiative) on financial-stress counselling
Editorial methodology
Reviews every page against a 12-point YMYL checklist: visible risk before CTA, capital-loss language, no 'safe' or 'easy' framing, addiction-help links, regulator-warning citations, qualified-professional referrals, factual sourcing on every numerical claim, dated review, affiliate disclosure, language matching, accessibility, and a non-trading alternative.
V5 review remit
Rohan Iyer's remit is not only to write a topic; it also defines which claims should not publish. Each sensitive claim is checked against a source, account-screen context and a user-risk boundary.
| Coverage area | Evidence accepted | Claims blocked |
|---|---|---|
| Risk wording | Capital-loss language before CTA and visible no-advice boundaries | Safe, easy, guaranteed or low-risk framing |
| YMYL review | 12-point checklist, source freshness and affiliate disclosure | Pages that pressure a deposit before context |
| Reader protection | Pause rules, non-trading alternative and addiction-help visibility | Risk hidden only in footer or legalese |
Recent V5 audit work
This log shows what Rohan Iyer changed or verified during the latest content audit. It is not a public performance claim; it is an editorial accountability record.
| Date | V5 audit work | Outcome |
|---|---|---|
| May 27, 2026 | Risk and CTA copy review | Commercial CTAs stayed paired with visible risk and affiliate disclosure. |
| May 27, 2026 | Author-page E-E-A-T review | Author scope, claim boundaries and audit logs were added. |
| May 27, 2026 | Full live technical SEO review | Canonical, schema, noindex, sitemap and affiliate rel checks passed cleanly. |
Claims this author will not make
- No safe, easy or guaranteed framing.
- Risk disclosure is not allowed to live only in the footer.
- No personal financial, legal or tax advice.
How this profile helps readers
Rohan's profile explains how the portal's risk layer works. He reads every page from the perspective of a reader who may decide not to register. If the page is no longer useful to that reader, the wording is considered too promotional and is sent back for revision.
His YMYL review is not just about adding a disclaimer. He checks whether risk appears before commercial action, whether capital-loss language is plain, whether affiliate disclosure is near decision points, and whether the page avoids safe, easy or guaranteed framing. Footer-only risk does not pass his standard.
Rohan also looks for a non-trading alternative and a pause rule on sensitive pages. Demo, deposit, withdrawal, bonus and signal pages should help readers define amount at risk, session limit, stop rule and evidence log. That makes his role a reader-protection layer, not only a fact-checking step.
Evidence notes and conflict boundaries
Evidence note: Rohan does not let risk pages become legal boilerplate. Each sensitive article should leave the reader with a concrete pause rule, loss limit, non-trading alternative and evidence habit.
Reader use case: if a user reads a page and decides not to deposit, Rohan's review layer treats that outcome as valid. The content's job is usefulness and protection, not only conversion.
Audit trail: Rohan checks repeated claims, overconfident headings, hidden affiliate pressure and missing no-advice boundaries. If the wording weakens any of those safeguards, the page goes back into the rewrite queue.
Conflict boundary: Rohan blocks performance language, recovery-after-loss framing, emotional urgency and guarantee-like CTA patterns. His sign-off is based on reader protection rather than registration rate.
Update trigger: when a page receives a new bonus, payment route, app source or legal wording, Rohan checks that risk visibility increases in proportion instead of being pushed lower on the page.
Practical output: the reader receives more than a warning. Use this guide to leave them with usable controls: fixed budget, session stop, evidence log and the option not to trade.
Final check: on each commercial page, Rohan asks whether a cautious reader can leave with a useful answer even if they choose not to register. If not, the page returns to editing, and the reason is recorded.
Rohan Iyer — Published articles (3)
Contact and verification
Readers can contact Rohan Iyer directly for editorial queries, corrections, or source clarification at [email protected]. No personal financial advice is provided — please consult a qualified CA or SEBI-registered investment advisor.
PGP fingerprint: Available on request via contact page