Privacy Policy
NLAD · Last updated 8 October 2026
NLAD keeps a building’s maintenance record: what equipment there is, when it was serviced, by whom, and what it cost. This page says exactly what that involves for the people whose details end up in it.
The short version. We hold as little as the product can work with. There are no customer accounts and no passwords. We never sell anything to anyone, and we run no advertising.
1. There are no accounts, one email address and one mobile number
This is unusual enough to state first. A register is opened by scanning its own QR tag and entering the register's 6-digit PIN (the first time, the one printed on the admin card). There is no sign-up, no username and no password.
We do hold one management email address per register, given when it is set up, and we ask you to confirm it. If the PIN and the backup code are both lost, a reset code goes there, or by SMS to the register's verified mobile number, if you choose SMS and type that number. Without a confirmed email or mobile, the only way back is a person at NLAD verifying your management by hand, which takes at least seven days. We also use it for the other codes that protect the register (confirming the address, approving a change of mobile number), for security alerts (a changed PIN, wrong PINs tried, a new backup code), and for reminders when a machine's service is overdue. Your register shows a renewal notice from sixty days before your term ends. If the term ends without renewal, we email this address sixty and eighty-three days later, before the register is deleted. Those two emails carry a copy of your register, and a last one goes on the day it is deleted.
What that address is never used for: marketing, profiling, sale or sharing. It is not shown on any public page. You can change it in Settings whenever the management changes, and deleting the register deletes it, with everything section 8 says goes.
We also hold one management mobile number per register, proved by a code sent to it or by a WhatsApp message from it. It is used for the codes that protect the register — setting it up, changing the number, resetting a lost PIN, confirming a changed PIN — and for service reminders by SMS, at most one a day and eight a month per register. It is never shown on any public page, never sold or shared, and never used for marketing. The SMS are carried by MSG91 under India's rules for business SMS, and we keep only a masked form of the number in our own log.
2. What we hold
About the organisation: the name your management typed, the type (society, RWA, school and so on), the town and state, and the one management mobile number in section 1, which activation requires. The state decides which paperwork your register talks about; the number is how we know whose register a kit belongs to, since kits ship in bulk and nothing else links a serial to a buyer.
About the equipment: what each tag is on, where it is, make and model, licence and certificate numbers and their expiry dates, and the service schedule.
About the work: the date, what was done, the technician’s name and company if they gave one, the amount if there was a bill, and any photographs attached.
About money: what was spent, on what, who paid, and receipt images. These are never public.
Optionally, a person: the name and role of whoever keeps the register. It appears on your public tag pages only if the management ticks the box that says so, and it can be removed at any time.
From residents: if someone reports a problem from a tag, their name and phone number, both optional.
From anyone who uses our help form: their phone number, the organisation’s name, an order number and what they wrote.
From technicians: their mobile number, only if they tick the box to save it, and their phone’s location when they send it or when the management asks for it.
Contact numbers the management publishes (emergency, servicing firm, caretaker), which appear on the tag pages. The building’s location on a map, if the management sets one.
For security and delivery: a scrambled form of the internet address a request came from, used to stop floods; and, if you turn on notifications, the address your phone’s browser gives us to deliver them.
3. What is public, and what is not
Anyone who scans an equipment tag sees a page for that item: what it is, where it is, when it was last serviced, when the next service is due, and the approved service history. That is the point of the product — a resident or an inspector standing in front of a lift can see its record without asking anybody. Contact numbers the management chooses to publish are shown on that page.
Never on that page: your PIN, your backup code, any money entry, any receipt or evidence photograph, the management mobile number, or the name of the keeper of the register unless it was deliberately published.
4. Photographs
Evidence photographs and receipts are stored privately. They are visible only to whoever holds the admin PIN, through links that expire after an hour.
When you or a technician tap “read this photo”, that one image is sent to Anthropic in the United States to be turned into draft form fields. This happens only when someone presses that button — never in the background, and never to a photograph nobody asked us to read. The image is used for that request and is not kept for training. Everything it fills in is a draft a human must check and the management must approve before it enters the register. If you would rather no photo or document left India, do not use the reading buttons; every field can be typed.
5. Where it is stored
Your register is stored in Mumbai, India, on Supabase’s servers in India.
Some of the work happens outside India. The website is served by Netlify, and its server runs in Singapore. Emails we send go through Resend. A photo or document you ask us to read, and the figures used to write an AGM paragraph, go to Anthropic in the United States. A map search goes to OpenStreetMap. Our encrypted backups are held by GitHub and by Backblaze in Europe. We have named everything that leaves India here.
The backup copies are held outside India, and are encrypted before they leave. A copy is taken every night so that a failure at our database provider cannot end a building’s record: the photographs go to a private storage account in Europe, the written records to GitHub, and once a week a full copy of the database goes to the same European storage. All of it is encrypted here first, with keys that stay with us. Neither company can read what it holds for us — what crosses the border is an unreadable block, not somebody’s lift licence. They are kept away from the live system on purpose, because a backup in the same place as the thing it protects is not a backup. Copies of your written records expire after 30 days.
6. Your PIN, and what we cannot see
Your PIN and backup code are stored only in a scrambled form that cannot be turned back. Nobody at NLAD can read them, we will never ask you for them, and we cannot look one up for you. If both are lost, Forgot PIN sends a code to the register's confirmed email or verified mobile; only a register with neither a confirmed email nor a verified mobile has to wait for the seven-day public notice described in the terms, section 7.
Three wrong PINs lock that admin page for twelve hours (five on a register with neither a confirmed email nor a verified mobile), and later locks last longer. Someone from your management who has the right PIN still gets in from their own phone during a lock. Public tag pages are unaffected and keep working.
7. Who else sees any of this
Nobody, other than the service providers that make the product run: Supabase (database and file storage, Mumbai), Netlify (serving the website, servers in Singapore), Anthropic (only the photographs and documents you ask to have read, and the figures for an AGM paragraph you ask for), Resend (which carries the email we send to your one address), MSG91 (which carries the SMS we send to your mobile number), Backblaze and GitHub (which hold the encrypted backups and can read neither), OpenStreetMap (only when you search for or pin your building on a map), WhatsApp (only when you choose to message us there), the company that makes your phone’s browser (it delivers notifications you turn on, which carry no content), Amazon, if you bought your kit there, and Razorpay if and when you pay us — we never see your card number.
We do not sell data, we do not share it with advertisers, and there is no analytics or tracking on the pages a resident scans.
8. How long we keep it
While the register exists, and no longer, except for what the last paragraph of this section names. A register whose term ends without renewal becomes read-only for at least ninety days and is then deleted, after reminders at sixty and eighty-three days to the confirmed management email; the terms, section 3, have the whole of it. While the register exists, no entry is ever silently deleted — an entry can be voided with a reason and stays visible, struck through, because a maintenance record that can be quietly edited is not a record.
You can export everything at any time from Reports, as a CSV and as a printable audit pack. If you want a register deleted, delete it from Settings, or write to support@nlad.in and we will confirm what is removed and when. Closing a register (terms, section 12) stops new entries but deletes nothing.
The off-site copies go too, and nobody has to remember to remove them. When a register is deleted, by you or after a lapse, its photographs and documents are removed from the live system that day. They stay in the encrypted European backup a little longer, because a backup that forgets the moment you do is no protection against a deletion made by mistake — and then they are deleted automatically, on the first nightly run after they have been gone from the live system for thirty days. Copies of your written records expire on the same thirty-day schedule. After that nothing of the register is left anywhere, ours or anyone else’s, except what the next paragraph names.
When a register is deleted, we keep only these: the messages sent to our support desk, kept for 24 months so that we can answer them and keep our own records; and a short security log of the codes we sent to the management mobile, with the number they went to. Everything else goes as described above.
9. Your rights and who to contact
This section is for anyone whose details are in a register, not only the management. A technician whose name is on a service record and a resident who reported a broken lift and left a number are both in here, and neither of them signed up for anything.
You may ask what we hold about you or about your organisation, ask us to correct anything that is wrong, ask for an export, and ask us to delete it. Write to support@nlad.in. That address is the one a person with a complaint should use, and it reaches a person rather than a queue.
We answer within 30 days. That is the same promise we make for any written complaint, and we would rather be held to it than to the outside limit the rules set, which is ninety days. If we are going to need longer on something — an export from a backup, say — we will say so inside the 30 rather than at the end of them.
Grievance contact: Mynampati Latha, proprietor, support@nlad.in. You may withdraw consent at any time by writing to us. We will then stop using your details and delete them, except what the law requires us to keep. If you are not satisfied with our answer, you may complain to the Data Protection Board of India.
We identify the management by a request written from the confirmed management email on that register. Where that is not possible, we use the same evidence as an assisted PIN reset — letterhead, registration number, a resolution from the management, and a photograph of a tag in place. We will never ask for your PIN or backup code. An individual asking about their own name or number in somebody’s register we identify from the entry itself, and we do not ask a resident to prove anything to the management to reach us.
If there is a breach. If personal data held here is exposed, we tell the people affected without delay, in plain words: what happened, what of theirs was in it, what we have done, and what they can do. We tell the Data Protection Board of India as well, first straight away and then in fuller detail. We have written the steps down in advance, with the wording of the notice, so that on the day nobody is drafting a legal document and deciding who to ring at the same time.
10. Children
This is a tool for building management teams and their contractors. It is not directed at children and we do not knowingly collect anything about them.
11. Changes
If this policy changes we will update the date at the top. If a change materially affects what we hold or where it is stored, we will say so on the register itself, where the management will actually see it.
Who you are dealing with
- Trade name
- NLAD
- Legal name
- Mynampati Latha
- Entity
- Sole proprietorship
- GSTIN
- 27ICOPM1622L1Z4
- Address
- Devraee, Floor 6, Gat No. 285 P & 286, Jadhav Wadi Road, Near Silver Fitness Club, Chikhali, Pimpri Chinchwad, Pune, Maharashtra 411062
- support@nlad.in