Privacy

Notice version 2026-11-v34, in force from 11 November 2026. Written under India's Digital Personal Data Protection Act, 2023.

Who we are

House Federation is operated by Nextyug Technologies Private Limited, CIN U62013PN2025PTC238635, a company incorporated in India with its place of business in Pune, Maharashtra.

Who decides what happens to the data

For the committee members who sign in we are the data fiduciary. For the residents whose records the committee keeps, the society is the fiduciary and we are its processor: the society decides what to record about its residents, and we hold it on the society’s instruction.

What we collect

About the society. The society or federation name, its registered address, and its registration number where you provide it.

About the committee. The name, mobile number and email of the member setting it up, and of everyone they invite. We ask only for what the product genuinely needs. What they post in the society's forum is kept under their name.

About residents. What the committee records: the member and their unit, contact details, ownership or tenancy, dues, fines levied under the society's rules and whether they were paid or waived, bookings of the society's amenities, complaints and visitors, and the minutes of the society's meetings with who attended them. A member record may name family members, including children, where the committee records them as part of the household.

Billing details. The legal name, GSTIN and address the federation gives for its invoices, and a copy of them on each invoice.

Identity and KYC. Where the committee records them: a member’s PAN and Voter ID. Where the society asks for documents, a copy of each one uploaded as proof, such as identity or address proof, as one PDF, with its name, size, number of pages and when it was sent, and who approved or rejected it, when, and why. Photos are scaled down and joined into a PDF, and what the camera wrote into them is removed. An approved copy is sealed with our certificate, which records who approved it and when. For Aadhaar we accept only the masked e-Aadhaar from UIDAI, which shows the last four digits, never a photo of the card, and of an Aadhaar number we keep only the last four digits. The files are kept in Nextyug Drive, our own service in the same data centre. Each time a committee member opens one, we record who opened it and when.

About elections and resolutions. When the society holds a vote: a roll of its flats, the member it lists for each, and whether each may vote, with the flat’s unpaid dues on the day the roll was locked, because a society’s by-laws usually bar a defaulter. Nominations record the candidate and who proposed and seconded them.

Your vote is secret, at the booth and on the app. We keep two separate things. The first is that your flat voted: the flat, when, whether at the booth or on the app, and a receipt code. When you vote on the app, the election log also records your name and the time, as the booth’s officer records who came in. The committee sees this, so it can count turnout and stop a flat voting twice. The second is what was chosen. That is stored without your flat, your name, your phone or the time you voted, and nothing in House Federation shows, prints or exports it with you. The committee, other members and our staff see only the totals, once voting closes. A cast vote cannot be changed or removed, by you, the committee or us. Your receipt code shows that your flat’s ballot was counted. It does not show what you chose, so nobody can use it to make you prove how you voted. Your choices are never put in a notification, a text message, an email or a log. Voting does not read your location or contacts.

Vote where nobody can see your screen. On the app nobody can check that you are alone, as the booth does. If somebody asks to see your vote, or pressures you, you need not show them. Where your society runs a polling booth you may vote there instead, and you can always tell the election officer or write to [email protected].

About people who sign up. Your name, email address and mobile number, each confirmed with a six-digit code before the account is made, and the federation you name. If you start a new federation, its name and address. If you ask to join one, the societies you tick, so its admin knows where you belong; the admin sees your email and mobile masked and can copy them only by a recorded action.

About people asking to join. When somebody asks to join a society at /join: their name, mobile, the flat they give, whether they own it, rent it or live with the owner or tenant, and whether they want the society's text messages. The society's committee sees it and decides; the decision and who made it are kept with the request. Approving it puts the person on the register.

About visitors at the gate. What the gate records when somebody visits: their name, what kind of visit it is, the flat or office they came to, and when they came in and left. Where the guard asks: a mobile number, a vehicle number, how many people came, and which ID was shown with only its last four digits. The whole ID number is never recorded.

About daily help. When a flat adds a maid, cook, driver or other helper: their name, what they do, a mobile number if given, which ID they showed with only its last four digits, the flats they work at, the days and hours each flat expects them, the times the gate let them in and out, and one photo of them if a flat or the guard took one, after asking them. The photo is kept in Nextyug Drive and shown only to the guards and to the flats the helper works at, so the guard can recognise them; it is never used for face matching, and it is deleted when the last flat removes the helper. The society keeps a helper when one flat removes them, because another flat may still use them. A helper is a data principal too, and can ask the society office, or write to [email protected], to see, correct or erase what is held about them.

Parcels, vehicles and gate safety. Parcels the gate keeps for a flat, with the code that releases them; vehicles a flat lists, with the parking slot and sticker; names a flat always lets in; people or vehicles the Security Head has blocked, with the reason; the guard on each shift; patrol rounds, by which guard and when, with no location read from the phone; and incidents a guard writes down, with a photo where one was taken.

