Shraddha Prime Projects updates official email address for all communications
- Official email changed to shraddhaprimeprojects@gmail.com effective immediately
- Previous email towasurvey@yahoo.co.in is no longer active for official use
- Notification filed with BSE under Regulation 30 of SEBI LODR 2015
- Investors must direct all grievances and queries to the new address

*this image is generated using AI for illustrative purposes only.
Shraddha Prime Projects has changed its official email address with immediate effect, directing all future correspondence to shraddhaprimeprojects@gmail.com .
The company notified BSE Limited on September 23, 2026, pursuant to Regulation 30 of the SEBI (Listing Obligations and Disclosure Requirements) Regulations, 2015. The change replaces the previous contact point, towasurvey@yahoo.co.in , ensuring streamlined communication channels for stakeholders.
Communication details
The company requested BSE to update the new contact details in their records. All investor grievances and official queries should now be directed exclusively to the new Gmail address. The Managing Director, Sudhir Mehta, signed the notification confirming this administrative change.
| Item | Details |
|---|---|
| Old Email ID | towasurvey@yahoo.co.in |
| New Email ID | shraddhaprimeprojects@gmail.com |
| Effective Date | September 23, 2026 |
| Regulatory Basis | Regulation 30, SEBI LODR 2015 |
Historical Stock Returns for Shraddha Prime Projects
| 1 Day | 5 Days | 1 Month | 6 Months | 1 Year | 5 Years |
|---|---|---|---|---|---|
| -1.98% | -0.14% | -9.20% | -1.86% | -1.86% | -1.86% |
How will the shift from a corporate domain to a generic Gmail address impact institutional investor confidence in Shraddha Prime Projects' governance standards?
Does this administrative change signal a broader restructuring or cost-cutting initiative within the company's operational framework?
What are the potential regulatory implications for Shraddha Prime Projects regarding data security and compliance with SEBI's evolving cybersecurity guidelines?


































