Terms of Service
Welcome to MySocietyEntry. These Terms of Service ("Terms") represent a legally binding agreement between MySocietyEntry Corporation ("we", "us", "our") and the housing societies, resident welfare associations (RWAs), developers, residents, supervisors, accountants, and gate security personnel ("you", "User") accessing or utilizing our platforms.
1. Acceptance, Platform Scope, and Relationship Boundaries
• 1. By creating an account, the user acknowledges that they have read and agreed to these Terms of Service. • 2. These Terms govern your access to the MySocietyEntry web portals, guard console apps, and resident tools. • 3. MySocietyEntry acts solely as a software-as-a-service (SaaS) provider and is not a party to RWA bylaws. • 4. We do not employ or supervise security guards, maintenance personnel, or property managers. • 5. The platform is provided on an 'as-is' and 'as-available' basis without warranty of any kind. • 6. We reserve the right to deploy hotfixes, updates, and UI upgrades without prior user notifications. • 7. Use of the app for unlawful surveillance, harassment, or unauthorized tracking is strictly prohibited. • 8. These Terms apply equally to flat owners, tenants, committee members, and commercial shop unit vendors. • 9. Access to database ledgers is restricted by roles configured exclusively by your society administrators. • 10. We carry no responsibility for physical disputes, parking blockages, or gate entrance lane bottlenecks. • 11. All notices published on the digital board are the sole responsibility of the publishing RWA committee. • 12. We do not verify the authenticity of resident-uploaded documents, profile photos, or lease agreements. • 13. The platform does not guarantee internet uptime or hardware power back-ups at guard gate terminals. • 14. Residents are responsible for managing sub-user access for family members and domestic helpers. • 15. Any attempt to reverse-engineer the API, web scrap, or bypass token security will lead to instant ban. • 16. We do not act as an escrow agent or intermediary for payments made between residents and the RWA. • 17. Third-party advertising, if enabled by RWA, is subject to regional guidelines and RWA content approvals. • 18. We reserve the right to suspend platform access for societies violating national data security laws. • 19. These Terms govern the use of all standard modules including accounting, gate security, and helpdesk. • 20. Residents must ensure their mobile devices meet minimum OS specifications to receive push notifications. • 21. We do not guarantee the physical security of assets, vehicles, or units on-premises. • 22. Committee members agree to use administrator dashboards strictly for authorized RWA purposes. • 23. The platform cannot be used to coordinate public protests, commercial campaigns, or political rallies. • 24. Any fee changes or premium feature adjustments will be communicated to the RWA 30 days in advance. • 25. Users must log out of active sessions on shared public terminals to prevent unauthorized access. • 26. We are not liable for errors in third-party maps used for guard patrol routing checks. • 27. Terms of service updates will be displayed on the admin portal dashboard and resident app splash screen. • 28. System access logs are recorded for security audits and are accessible to RWA treasurers. • 29. Residents agree to maintain civil communication standards when posting on the community board. • 30. Failure of the RWA to enforce their bylaws does not constitute a waiver of MySocietyEntry terms. • 31. All database operations conform to standard corporate safety and data isolation rules.
2. Account Registration, Credentials Security, and Resident Verification
• 32. Residents must submit accurate flat mapping units, block identifiers, and phone numbers during signup. • 33. The RWA committee retains sole authority to approve or reject pending resident profile activations. • 34. Users must secure their login passwords and are liable for all actions taken under their accounts. • 35. Phone number verification via SMS OTP is mandatory to finalize user profile setup. • 36. Tenants must upload a valid lease agreement or RWA authorization to clear profile checks. • 37. We reserve the right to deactivate accounts linked to simulated coordinates or bot activities. • 38. Residents must promptly update their profile if they vacate, lease out, or sell their flat unit. • 39. Administrators must verify the credentials of accountants and supervisors before granting dashboard access. • 40. Sharing of guard console tablet login codes with unauthorized visitors is strictly prohibited. • 41. We are not responsible for delivery delays resulting from outdated phone numbers on resident profiles. • 42. Tenants agree that the flat owner may request access logs of the mapped unit from the RWA. • 43. The RWA is responsible for cleaning up old profiles of residents who have vacated the society. • 44. Residents must verify that their registered email matches their billing record to receive receipts. • 45. Any unauthorized usage of the admin panel must be reported to support@mysocietyentry.com within 24 hours. • 46. We do not allow duplicate accounts for the same resident unit under conflicting roles. • 47. Committee members agree to keep resident phone numbers confidential and hidden from external lists. • 48. We reserve the right to block accounts with multiple failed login attempts within a 5-minute span. • 49. Residents must register domestic helpers with their legal names matching official government IDs. • 50. The RWA agrees to obtain explicit consent from guards before installing security patrol apps on devices. • 51. Account deletion requests by residents are subject to pending dues verification by the RWA treasurer. • 52. A tenant profile is linked automatically to the respective owner profile for notification transparency. • 53. We are not responsible for financial losses due to compromised admin accounts with weak passwords. • 54. Users must complete email verification within 7 days of signup to prevent profile deactivation. • 55. Society admins must not grant system access to banned commercial vendors or blacklisted staff. • 56. We use industry-standard encryption for all session tokens stored on client browser cookies. • 57. Residents agree that their public profile details (name, flat number) are visible to neighbors in the app directory. • 58. We reserve the right to audit user profiles to verify compliance with gated community rules. • 59. The RWA agrees that their database files will be permanently deleted 90 days post subscription cancellation. • 60. Account access during maintenance downtimes may be limited to essential gate security functions. • 61. Residents must verify the registration details of vehicles before requesting RFID tags. • 62. We do not store plain-text passwords on any server, backup database, or memory cache.
3. Society Maintenance Invoicing, Late Fees, and Payment Gateway Settlement Rules
• 63. The RWA is solely responsible for defining maintenance formulas, flat rates, and billing cycles. • 64. Late fee interest rates, grace periods, and fine structures are configured by RWA accountants. • 65. All transactions processed through integrated payment gateways are subject to third-party processing terms. • 66. Payment gateway settlement times to the RWA bank account typically take 2 to 3 banking days. • 67. We are not responsible for gateway downtime, transaction timeouts, or network payment drops. • 68. Residents must review invoice details for discrepancies before initiating online payments. • 69. Transaction reference numbers issued by banks are the primary proof of payment during disputes. • 70. Payment processing fees and convenience charges are non-refundable once the transaction is cleared. • 71. RWA treasurers must review auto-reconciliation reports before closing monthly accounts sheets. • 72. Refund requests for maintenance double-payments must be raised directly with the RWA management. • 73. We do not collect, store, or process raw credit card numbers or bank account login passwords. • 74. The billing ledger updates in real-time upon receipt of payment status updates from gateways. • 75. Defaulter list generation and penalty calculation are executed automatically based on RWA rules. • 76. Residents agree to pay all applicable utility charge increments configured by the committee. • 77. We are not liable for incorrect tax computations resulting from wrong rates entered by RWA admins. • 78. Chargeback disputes raised by residents on credit card payments are subject to gateway review rules. • 79. Manual cash receipts entered by accountants must be matched against physical bank vouchers. • 80. Automated payment reminders are dispatched to residents based on schedule timings set by RWA. • 81. We reserve the right to restrict online payment features for societies with high chargeback ratios. • 82. Residents must ensure their bank accounts have sufficient funds before scheduling auto-debits. • 83. The RWA agrees to maintain an active bank account linked to the payment gateway routing keys. • 84. Payment receipts are generated in PDF format and sent automatically to the resident email. • 85. We do not guarantee that payment portals will support all local cooperative bank accounts. • 86. RWA accountants must verify opening balances before migrating to MySocietyEntry ledger tools. • 87. Resident pre-payments are kept in credit ledgers and cannot be withdrawn as cash from the platform. • 88. The platform records transaction processing logs for compliance auditing by RWA auditors. • 89. Late fee penalties will continue to accumulate on overdue invoices until the payment is settled. • 90. We are not responsible for double deductions resulting from multiple clicks on the checkout button. • 91. RWA agrees to resolve resident payment disputes within 15 days of receiving the complaint. • 92. Online payment options may be suspended if the RWA bank account fails KYC verification. • 93. We do not provide interest on credit balances held in the resident payment registry.
4. GST Registers, GSTR-1/3B Reports, and Section 194C/194J TDS Accounting Ledger Compliance
• 94. RWA committees are responsible for uploading valid GSTIN details for tax-compliant invoicing. • 95. All GST GSTR-1 and GSTR-3B report extractions are compiled based on RWA transaction history. • 96. The platform calculates GST at configured rates (e.g., 18%) for units exceeding statutory limits. • 97. RWA accountants must verify TDS deductions (Section 194C/194J) on vendor payouts. • 98. Vendor PAN details must be entered correctly to ensure accurate TDS calculations in ledgers. • 99. Section 194C TDS rates of 1% (individuals/HUF) or 2% (others) must be selected by the accountant. • 100. Section 194J TDS rates of 2% or 10% are applied based on professional service categories. • 101. Form 26Q TDS reports generated by the platform are meant strictly for tax filing assistance. • 102. We are not responsible for penalties arising from late filings of GST or TDS returns by the RWA. • 103. The RWA agrees that tax ledgers are subject to adjustment by their designated chartered accountants. • 104. GST input tax credits (ITC) must be claimed manually by the RWA on the government portal. • 105. TDS deduction certificates (Form 16A) must be generated and signed outside our platform. • 106. The RWA must configure correct tax slabs for commercial shops vs residential apartments. • 107. We do not filing taxes directly with the government; we compile reports for filing preparation. • 108. TDS challan numbers and payment details must be entered manually to reconcile tax registers. • 109. GST exemption rules for small societies (turnover under threshold) must be managed by the admin. • 110. Any tax auditing conflicts must be resolved by the RWA's tax consultants. • 111. We do not guarantee real-time synchronization with government GST or income tax portals. • 112. RWA accountants must review Section 194C contract values before applying lower deduction rates. • 113. Reverse Charge Mechanism (RCM) tax calculations are the sole compliance duty of the RWA. • 114. The platform maintains an immutable audit trail of all tax ledger corrections made by users. • 115. GST credit notes and debit notes must be mapped to the original invoice index for tracking. • 116. Tax ledgers are exported in standard Excel formats to support external filing software tools. • 117. The RWA agrees to bear all legal fees resulting from tax disputes with national tax boards. • 118. TDS deductions must be deposited into the government treasury within statutory timelines. • 119. We do not check the validity of vendor GST registration numbers against external portals. • 120. Annual tax summaries are generated based on the society's financial year settings. • 121. RWA treasurers must ensure tax ledger groups are not deleted mid-year to maintain file integrity. • 122. GST invoice numbering sequences must be configured in compliance with tax guidelines. • 123. We are not responsible for discrepancies in GSTR reports due to retroactively modified invoices. • 124. TDS calculations apply strictly to vendor payouts and are not applicable to resident invoices.
5. Gate Operations, Guard Tablets, Visitor OTP Approvals, and Entry Pass Regulations
• 125. Security personnel must verify the identity of visitors before granting gate entry passes. • 126. Visitor photo capture at entrance lanes is mandatory for all unregistered guests. • 127. Security guards must verify the destination flat number with residents via intercom or app. • 128. Visitor OTP verification is required to clear high-security checkpoint entries. • 129. Security guards must not use guard console tablets for personal browsing or entertainment. • 130. The RWA must ensure guard tablets are kept clean, charged, and connected to the network. • 131. Delivery agents from Zomato, Swiggy, and Amazon must show their delivery app logs at the gate. • 132. Gate entry passes generated by residents are valid only for the designated date and time. • 133. We are not liable for security breaches arising from guards bypassing verification rules. • 134. Visitor exit checkouts must be recorded to maintain accurate on-premises count logs. • 135. Guard shift handovers must include physical check-ins of all active visitor files. • 136. Security guards must report tablet hardware damage to the supervisor within 12 hours. • 137. We do not guarantee that the guard console app will work on low-memory Android devices. • 138. Visitor entry rejection by residents must be respected; guards must deny lane clearance. • 139. Daily helper PIN codes are personal and must not be shared with other workers. • 140. The RWA must ensure gates have backup power supply for routers to maintain tablet sync. • 141. Cab drivers must not remain inside the society beyond the designated pickup/drop duration. • 142. Visitor records are purged automatically after 180 days to protect user privacy. • 143. We do not verify the criminal records or backgrounds of visitors checking in at the gates. • 144. Guards must log manual overrides for vehicles without active RFID tags with reasons. • 145. Visitor log books must not be copied or shared with external marketing agencies. • 146. Resident pre-approvals are subject to final gate check-ins by the duty security guard. • 147. We are not responsible for guard console app lag due to local network bandwidth caps. • 148. Delivery packages left at the gate security cabin are stored at the resident's risk. • 149. The RWA agrees to train security guards on how to operate the tablet check-in forms. • 150. Any unauthorized entry due to guard negligence is not the responsibility of MySocietyEntry. • 151. Guards must capture clear license plate photos for vehicle-entry logs when required. • 152. Visitor data access by security supervisors must be logged for audit reviews. • 153. Temporary worker passes must be deactivated immediately upon completion of work. • 154. We reserve the right to collect anonymous usage stats from guard tablets to optimize layouts. • 155. Resident notifications for guest arrivals are delivered best-effort via push APIs.
6. Emergency Panic SOS Sirens, Device Communications, and Liability Disclaimers
• 156. The emergency SOS panic button is designed for local warning broadcasts within the society. • 157. SOS triggers send instant alerts to gate security cabins and selected family contacts. • 158. MySocietyEntry does not contact police, fire department, or medical responders during SOS alerts. • 159. The resident is responsible for dispatching emergency services if required. • 160. We are not liable for delayed notifications due to cell tower drops or device offline states. • 161. Guard console tablets sound a high-decibel alarm when an SOS is triggered by a resident. • 162. Residents must not trigger false SOS alarms; repeat offenders may face dashboard suspension. • 163. The RWA is responsible for establishing emergency response protocols for guard actions. • 164. SOS alerts display flat coordinates, tower name, and registered resident names. • 165. We do not guarantee GPS location accuracy inside high-rise concrete structures. • 166. Family emergency contact lists must be updated by the resident inside the mobile app. • 167. The RWA agrees to test the SOS receiver cabinet screens at least once a month. • 168. We are not liable for panic alarm failures during power outages at the main guard cabin. • 169. SOS logs are stored for security reviews and cannot be modified by guards or admins. • 170. The RWA supervisor must document all actions taken during active SOS alerts. • 171. We do not verify the availability of medical kits or fire gear inside RWA cabins. • 172. SOS alerts are routed through Firebase Cloud Messaging and are subject to network delays. • 173. Residents acknowledge that SOS sirens are audible to security guards on duty. • 174. The SOS function requires active background app permissions on the resident's device. • 175. We are not responsible for panic alert failures on devices with disabled notifications. • 176. The RWA must maintain up-to-date emergency contacts in the digital directory. • 177. Residents must instruct minors on correct usage of the SOS panic button features. • 178. We do not guarantee that guards will respond immediately to flashing SOS console alerts. • 179. SOS alert broadcasts are limited to the borders of the registered housing society. • 180. The platform does not support medical telemetry transmission during emergency alerts. • 181. The RWA agrees to bear all costs for cabin siren speakers integrated with tablets. • 182. False alarms caused by app testing must be cleared by admins with test-log tags. • 183. Emergency alert notifications are encrypted in transit to protect resident locations. • 184. Residents agree to whitelist MySocietyEntry app from battery optimizer settings. • 185. We do not provide emergency ambulance coordination services under any plan. • 186. All emergency SOS logs are archived for legal and society security committee reviews.
7. Domestic Helpers registers, Maid KYC documentation, and Attendance Shift Logs
• 187. Residents must upload domestic helper details including name, photo, and job description. • 188. Helper KYC documents (Aadhaar/Voter ID) must be verified by the resident before registration. • 189. Unique entry passcodes generated for helpers are linked to their active work profiles. • 190. Daily check-in and checkout times of helpers are logged on gate console tablets. • 191. Helpers working across multiple flats must have their schedules mapped to all units. • 192. The RWA may blacklist helpers for policy violations, blocking gate access codes. • 193. Residents are responsible for helper behavior and actions within the society borders. • 194. Helper attendance registers are compiled and visible to mapped unit residents. • 195. Helper salary advances and loan payout records are managed directly by residents. • 196. We do not act as an employer, union, or agency for registered domestic helpers. • 197. Helper profile details must not be shared with external hiring platforms by RWA. • 198. Residents must deactivate helper profiles immediately upon termination of service. • 199. Helper PIN codes are validated in real-time against cloud worker registries. • 200. We are not liable for helper wage calculation disputes or payment defaults. • 201. RWA supervisors must verify helper entry badges during routine security rounds. • 202. Helper background police verification is the exclusive responsibility of the RWA. • 203. We do not guarantee that daily helper logs will be accepted as legal attendance proofs. • 204. Helper records are archived safely and subject to right-to-erase guidelines. • 205. The RWA agrees to display helper safety guidelines at the main gate terminal lanes. • 206. Residents must ensure helpers are aware that their entry/exit times are logged. • 207. We do not store physical copies of helper identity card documents on our local servers. • 208. Daily helper present/absent stats are compiled to help residents plan chores. • 209. Salary advance EMI maps must be reconciled by residents before billing closes. • 210. We are not responsible for helper profile errors due to typo inputs by guards. • 211. Helper shift schedules must align with RWA-configured security gate hours. • 212. Residents agree that helpers are not permitted in restricted society areas. • 213. The platform does not manage helper employee benefits, health insurance, or PF. • 214. Helper check-in alerts are sent via push notifications to resident apps. • 215. RWA admins must review weekly helper attendance logs for security audits. • 216. Helper badge barcode replacements must be registered immediately in the database. • 217. We do not arbitrate helper employment disputes between residents.
8. Vehicle RFID gates access, Boom Barrier hardware, and Parking Spot allocations
• 218. Residents must register vehicle license plate numbers and park in assigned slots. • 219. RFID tags issued to vehicles are non-transferable and must be fixed to the windshield. • 220. Vehicle entry and exit times are logged via automatic RFID scanner reads at gates. • 221. Boom barrier hardware operations are dependent on local network connectivity speeds. • 222. We are not liable for vehicle damage resulting from boom barrier gate closures. • 223. License Plate Recognition (LPR) camera OCR text is stored for verification checks. • 224. Visitor vehicle temporary parking allocations are managed by duty security guards. • 225. Residents must not park in common areas, fire lanes, or slots assigned to neighbors. • 226. The RWA may issue parking fines and invoices through the society finance module. • 227. RFID barrier override logs are recorded with guard IDs for security tracking. • 228. We do not guarantee the compatibility of RFID tags with third-party barrier controllers. • 229. Residents must report lost or damaged RFID tags to the RWA admin for deactivation. • 230. Vehicle plate capture images are stored for 180 days before database purging. • 231. The RWA is responsible for parking slot demarcation and physical barrier setups. • 232. We are not responsible for vehicle theft, damage, or accidents inside parking zones. • 233. FASTag billing integration validation checkups are subject to bank API uptimes. • 234. Unregistered vehicle entry requires manual entry pass generation at gate consoles. • 235. RFID tags are scanned at entry and exit loops to update vehicle location states. • 236. The RWA agrees to maintain barrier sensors to prevent vehicle tailgating issues. • 237. Parking fine disputes must be resolved directly with the RWA parking committee. • 238. We do not provide GPS tracking for vehicles parked inside basement levels. • 239. Resident parking allocations are verified before vehicle gate passes are issued. • 240. Vehicle access logs can be accessed by RWA admins during security investigations. • 241. We are not liable for barrier sensor failures due to dust or water blockages. • 242. RFID card reissue fees are configured and collected exclusively by the RWA. • 243. Vehicle entries during system offline modes must be logged manually by guards. • 244. The RWA must ensure RFID readers have correct IP configurations on the subnet. • 245. Residents agree that unregistered visitor vehicles may be denied entrance lanes. • 246. We do not manage EV charging slot payments or grid load distribution rules. • 247. Vehicle registration document scans are stored securely and encrypted in backups. • 248. Automated gate opening triggers require active RFID tag signatures on windshields.
9. Subscription Tiers (Bronze, Silver, Gold, Platinum), Billing Terms, and Default Suspensions
• 249. MySocietyEntry subscription tiers (Bronze, Silver, Gold, Platinum) carry distinct module limits. • 250. Subscription invoice payments must be settled within 15 days of the bill date. • 251. Overdue balances beyond the grace period will lead to administrative dashboard suspension. • 252. Bronze tier plans are limited to basic gate security logbook registers. • 253. Gold and Platinum tier plans include advanced financial ERP, tax registers, and LPR integrations. • 254. Free trial periods carry zero charges but are limited to 30 days of platform usage. • 255. The RWA agrees to pay committed subscription rates based on total flat counts. • 256. We do not provide prorated refunds for mid-cycle subscription cancellations. • 257. Voluntary plan downgrades take effect from the start of the next billing cycle. • 258. We reserve the right to modify subscription pricing with a 60-day notice to RWA. • 259. Suspended accounts are locked out of all admin dashboard features and resident tools. • 260. Re-activation of suspended accounts requires clearing all dues and setup fees. • 261. Onboarding configuration charges and custom domain setups are non-refundable. • 262. We are not liable for RWA database access losses during payment suspension phases. • 263. The RWA is responsible for downloading billing transaction history before cancellation. • 264. Subscription agreements are auto-renewed unless cancelled 30 days prior to expiry. • 265. We do not include physical guard tablet hardware costs in subscription licenses. • 266. SLA priority support response times apply strictly to Gold and Platinum plans. • 267. Excess flat registrations beyond the plan tier limits will trigger auto-upgrades. • 268. We reserve the right to cancel subscriptions for societies with persistent default issues. • 269. Tax invoices for subscription charges are generated and sent to the RWA email. • 270. The RWA agrees to bear all bank remittance fees for subscription transactions. • 271. Data migration packages from old portals are billed as custom setup scopes. • 272. We do not offer custom software modifications under standard subscription plans. • 273. API rate limits apply to all plans to ensure database performance stability. • 274. The RWA must designate an active billing contact to receive invoice notifications. • 275. Payment defaults by the RWA do not erase resident historical data registers. • 276. We do not provide physical server hosting on-premises under standard plans. • 277. Subscription payments made in cash to representative agents are strictly invalid. • 278. The RWA agrees that all software license titles remain with MySocietyEntry. • 279. We reserve the right to audit society unit registers to verify billing flat counts.
10. General Legal Terms, Dispute Resolution Forums, Severability, and Liability Limitations
• 280. These Terms are governed by and construed in accordance with national laws. • 281. All disputes arising from these Terms will be subject to exclusive local jurisdictions. • 282. Any claim must be resolved through binding arbitration before seeking court relief. • 283. Users agree to waive their right to participate in class-action lawsuits against us. • 284. If any provision of these Terms is found invalid, the remaining terms remain in effect. • 285. Our total liability for any claim is capped at the subscription fees paid in the last 12 months. • 286. We are not liable for indirect, incidental, or consequential damages of any kind. • 287. Failure to enforce any right under these Terms does not constitute a waiver of that right. • 288. Force Majeure: We are not liable for failures due to natural disasters, power grid failures, or war. • 289. These Terms constitute the entire agreement between the User and MySocietyEntry Corporation. • 290. Users cannot assign their rights under these Terms without our prior written consent. • 291. Intellectual Property: All logos, code structures, and designs belong to us. • 292. We reserve the right to update these Terms and publish them on our legal domain. • 293. Continued use of the platform after Terms updates constitutes acceptance of changes. • 294. RWA agrees to indemnify us against all claims arising from illegal usage of dashboards. • 295. We do not guarantee that the software will be completely error-free or uninterrupted. • 296. Residents agree to defend us against claims regarding domestic helper privacy complaints. • 297. Export Controls: Users agree not to export our tools in violation of trade laws. • 298. All legal notices to us must be sent to legal@mysocietyentry.com via registered mail. • 299. Third-party software components used in our build are licensed under standard terms. • 300. We do not waive our rights if we delay taking action on terms violations. • 301. Arbitration hearings will be conducted in the English language. • 302. Severability: Invalid clauses will be replaced with valid ones that match intent. • 303. These Terms survive the termination of your account or subscription plan. • 304. We do not guarantee that the software matches specific local housing bylaws. • 305. RWA represents that they have the legal authority to sign these software terms. • 306. We are not liable for database breaches resulting from AWS hosting network issues. • 307. User comments, feedback, and reviews can be used by us for promotional purposes. • 308. Legal claims must be filed within 1 year of the incident date to be valid. • 309. The platform compliance stance aligns with standard ISO 27001 ISMS policies. • 310. All decisions made by our legal panel regarding terms disputes are final.
Need clarification?
If you have any questions regarding these terms, please contact our administrative and legal team.
Contact Administration