Signing in from the app. A resident signs in to the House Federation app with the mobile number the committee recorded for them. We keep that number on their user, the codes we text to it (only a scrambled copy, for thirty days), and for each phone they sign in on a random identifier the app makes for itself, the sessions that phone holds, and, once they allow notifications, the push address that reaches it, with the phone's platform and app version. We also keep which kinds of notification, and which single notifications, you switched off in the app's settings, and which notifications you have opened. If you choose a photo of yourself in the app, we keep it in Nextyug Drive and show it beside your name in the app; you can remove it at any time, and removing it deletes the file. The app's colours and theme stay on your phone and are not sent to us. The app does not read the phone's contacts, location or advertising identifier.

Family on the app. Where the society allows it, the owner or tenant of a flat may add an adult family member with their name, relationship, date of birth and mobile number. That number lets them sign in to the app for the flat to answer the gate, read notices and see bills, from the day they were added. They cannot pay or vote. Removing them, or the flat's member moving out, ends their sign-in.

Moving out, selling and renting. When a person leaves a flat we keep the date, the reason they give, and the handover note; only the committee sees the reason. When a flat is sold we keep the buyer's name, mobile number and email, the date it changes hands and the share certificate number, and the buyer becomes a member on that date. For a tenant we keep the agreement's start and end dates, the date of police verification (never the report) and whether the owner lets the tenant pay the flat's bills. Moving out ends the person's sign-in and roles on the day; their record is kept, not erased.

Chats. What people who sign in to the society write to one another in the product: the message, who wrote it, when, and how far each person has read. A message can be taken back by the person who wrote it, which empties it for everybody.

About the society's suppliers. When the committee keeps a supplier it buys from: the supplier's name and legal name, the contact person, a phone number and an email, the GSTIN, PAN and Udyam number where it has them, its address, the bank account it is paid into, and copies of documents such as its GST certificate, PAN card or a cancelled cheque. The account number is kept sealed, and outside the edit form only its last four digits are shown. Lists show the phone and email masked; copying either is a recorded action, and so is opening a document. A supplier who is a person, such as a plumber, is a data principal under the Act like anybody else.

What we deliberately do not collect

No advertising, no tracking. We use no analytics service. Our own server logs show which pages are used and, when you are signed in, your account id, so that we can fix faults and improve the product; they set no cookies. We do not use Google Analytics, advertising pixels or any advertising-related tracker. We do not sell your data, we do not show advertising, and we do not share member information with marketing partners.

Not for training. We do not use your society’s data to train AI models.

Not the maintenance money. Each society connects its own Razorpay account and collections settle directly to that society. Maintenance money never belongs to us and never passes through our hands.

Why we collect it, and on what basis

Running the society. To keep the register, raise and receipt dues, log complaints and visitors, and let the committee see what happened. These are legitimate uses under the Act, because without them there is no product.

Dues that are late. Where the society's general body has set a rate, simple interest is worked out each night on a member's unpaid bills from the due date, and shows as its own line on the next bill and on the flat's statement. A member who owes for three months or more can be sent a notice of what is owed. The Treasurer can give the society's accountant a copy of the ledger, with each member's name, flat, bills and receipts, and every copy taken is recorded. These are legitimate uses: the society recovers its dues and keeps accounts under its bye-laws.

Reaching residents. To send a notice, a reminder or a gate alert to the person it concerns, through the channels the society has set up. A member who turns a channel off gets only receipts for their own money on it. We keep a record of each message: whom it went to, when, and whether it was delivered.

Buying for the society. To keep the society's list of suppliers, check their tax registrations, and pay them. This is a legitimate use: the society cannot buy or pay without it. How long supplier records are kept is [YOUR POLICY - years to keep purchase records].

Where a purpose rests on your consent rather than on running the service you asked for, you may withdraw it at any time, and withdrawing is no harder than giving it was. Withdrawing consent does not undo what was lawfully done before.

Who else sees it

Amazon Web Services. Sends the six-digit sign-in code when you ask for one by email, through Amazon Simple Email Service in its Mumbai region. It receives your email address and that one message.

Expo, Apple and Google. Deliver the app's notifications to a resident's phone: Expo passes each one to Apple for an iPhone or Google for an Android phone. They receive the phone's push address and the notification's title and one line, never the record behind it.

MSG91. Sends the six-digit code by text message when you sign up, and when a resident signs in to the app. It receives the mobile number and that one message.

Google. Only if you choose Continue with Google. Google tells us your name and confirmed email address, and that you signed in; it learns that you used this service.

Ola Maps. Finds an address on the map when a committee member types one for the society or a member. Our server asks Ola Maps, an Indian mapping service, with the words typed into the search box or the point dropped on the map. It does not receive who is asking or whose address it is.

