Terms of Use - The Real Connect Terms of Use

This Annexure forms part of the Service Agreement between the Developer/Individual ("Client") and The Real Connect ("TRC"). The name of the Developer/Individual Shall be mentioned below.

1. Nature of Service

TRC is an information dissemination platform designed to seed project details, developer branding, sales contacts, and collaterals into Channel Partners' (CPs) Smart Phones through structured WhatsApp communication.

TRC is not:
  • A lead-generation service
  • A sales conversion system
  • A transaction facilitator

TRC is not involved in outcomes such as leads, walk-ins, or closures, transactions.

2. Messaging Infrastructure

TRC operates using WhatsApp Business API (Meta), approved Business Solution Providers (BSPs), and cloud servers.

Message delivery, approval, and uptime are dependent on these third-party systems.

3. Account Activation

The TRC account, onboarding process, Meta setup, template approvals, and all campaign activity will be activated only upon receipt of full payment of the invoice issued to the Developer.

4. No Refund Policy

All payments to TRC—including subscriptions, message usage, setup fees, campaign costs, and creative charges—are non-refundable under all circumstances, except in cases covered under Clause 5. Once messages are sent the usage is considered consumed. Wallet use will be only for Delivered messages only which is visible on Dashboard.

5. Service Downtime

A refund/credit will be considered only if TRC-controlled systems are down for 72 consecutive hours. Refunds do NOT apply to downtime caused by:

  • Meta/WhatsApp outages or throttling
  • BSP (Business Solution Provider) issues
  • Template rejections
  • Incorrect Developer data
  • Network/handset issues
  • External or force-majeure events

6. WhatsApp Number Blocking / Restrictions

  • Meta may impose restrictions, rate-limiting, quality downgrades, or permanent bans.
  • TRC is not responsible for such actions.
  • TRC will support reinstatement efforts but recovery is not guaranteed.
  • If a number cannot be restored, TRC will onboard a new number without charging any TRC onboarding fee.
  • TRC is not liable for losses caused by number bans or restrictions or from Complaints or for any other reason like message going to non channel partner etc.

7. Meta (WhatsApp API) Onboarding Requirements

7.1 Dedicated Number

The Developer must provide a fresh/unused mobile number not registered on WhatsApp.

This number remains under Developer ownership and the Developer should keep this number on for incoming calls.

7.2 Verification

Meta requires OTPs, documents, business verification, and compliance steps. TRC will assist, but OTPs must be completed by the Developer.

7.3 Display Name & Logo

Developer must specify a Display Name (Company/Group/Project).

Meta approval depends on policy compliance and availability.

Recommended: onboard with the Developer's name, allowing all projects under one verified brand identity.

7.4 Timeline

Meta onboarding takes approx. 2 working days, subject to verification queues.

7.5 Testing & Training

After onboarding, TRC will perform testing and conduct a training session for the Developer's team.

8. Content Responsibility

Developer must provide correct, RERA-compliant project information, creatives, and pricing. TRC is not responsible for verifying Developer-provided content.

9. Billing, Usage & Payment Terms

  • All invoices must be cleared before account activation.
  • Usage exceeding agreed limits will be billed separately.
  • Developer must manage TDS deductions and timely GST payment.
  • Unpaid dues may result in suspension of messaging.

10. Liability Limits

TRC shall not be liable or held accountable for:

  • Sales performance
  • Lead generation
  • CP responsiveness due to Message Quality etc.
  • Walk-ins or site visits
  • Market conditions
  • Commercial losses of any kind

TRC's responsibility ends after successful dispatch of approved communication.

11. Termination

  • Both parties may terminate with 15 days written notice.
  • All dues must be cleared prior to discontinuation.
  • Unused subscription balances are non-refundable.

12. Acceptance

By engaging TRC, the Developer acknowledges and accepts:

  • TRC is purely an information distribution system
  • No sales results are guaranteed
  • Messaging behaviour is controlled by Meta
  • All services and payments are governed by this Annexure

13. Template Approval

All Templates Sent by the Developer Teams must be approved by the Developer and the sending control remains with the Developer however for testing purposes TRC may use a few credits. The Testing will be done with Developers Teams.

14. Personal Use by Sourcing Managers / Sales Managers

If any Sourcing Manager, Sales Manager, or employee of the Developer uses The Real Connect ("TRC") platform in a personal or individual capacity, the following conditions apply:

Mandatory Written Approval

The individual must obtain an email confirmation from:

  • The Developer's Marketing Head, or
  • Team Leader (TL), or
  • Senior Management

confirming that they are permitted to use the TRC platform for project communication.

Personal Risk & Responsibility

All usage, messaging, communication, and approvals carried out by the individual shall be at their own risk and responsibility.

TRC will not be liable for:

  • Miscommunication
  • Incorrect project details
  • Misuse of the system
  • Violations of Developer policies
  • Unapproved or unauthorized usage
No Liability on TRC
  • The Developer shall indemnify TRC against any claim arising due to unauthorized or personal usage by its employees.
Developer Accountability/Sales Team Managers
  • It is the Developer's responsibility to ensure that all internal permissions, approvals, and compliance measures are completed before granting access to their team members.

15. Data Protection & Privacy

TRC has its own data of Channel Partners/Agents

TRC does not sell, share, or misuse any Developer data uploaded by the Developer/Sales Teams etc.

All data shared with TRC is used only for executing the agreed WhatsApp communication services.

16. Compliance & Content Responsibility

All messaging content, creatives, prices, and project details are provided and approved by the Developer.

The Developer is responsible for ensuring all information is accurate and compliant with RERA and Meta/WhatsApp policies.

17. Indemnity

The Developer agrees to indemnify and hold TRC harmless against any claims, penalties, or losses arising from the content, use of data, or unauthorized system use by its team members.

18. Intellectual Property

All templates, message formats, and creatives designed by TRC remain TRC's intellectual property unless otherwise agreed in writing. The Developer receives permission to use these only within their TRC account.

19. Force Majeure

TRC is not responsible for delays or non-performance caused by outages, technical failures, network issues, Meta/BSP downtime, or any events beyond reasonable control.

20. Governing Law & Jurisdiction

These Terms are governed by Indian law.

Any disputes will fall under the exclusive jurisdiction of Mumbai courts.

I agree and confirm that I have read the above terms and conditions.

© 2025 The Real Connect