trelaCRMTerms of ServicePrivacy PolicyData Processing Agreement

Data Processing Agreement — TRELA CRM

DRAFT — for review by counsel. Not legal advice and not yet in force. Version 2026-11-21-v2-draft. Text in [BRACKETS] is still to be filled in. Points marked OPEN POINT need a decision.

Last updated: 21 November 2026 · Effective date: the date the Customer accepts it at sign-up.

This Data Processing Agreement ("DPA") is between:

  1. Shahi Moso Propverse Private Limited, a private limited company incorporated in India (CIN [CIN]), with its registered office at U210, NPVIL, Jahajgarh, Pawala Khusropur, Gurugram 122006, Haryana, which operates TRELA CRM at crm.trela.in ("TRELA", the "Processor"); and
  2. the business that accepted this DPA when creating a TRELA CRM account (the "Customer", the "Fiduciary").

It forms part of the Terms of Service. Under the Digital Personal Data Protection Act, 2023 (the "Act"), a Data Fiduciary may engage a Data Processor to process personal data on its behalf only under a valid contract. This DPA is that contract. It is written to apply from the day it is accepted, including before the Act's remaining provisions and the Digital Personal Data Protection Rules, 2025 (the "Rules") come into force. OPEN POINT: counsel to confirm commencement dates (we understand most of the Rules apply from about 13 May 2027).

1. Definitions

"Personal Data", "Data Principal", "Data Fiduciary", "Data Processor", "Processing", "Consent Manager" and "Personal Data Breach" have the meanings given in the Act. "Customer Personal Data" means Personal Data that TRELA processes on the Customer's behalf through the Service. "Applicable Law" means the Act, the Rules, the Information Technology Act, 2000 and the rules and directions under it (including the CERT-In directions of 28 April 2022), and any other Indian law that applies to the Processing. Other capitalised words have the meanings in the Terms.

2. Roles

  1. The Customer is the Data Fiduciary for Customer Personal Data and decides why and how it is processed.
  2. TRELA is the Data Processor and processes Customer Personal Data only on the Customer's behalf.
  3. For personal data of the Customer's owners, staff and billing contacts that TRELA uses for its own purposes (running accounts, security, billing and legal compliance), TRELA is itself a Data Fiduciary, as the Privacy Policy explains.

3. Details of processing

The subject matter, nature, purpose and duration of the Processing, the kinds of Personal Data and the categories of Data Principals are set out in Annex A.

4. TRELA's obligations

TRELA will:

  1. process Customer Personal Data only on the Customer's documented instructions — this DPA, the Terms, and the Customer's use of the Service's settings and features — unless Applicable Law requires otherwise, in which case TRELA will tell the Customer first where the law allows;
  2. not sell Customer Personal Data; use it for advertising, profiling or any purpose of its own; share it with the trela.in network or with other customers; or use it to train artificial intelligence models;
  3. not combine Customer Personal Data with data from other customers or sources, except as needed to run the Service for the Customer (for example, the shared WhatsApp routing record in clause 6, once available);
  4. ensure that everyone who can access Customer Personal Data is bound by a duty of confidentiality and has access only as needed for their role, and that access by TRELA staff is restricted and logged;
  5. implement and maintain the security measures in Annex B, or measures at least as protective, review them at least once a year, and keep them in line with the reasonable security safeguards required by Applicable Law;
  6. keep the logs and records Applicable Law requires of a Data Processor, including logs of Processing and access for at least one year and system logs for at least 180 days within India as the CERT-In directions require, so that incidents can be detected and investigated;
  7. process and store Customer Personal Data in [INDIA / REGION], and transfer it outside India only to the sub-processors in Annex C, as Applicable Law allows and under written terms;
  8. tell the Customer promptly if it believes an instruction breaks Applicable Law;
  9. not engage another processor except under clause 7.

5. The Customer's obligations

The Customer is responsible for, and confirms that:

  1. it has a lawful ground — and, where required, valid consent — to collect Customer Personal Data and to have it processed through TRELA, and has given Data Principals any notice the law requires;
  2. it will keep consent records up to date (the Service has tools for this) and act on withdrawal of consent;
  3. it will contact its clients only with their permission, and comply with the Telecom Regulatory Authority of India's rules on unsolicited commercial communication and, once WhatsApp features are available, Meta's policies;
  4. it keeps Customer Personal Data accurate, updates it promptly, and removes data it no longer needs;
  5. it uses sensible access settings — including who can see full phone numbers, export or reassign records — and removes people who leave;
  6. it responds to requests and grievances from its Data Principals, with TRELA's help under clause 9;
  7. it will not enter children's data or other especially sensitive data without a lawful basis and without telling TRELA in advance;
  8. its instructions to TRELA comply with Applicable Law.

