Terms of use
Draft template, not yet in force. The wording below is a skeleton for the team and its adviser to complete. Every To confirm tag and every dashed box marks a decision nobody has made yet. The page carries noindex and must not go live until those are filled and a qualified adviser has reviewed it. Nothing here is legal advice.
These terms cover using RERA Stack. They are written for the consultant's firm that holds the engagement, not for the builder, and not for the professionals who sign the certificates.
What this page still needs from you
- The legal entity name and registered address behind these terms.
- Fees, billing cycle, what happens on non-payment, and notice period to cancel.
- Any uptime or support-response commitment, if one is being made at all.
- The liability position and any cap. This is the clause that most needs a qualified adviser.
- Governing law and which courts have jurisdiction.
- How much notice you give before changing these terms.
1. Who these terms are between
These terms are between legal entity name (“we”) and the firm that signs up for RERA Stack (“you”). To confirm
2. What RERA Stack does
RERA Stack handles your builders' unit data on the MahaRERA portal from an Excel file: the quarterly Withdrawal Update, with Registration of Units and Project Correction as they ship. It checks every row against the portal, waits for a named person in your firm to approve, and then files unit by unit, keeping a record of every change it makes.
3. What RERA Stack does not do
- It does not prepare or certify Forms 1, 2, 3 or the annual Form 5. Those stay with the architect, engineer and chartered accountant. To confirm — a Form 2 generator exists in the team's codebase, so this sentence must be checked against what is actually being sold.
- It does not give legal, financial or compliance advice, and it is not a substitute for your professional judgement.
- It is not affiliated with, endorsed by, or connected to MahaRERA, and it cannot influence anything MahaRERA decides.
4. Your builders' portal logins
RERA Stack signs in to MahaRERA using the builder's own login, the one you already hold for the engagement. By saving a login you confirm you are authorised to use it for this purpose and that the builder knows.
You are responsible for keeping your own RERA Stack account secure, and for telling us if you think someone else has got into it.
5. Approval, and who is responsible for what
Nothing reaches MahaRERA until a named person in your firm clicks Approve and File. That name and time stay on the run.
Because of that, what gets sent to MahaRERA is your decision. We are responsible for the tool doing what this page says it does. You are responsible for the accuracy of the data you upload and for what you approve.
6. Availability
We aim to keep RERA Stack running, particularly in the week a quarterly update is due. state any uptime or response commitment, or say plainly that none is given To confirm
RERA Stack depends on the MahaRERA portal being up and behaving as it does today. When MahaRERA changes or goes down, we may not be able to file, and we will tell you when that happens.
7. Fees
One fee per firm, set by how many registered projects are active with you this quarter. amounts, billing cycle, what happens if payment is late, notice to cancel To confirm
8. Liability
This clause needs a qualified adviser. It should set out what we are and are not liable for, and any cap on it, consistent with section 5. To confirm
9. Ending the arrangement
You can stop using RERA Stack at any time. notice period, what happens to your data, refunds if any To confirm Your data is dealt with as set out in the privacy page.
10. Changes to these terms
If we change these terms we will put the new date at the top and tell the firms using RERA Stack, giving notice period before the change takes effect. To confirm
11. Governing law
These terms are governed by the laws of India, and the courts at city have jurisdiction. To confirm
12. Contact
Questions go to support@rerastack.com.