What the Mygate-Adonmo deal puts under one roof
On 21 October 2026, Entrackr reported that Mygate and Adonmo are set to merge, with Adonmo ceasing to exist as a separate entity. The transaction is still subject to definitive agreements and customary closing conditions, so nothing in this post treats it as done. What matters for insurance buyers is the shape of the business that would come out the other side.
Mygate provides visitor management, security, accounting and community engagement for gated residential communities. Its turnover, as reported by Entrackr, grew from Rs 96 crore in FY24 to Rs 171 crore in FY25 and Rs 229 crore in FY26, a 34% rise in the latest year. Adonmo runs an ambient digital advertising platform built on a cloud-connected network of screens placed inside residential communities.
Eternal, which invested Rs 112 crore in Adonmo in January 2022, would swap that holding for about 4.4% of Mygate on a fully diluted basis, valued at Rs 156 crore. By simple arithmetic that values Mygate at roughly Rs 3,500 crore on a fully diluted basis, though that is an implied figure, not one either company has stated.
Put plainly, the combined company would hold two kinds of asset in the same physical places: a record of who enters a residential society, when, and to see whom, and a set of internet-connected screens that show advertising to the people living there. That combination changes the cyber, privacy and professional liability profile of both businesses, and it changes what a careful buyer of insurance should be asking before and after closing.
Why a society-management app is a distinct cyber risk
A society-management platform is not a typical consumer app. It sits between three parties: the resident, the resident welfare association (RWA) or facility manager that signs the contract, and the visitor, delivery agent or domestic worker who never chose the app at all. Each of them has data on the platform.
The categories of data that a visitor-management and community platform typically handles include:
- Visitor names, mobile numbers and photographs captured at the gate
- Vehicle registration numbers and entry and exit timestamps
- Attendance and identity records for domestic staff, drivers and security guards
- Resident flat numbers, family details and pre-approved guest lists
- Maintenance dues, payment histories and society accounting records
Individually most of these look mundane. Together they form a movement log for a residential population: who is home, when they leave, who visits them and how often. A breach of that log is a physical security problem, not only a privacy one, which is why loss scenarios for this sector should include stalking, burglary facilitation and targeted fraud, not just notification costs.
There is also an availability angle. When a gate approval system is the only way security staff verify entry, an outage or ransomware event becomes an operational failure at hundreds of sites at once. That is the kind of correlated, many-clients-at-once event that cyber underwriters price differently from a single-insured breach, a theme we cover in cyber limit sizing for Indian firms.
Adding a network of cloud-connected screens widens the attack surface again. Each screen is an endpoint inside a residential complex, managed remotely, and capable of displaying whatever the content management system sends it. A compromised screen network is a reputational event (offensive or fraudulent content in a lobby) as well as a possible pivot point if screens share infrastructure with the visitor platform.
DPDP: consent and purpose limitation when resident data meets advertising
The Digital Personal Data Protection Act, 2023 is built around consent tied to a specified purpose. A visitor who gives a name and mobile number at a gate does so to get in. A resident who records a guest or a domestic worker does so for security. Neither purpose obviously covers using the same data to select, target or measure advertising on a screen in the lift lobby.
The questions a merged platform has to answer
- Who is the Data Fiduciary? Depending on the contract, the RWA may decide why data is collected and the platform may process it on the RWA's behalf, or the platform may be determining purposes itself. The answer decides who carries which obligations and who the Data Protection Board would look at first.
- Is any visitor or resident data feeding ad decisions? Footfall, occupancy patterns or flat-level profiles used for targeting would be a new purpose needing fresh, specific consent, not a line buried in updated terms.
- Are children in scope? The Act requires verifiable parental consent for processing children's personal data and bars tracking, behavioural monitoring and targeted advertising directed at children. Screens in residential lobbies are seen by children every day.
- Can consent be withdrawn as easily as it was given? For visitors who never installed the app, that is a practical design problem.
The safest structural answer for a merged business is hard separation: the advertising stack receives no personal data from the visitor platform, and that separation is documented, tested and written into both RWA contracts and privacy notices. If the business intends to combine data, the consent journey has to be rebuilt before the data flows, not after. Our note on DPDP enforcement and the Data Protection Board sets out how inquiries are likely to run and which costs a cyber policy can respond to.
Structuring cyber cover for a merged proptech platform
A platform with this profile needs a cyber insurance programme that answers four separate questions rather than one generic limit.
First-party and third-party sections
On the first-party side, the priorities are incident response, forensic costs, data restoration and business interruption from a security event, with a waiting period short enough to matter for a gate system that cannot be down for long. On the third-party side, the policy should respond to privacy liability claims from residents and visitors and to network security liability claims from RWAs whose operations were disrupted.
Points worth negotiating explicitly:
- Regulatory defence costs for proceedings before the Data Protection Board, and for CERT-In reporting obligations, which require notifying specified incidents within six hours of noticing them
- Notification costs for affected Data Principals, which in a residential platform can mean very large numbers of individuals from a single incident
- IoT and connected-device coverage, so that a compromise of the screen network is not argued out of scope as "hardware" or "operational technology"
- Media liability for content displayed on screens, including content injected by an attacker
- Dependent business interruption for the cloud providers that both the visitor platform and the screen network rely on
Aggregation and limit adequacy
Underwriters will look hard at how many communities sit on a single tenant, a single cloud region or a single admin console. A platform that can show segmentation between societies, between the visitor stack and the ad stack, and between production and analytics environments will usually get better terms than one that cannot. Retentions should be set with the merged incident frequency in mind, not the smaller of the two legacy programmes.
Tech E&O owed to RWAs and facility managers
Cyber insurance responds to security and privacy failures. It does not usually respond to the platform simply getting its service wrong. That is the job of technology errors and omissions cover, a form of professional indemnity.
For a society-management platform, the realistic E&O claim scenarios are specific:
- An accounting module miscalculates maintenance dues or penalty interest, and the RWA faces resident disputes and reconciliation costs
- A gate approval failure lets an unauthorised person in, or locks out a legitimate visitor at a critical moment
- A software update corrupts guest lists or staff attendance records used for payroll by the facility manager
- Ad screens fail to run campaigns as contracted, and the advertiser claims for lost value
Two drafting issues come up again and again. First, contractual liability exclusions: many E&O wordings exclude liability assumed under contract beyond what would exist in law, so indemnities and uncapped service credits in RWA agreements may sit outside cover. Second, the cyber and E&O boundary: a single gate outage caused by a botched update with a security dimension can be argued into both policies or neither. Placing both lines with aligned definitions, or with a combined tech and cyber form, reduces that gap.
The merger itself adds a third issue. Adonmo's contracts are with advertisers and with societies that host screens; Mygate's are with RWAs and residents. After a merger, the surviving entity inherits both sets of obligations. The E&O schedule, insured services definition and any exclusions for advertising activity need to be reviewed so that the new business lines are actually described in the policy.
Deal points: W&I, run-off and change of control
Even when a deal is a share swap with an existing investor rolling over, the insurance mechanics of a merger matter. The general approach is in our guide to insurance due diligence for mergers and acquisitions in India; the points specific to this kind of proptech combination are below.
Warranty and indemnity insurance
If the definitive agreements include business warranties, warranty and indemnity (W&I) insurance can backstop breaches of data protection, IT and compliance warranties. Expect underwriters to scrutinise data-room evidence on consent records, breach history and vendor security. Anything disclosed as a known issue, such as an unresolved consent gap or a past incident, will normally be excluded, and DPDP fines are frequently carved out as uninsurable. Buyers should push for specific, testable data warranties rather than broad statements that underwriters will exclude.
Run-off and change of control
Because Adonmo would cease to exist as a separate entity, its own claims-made policies need attention before closing:
- Purchase extended reporting or run-off on Adonmo's cyber and E&O policies so that claims made after closing, for acts before closing, still have a home
- Put D&O run-off, commonly for six years, in place for Adonmo's former directors and officers
- Check whether the surviving entity's policies give any cover for prior acts of the merged business; most will not by default
Mygate's own policies will typically contain change-of-control or merger clauses requiring notice to insurers and, in some cases, triggering automatic run-off or re-underwriting. Notify insurers in good time. If the new shareholding brings board nominees, confirm the D&O programme covers outside directorships and that limits remain adequate for a larger company with a wider investor base.
A practical checklist for platforms, RWAs and investors
The insurance work splits naturally by who is reading.
For the platform:
- Map every data flow between the visitor platform and the screen network and document whether any personal data crosses
- Rebuild consent notices for any new purpose before data moves, with specific handling for children
- Re-market cyber and tech E&O as a merged risk, with IoT, media and dependent BI cover addressed in the wording
- Buy run-off on legacy Adonmo policies and confirm D&O run-off for its former board
For RWAs and facility managers: ask the platform for its updated privacy notice and the data processing terms that apply after the merger. Check whether your agreement names the RWA as a data fiduciary, and whether the platform's indemnity for data breaches is backed by an insurance certificate showing cyber and E&O limits. RWAs also have their own exposure as committees handling resident data, which a modest liability or D&O policy for the committee can address.
For investors: confirm W&I scope, specific data warranties and known-issue exclusions, and see evidence that the merged entity's insurance has been reviewed rather than simply continued. A platform that holds a residential population's movement log and adds advertising screens to the same buildings should be able to show, in documents, how the two are kept apart.