The Customer remains responsible to Data Principals and authorities as the Data Fiduciary.

6. WhatsApp features (coming soon)

TRELA's WhatsApp features are not yet available. When TRELA makes them available and the Customer switches them on, this clause will apply in addition to any terms TRELA shows at that time:

  1. Until the Customer connects its own WhatsApp number, its clients may reach it through a WhatsApp number shared by several TRELA customers. Each customer's link carries its own code, which TRELA uses to send each conversation only to the customer it was meant for.
  2. To do this, TRELA keeps a record of each client's WhatsApp number and the customer they last messaged. TRELA uses it only to deliver messages to the right customer, never shows one customer another customer's conversations, and deletes a customer's routing for a client when that customer erases the client, or 12 months after the client's last message.
  3. The first automatic reply a client receives from the Customer will carry a short notice, which the Customer cannot remove, that messages are handled through TRELA, with a link to TRELA's privacy information. The Customer remains responsible for any notice the law requires of it as Data Fiduciary and for the text of any automatic reply it writes. The automatic reply answers the client's message and must not be used for marketing.

7. Sub-processors

  1. The Customer authorises TRELA to engage the sub-processors listed in Annex C.
  2. TRELA will bind each sub-processor by written contract to data protection obligations no less protective than this DPA, and remains responsible to the Customer for their performance.
  3. TRELA will give at least 30 days' notice, by email and in the Service, before adding or replacing a sub-processor that processes Customer Personal Data. The Customer may object on reasonable data protection grounds within 15 days. If the parties cannot resolve the objection, the Customer may end the affected Service and receive a pro-rata refund of prepaid fees for the unused period.

8. Personal Data Breaches

  1. TRELA will notify the Customer without undue delay, and in any case within 24 hours, after becoming aware of a Personal Data Breach affecting Customer Personal Data, so that the Customer can meet its own duty to inform the Data Protection Board of India and affected Data Principals.
  2. The notice will describe, as far as known: the nature, extent, timing and location of the breach; the kinds of data and approximate number of Data Principals affected; its likely consequences; what TRELA has done and will do to contain it; what the Customer and Data Principals can do to protect themselves; and a contact person. TRELA will provide further details as they become known.
  3. TRELA will promptly take reasonable steps to contain, investigate and remedy the breach, preserve relevant evidence, and help the Customer meet its obligations to the Board, Data Principals and, where relevant, CERT-In.
  4. TRELA will report incidents to CERT-In where its directions require TRELA itself to do so, and will tell the Customer when a report concerns the Customer's data.
  5. A breach notification is not an admission of fault or liability.

9. Helping the Customer with Data Principal requests

  1. The Service has tools to view, correct, export and erase a contact's data, to record consent and its withdrawal, and to delete records. The Customer can use them to answer requests.
  2. If TRELA receives a request directly from a Data Principal about Customer Personal Data, it will pass it to the Customer without undue delay and will not respond itself, other than to say it has done so, unless the law requires otherwise.
  3. On the Customer's reasonable written request, TRELA will help with anything the tools cannot do, within 10 working days. TRELA may charge reasonable fees for requests that need exceptional effort, and will tell the Customer before doing so.
  4. When the Customer erases a contact with the erasure tool, TRELA removes the person's name, contact details, notes and history from live systems. Records that no longer identify the person (for example the amount and date of a closed deal) may remain for the Customer's own accounts. Backup copies are overwritten on the backup cycle in Annex B.
  5. TRELA will reasonably help the Customer with any data protection impact assessment or audit the Act requires of it, at the Customer's reasonable cost where the work is substantial.

10. Audit and information

TRELA will give the Customer the information reasonably needed to show compliance with this DPA, including answers to one reasonable security questionnaire a year. If that is not enough, the Customer may, on at least 30 days' written notice and not more than once a year (or at any time after a Personal Data Breach), have TRELA's relevant controls audited by a reputable independent auditor bound by confidentiality, during business hours, in a way that does not disrupt TRELA or expose other customers' data. Each party bears its own costs, unless the audit finds a material breach by TRELA, in which case TRELA bears the reasonable audit costs.

11. End of processing and return of data

  1. During the term the Customer can export its data at any time.
  2. After the Terms end, TRELA will keep Customer Personal Data available for export for 30 days, then delete it from live systems within a further 30 days, and from backups on their normal cycle (Annex B).
  3. TRELA may keep data that Applicable Law requires it to keep — for example invoices and payment records (kept for eight years) and audit logs — and will protect it and use it only for that purpose, for only as long as required.
  4. On request, TRELA will confirm deletion in writing.

12. Liability

