Skip to content
HomelyBlock

Privacy policy

What HomelyBlock stores, who can see it, and which Indian privacy duties are already in force.

Last updated 18 November 2026. This page describes the application and the official Indian sources reviewed while writing it. It is not a legal opinion, a certification, or a claim that every duty is already in force. A qualified adviser must approve it before a public launch.

What this policy covers

HomelyBlock is a web application for residential society operations. This policy explains what the application stores and who can see it. It does not decide, for every society, whether the platform operator or the society is the data fiduciary. That depends on who determines the purpose and means of processing, and on the contract between them.

Who operates this deployment

The registered legal name, address, GSTIN, and CIN of the organisation that operates this deployment are not configured. Do not treat any company name or office address as belonging to HomelyBlock until the operator publishes them. This is a launch blocker.

How to reach the operator

Use the contact form for platform questions. Society complaints, visitor issues, and maintenance disputes belong with the society administrator inside the society, not in this form. Contact

A support email address has not been published. The contact form stores the message for the operator.

A named grievance officer and a published privacy contact are not configured. Publishing them is a launch blocker. Do not assume a government portal or a personal inbox is the grievance channel.

Information the application stores

  • Account and authentication information: the sign-in identifier from the configured authentication service, display name, email, and optional phone. HomelyBlock does not store passwords.
  • The registration choice of society administrator or resident. Platform owner is not a public registration choice.
  • Society and membership information: society address, buildings, units, role, membership status, and the unit linked to a membership.
  • Household information entered by a resident or administrator, including a name, relationship, and optional contact details. Household members do not receive separate logins. A record may describe a child who lives in the home.
  • Billing and transaction records: maintenance configuration, bills, and payments an administrator records. HomelyBlock does not collect card or UPI payments and does not receive a bank confirmation.
  • Complaint text, status, comments, and, only if the operator explicitly enables storage, complaint images.
  • Visitor names and visit details entered for expected or walk-in visitors.
  • Notices and whether a person has opened a notice.
  • Service-directory contacts published by an administrator.
  • Messages sent through the public contact form.
  • An audit log of selected administrative actions, with the actor, action, resource, and time. The log is not a complete record of every login.
  • Technical information needed to keep the session, including essential authentication cookies. The product does not run analytics or marketing tags.

Why this information is used

The application uses this information to create accounts, connect people to a society, show notices, visitors, bills, complaints, households, and services, and to keep an audit trail of selected changes. Contact messages are used to respond to platform questions.

The Digital Personal Data Protection Act, 2023 (Act 22 of 2023) received assent on 11 August 2023. Notification G.S.R. 843(E) dated 13 November 2025 brings it into force in stages. On 18 November 2026, the provisions in force are those that started on publication and the one-year group (section 6(9) and section 27(1)(d), concerning consent managers). The operative duties are in the eighteen-month group, which is 13 May 2027. The Digital Personal Data Protection Rules, 2025 follow the same stages. HomelyBlock is not a consent manager.

Because those operative duties are not yet in force, this policy does not claim that a particular processing ground under section 4 or section 7 is already a legal requirement. The product still limits access by role because that is how the software is built. Counsel should confirm whether the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 continue to apply until section 44(2) of the DPDP Act comes into force.

Who can see records

The API checks the caller on each request. A resident sees the societies where their membership is active, and not another resident’s private household, complaint, or bill. A society administrator sees the society they administer. A platform owner can open the societies the product authorizes. Hiding a button is not the control.

Sharing and processors

The deployment uses an authentication service for sign-in and a database for society records. If the operator configures contact email, the message is sent through that provider. Complaint images stay disabled unless storage is turned on. No advertising network is built in. The operator must name the actual subprocessors before launch. This policy does not invent that list.

Storage, transfers, and retention

Where the database runs, and whether a copy leaves India, depends on the operator’s hosting. There is no self-service button that erases an account or a society’s historical bills. An administrator can suspend or remove a membership. How long visitor logs and bills are kept is an operator decision. This should be reviewed before the erasure and retention duties scheduled for 13 May 2027.

Security

The application verifies sign-in tokens, checks roles on the server, isolates society queries, rate-limits requests, and writes an audit record for selected administrative changes. These are safeguards, not a promise that information cannot be compromised.

Children

HomelyBlock does not offer accounts for children. An adult may enter a household member who is a child. The product does not collect a date of birth. Section 9 of the DPDP Act is in the group scheduled for 13 May 2027. Until an adviser confirms the approach, operators should not invite children to create their own logins.

Your requests

You can correct your own profile in the application. Membership, bills, and other society records are changed by an authorized administrator. A request to access, correct, or close information can be sent through the contact form. The statutory request process under the DPDP Act is not yet in force. Essential sign-in cookies cannot be switched off without ending the session.

CERT-In and incidents

CERT-In directions of 28 April 2022 under section 70B(6) of the Information Technology Act, 2000 can apply to service providers, intermediaries, data centres, body corporates, and government organisations. If the operator is in that class, the directions include a six-hour incident report, 180-day ICT logs inside India, NIC or NPL time, and a point of contact. A host’s compliance does not replace the operator’s duty. See the security page to report a vulnerability.

Updates

When this text changes, the last-updated date changes with it. Continued use after an update does not replace a consent the law requires the operator to obtain separately.