Razorpay. Takes payments. The society connects its own account, so collections settle to the society and card details never reach our servers. A federation pays our plan through Razorpay too, on our account; we keep its payment reference and issue the GST invoice ourselves.

Meta / WhatsApp. Only where the society connected a WhatsApp number. Meta receives what is needed to deliver the message.

Nextyug Relay, Drive, Report and Agent. Our own products, run in the same place, and every society has them. Relay and the others read each adult member's name, phone, email, wing and flat from this database when they need them, and keep no copy. A member under 18 is never shared.

Nobody else receives your data. We do not sell it, we do not build advertising profiles from it, and we do not train anything on it.

Whether it leaves India

The application and its database run in our own data centre in Pune, India. WhatsApp messages are delivered through Meta, which operates outside India, so a message a society sends that way leaves the country as part of being delivered. The app's notifications are delivered through Expo, Apple and Google, which also operate outside India, so a notification's title and line leave the country the same way. We will confirm the backup retention window for your society in writing on request.

How long we keep it

While the society is with us. Records are kept for as long as the society keeps them, because they are the society’s register rather than ours to expire.

A frozen plan. When a plan lapses the federation freezes and nothing is deleted. Its data is kept until the customer asks us to erase it.

Unfinished sign-ups. A sign-up you start and do not finish, with the codes sent for it, is deleted a day after it runs out, which is an hour after you last used it.

Sign-in codes and app sessions. A code texted to sign in is deleted thirty days after it was sent. A session in the app lasts ninety days from the last time it was used, ends at once when you sign out, and is deleted thirty days after it ends. A phone you stop using for notifications is forgotten thirty days later.

The gate log. Visitor entries, helper visits, collected parcels, patrol rounds and incidents, with their photos, are erased 180 days after the day they happened, unless the society sets a shorter or longer time between 30 days and a year. They are deleted for real each night, not hidden. Helpers, vehicles and blocks stay while the society uses them and go when they are removed.

SOS alerts. An SOS is erased ten minutes after it is closed, with the notification that told the guard and the committee about it. An SOS that is still open is kept until someone closes it.

Uploaded documents. A document waiting for approval or rejected is deleted from storage when a new copy is uploaded in its place; the record that it was sent stays with the member. An approved document is kept with the member’s record. When a member is deleted, the record of their documents goes with them, but the files themselves are not yet removed from storage at the same time; we delete them on request until that is automatic.

Invoices and transactions. Kept for as long as Indian tax law requires, and then deleted.

Chats. [YOUR POLICY — how long a chat is kept after its last message.]

Backups. Deleted data may persist in encrypted backups until they age out on their own cycle. Nothing is restored from a backup without re-applying the deletion.

What deletion actually removes

Your own user. If you are one of several committee members, deleting your user removes your personal data. The society’s own records stay, because they belong to the society and not to you.

The whole society. Everything recorded for it goes. Ask by email from the address registered on the account, with the subject Data Deletion Request.

We verify before acting. To stop anyone deleting a society out of spite, we verify who is asking before we act. We will never ask for your password, a government ID or card details as part of that.

A fraud-prevention hash stays. A non-reversible hash of the email address is kept briefly, so a closed account cannot be used to abuse sign-up. A hash cannot be turned back into an address.

What Meta already has. We delete the access token, the number configuration and the message log held in our system. Messages already delivered to a resident’s phone are on their device and on Meta’s servers under Meta’s retention policy, and we cannot remove those. To cut our access at Meta’s end, remove the app in your Facebook settings under Apps and Websites.

Your rights

Under the Digital Personal Data Protection Act, 2023 you can ask for a copy of the personal data we hold about you, ask us to correct or complete it, ask us to erase it, and nominate another person to exercise these rights on your behalf if you die or become unable to.

Write to [email protected], marked for the attention of the Grievance Officer. We answer within 30 days, and never later than the 90 the Act allows.

If we do not answer, or the answer does not satisfy you, you may complain to the Data Protection Board of India. Nothing here removes that right or requires you to come to us first.

Children

A member record may name children where the committee records them as part of a household. That information is entered by committee members, not by children, and the society is the entity deciding what to record about its residents. We do not knowingly collect personal information directly from a child, we do not profile or track children, and we show nobody advertising. A person under eighteen is never given a sign-in: a family member's phone number is accepted only with a date of birth eighteen or more years ago. Where the Act requires verifiable guardian consent for a child’s data, the society holds it.

If something goes wrong

If we become aware of a breach affecting you we will tell you, and the Data Protection Board, without delay, and follow with a full report within 72 hours.

Changes to this notice

This notice is versioned, and the version in force is shown at the top. A material change is announced 30 days before it takes effect, and earlier versions are available on request.

Contact

Grievance Officer, Nextyug Technologies Private Limited, Pune, Maharashtra, India. [email protected].