The limitations and exclusions of liability in the Terms apply to this DPA. Nothing in this DPA limits liability that cannot be limited by law. Each party is responsible for penalties under the Act arising from its own failure to comply. OPEN POINT: counsel to decide whether a separate, higher cap and mutual indemnities should apply to data protection breaches.

13. General

  1. This DPA lasts for as long as TRELA processes Customer Personal Data.
  2. If this DPA conflicts with the Terms on Personal Data, this DPA prevails.
  3. This DPA is governed by the laws of India. Disputes are settled as the Terms provide, and the courts at Gurugram, Haryana have exclusive jurisdiction.
  4. TRELA may update this DPA to reflect changes in law or the Service, with at least 30 days' notice. If a change materially reduces the protection of Customer Personal Data, the Customer may end the Terms before it takes effect and receive a pro-rata refund of prepaid fees.
  5. Contacts. TRELA's data protection contact and Grievance Officer: Mohit Arora, arora.mohit@trela.in; general and legal notices: admin@trela.in and the registered office. The Customer's contact is the account owner's email address.

Annex A — Details of processing

Item Details
Subject matter Providing TRELA CRM, a customer relationship management service, to a real estate business
Nature of processing Collecting through forms, imports (files and Google Sheets) and website-form webhooks; storing, organising, matching, displaying, sharing by link, exporting, notifying about and deleting records; sending reminders and notifications. Once available: receiving WhatsApp messages from registered staff and from the Customer's clients, turning them into records, sending one automatic reply on the Customer's behalf, and routing a client's later messages to the Customer
Purpose To let the Customer manage its clients, requirements, properties, leads, site visits, tasks, deals and team
Duration The term of the Terms plus the return and deletion periods in clause 11
Data Principals The Customer's clients, prospects and leads (buyers, tenants, investors); property owners and landlords; channel partners and other business contacts; the Customer's staff where they appear in records
Kinds of personal data Names; mobile numbers and email addresses; property requirements and preferences (budget, location, type, size); interaction notes, call and message logs, site visit feedback; consent records; lead source and enquiry text; important dates such as birthdays where the Customer records them; documents or photos if uploaded; assignment and ownership details; deal values and commission. Once WhatsApp features are available: WhatsApp profile names, message text and time, the type of media sent (not the media itself), and click-to-WhatsApp advertisement details
Special categories and children Not intended. The Customer must not enter children's data or other especially sensitive data without telling TRELA first
Frequency Continuous while the Service is in use

Annex B — Security measures

OPEN POINT: every item must be checked against the live environment before launch. Items marked ✔ are built into the product today; items marked ☐ depend on hosting and operations and must be confirmed.

  • ✔ Each customer's data is logically separated by database row-level security.
  • ✔ Role-based access: owners control who sees all, team-only or own records; who sees full phone numbers; who can export; and who can manage settings. Changes take effect at once.
  • ✔ Passwords stored only as salted hashes; email verification; one-time links and codes stored only as hashes; limits on repeated failed attempts; sessions can be ended on all devices.
  • ✔ Audit log of sensitive actions (permission changes, exports, erasure, reassignments, offboarding).
  • ✔ Uploaded photos are served only through short-lived signed links, and only real image files are accepted.
  • ✔ Webhooks from third parties are verified by signature; push endpoints are limited to known services.
  • ✔ Tools to record consent, export a contact's data and erase it.
  • ☐ Encryption in transit (TLS 1.2 or higher) on all connections, and encryption at rest for databases, file storage and backups.
  • ☐ Production secrets in a managed secrets store; no shared accounts; multi-factor authentication for all staff with production access; access reviewed every quarter.
  • ☐ Automated backups with point-in-time recovery, restore tests at least twice a year, and backup retention of [35] days.
  • ☐ Centralised logging, monitoring and alerting; log retention as in clause 4.6.
  • ☐ Vulnerability management, timely security updates, and an independent security test before launch and at least yearly.
  • ☐ Written incident response plan, staff confidentiality undertakings and yearly security training.

Annex C — Sub-processors

OPEN POINT: complete once hosting and email providers are chosen.

Sub-processor Service Location Data involved
[CLOUD HOSTING PROVIDER] Hosting, database, file storage, backups [REGION] All Customer Personal Data
[EMAIL PROVIDER] Verification, invitation, sign-in and notification emails [REGION] Staff names and email addresses; notification text, which may include a client's name
Browser push services (Google, Apple, Mozilla, Microsoft) Delivering notifications to devices Outside India possible Notification text, which may include a client's name
Razorpay (when paid plans start) Payments India Billing contact and payment status (no client data)
Meta Platforms, Inc. / WhatsApp (when WhatsApp features become available) WhatsApp Business messaging Outside India possible Messages staff send to the assistant (which may include client details they type); messages from the Customer's clients, their WhatsApp profile name and number, advertisement details, and automatic replies