Security
What the product enforces, and what it does not claim.
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.
Controls in the product
- Sign-in is handled by the configured authentication service. HomelyBlock stores the account profile, not the password.
- API requests require a verified access token. The browser session cookie is not treated as enough for the API.
- Roles are read on the server. Public sign-up cannot create a platform owner, and a user cannot change their own privileged role.
- Society queries are limited to the caller’s active membership, or to platform-owner authority where the API allows it.
- New memberships start as invited and do not authorize access until they are activated.
- Requests are rate-limited. The contact form has a stricter limit.
- Security headers are set on the site and the API. Errors returned to browsers do not include stack traces in production.
- Selected administrative changes are written to an audit log. The log does not store passwords, tokens, or full payment credentials.
- Complaint files are disabled by default. When storage is enabled, downloads still require an authorized request.
What is not in the product
There is no multi-factor step in the application for the platform owner. The sign-in service may offer that separately. There is no security certification to display. Backups, clock synchronisation, and 180-day log retention inside India are operator duties, not switches in this repository.
Report a vulnerability
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.
Send a report through the contact form with the subject “Security report”. Describe the impact and the page or API involved. Do not include a working exploit, other people’s data, or a demand for payment. This is a reporting channel, not a promise of a bounty.
CERT-In
If the operating entity is a service provider, intermediary, data centre, body corporate, or government organisation, the CERT-In directions of 28 April 2022 can require a six-hour report, 180-day ICT logs kept in India, NIC or NPL time, and a designated point of contact. That contact is not configured in the product. Whether this deployment is in scope has to be confirmed once the legal entity is known.