Privacy Policy

This policy was substantially revised on 13 September 2026. Since the first version of 21 June 2026, three things have changed. First, Garood is now operated by a company, Vishwantara Innovation Pvt Ltd, rather than by an individual, and this policy names that company throughout.

Second, the product has gained features that handle personal data in new ways: you can delete your own account and download a copy of your data from your profile; a society can export its record, take a copy of its files, and close its account; deletions complete automatically after a 30-day grace period; photographs can be attached to maintenance requests, including from a page that needs no account; and the app records which version of these terms each person accepted.

Third, we have corrected statements in the earlier version that were no longer accurate: the app uses Vercel's analytics and performance tools (it did not when the first version was written), and those tools now receive a page address with its query string and fragment removed and any identifier replaced by a placeholder; the app no longer loads fonts from Google; and the earlier description of what is kept after a person leaves has been replaced with what the system actually does.

1. About this policy and who we are

Garood ("Garood", "we", "us") is a facilities-management software platform used by residential societies and their staff, committee members, vendors, and residents to manage assets, maintenance, breakdowns, preventive maintenance, readings, inventory, and related records.

Garood is operated by Vishwantara Innovation Pvt Ltd (CIN U62011TS2024PTC185361, registered office at Rajapushpa The Retreat, Gandipet Main Road, Hyderabad - 500075), a company incorporated in India (the "Company"). Garood is a product of the Company. Where this policy says "Garood" or "we", it means the Company acting through the Garood product.

This policy explains what personal data Garood handles, why, how it is stored, how long it is kept, and the rights available to you under India's Digital Personal Data Protection Act, 2023 (DPDP Act) and the Digital Personal Data Protection Rules, 2025 (DPDP Rules). It covers two surfaces: the public website at garood.com and the invitation-only app at app.garood.com, including the pages of the app that can be reached without an account (Section 4).

Using Garood is acceptance. Signing in, or using the report page or the resident information board without an account, means you accept the Terms and Conditions and this policy. If you do not accept them, do not use Garood.

What Garood is. Garood is a record-keeping and workflow tool. It is not a maintenance provider, a contractor or an inspector; it does not monitor equipment, and it does not detect, warn about or escalate the condition of any asset; it does not recommend, vet or guarantee any vendor; and it makes no statement about the condition, safety or fitness of any equipment.

A record in Garood is what a person entered: its presence is not proof that work was done, and its absence is not proof that nothing happened. The notifications, dashboards and reports it shows organise a society's own work; they are not a warning system. The Terms and Conditions say this in full (their Section 4). It matters here because the personal data described below exists to keep those records, not to assess anyone.

Contact / Grievance point: Kapil B Vishnubhatla, Director, Vishwantara Innovation Pvt Ltd, hello@garood.com. You can write to this address with any question, request, or complaint about your personal data.

2. The two roles Garood plays (please read this first)

How your data is handled — and who is primarily responsible for it — depends on which data we are talking about.

(a) Data belonging to a society's operations — the society is in control. When a residential society uses Garood, the society decides what member, staff, vendor, and resident information is entered into the platform and why. For this operational data, the society is the Data Fiduciary (the party that determines the purpose and means of processing), and the Company acts as a Data Processor — we store and process this data on the society's instructions to provide the service.

If you are a resident, committee member, facility manager, security staff member, or a vendor's manager or technician working with a society, your operational data falls in this category. So do the contact details of vendor companies, and the names of workers that society staff write into maintenance records. For requests about this data, you should ordinarily approach your society first; we will also assist as described in Section 8.

(b) Data Garood collects to run its own service — the Company is in control. For information we collect to operate Garood itself — your sign-in account and its security records, the record of which version of our terms you accepted, your deletion request, the technical and usage information described in Section 6, and enquiries sent through our website — the Company is the Data Fiduciary. This policy is the notice for that data, and we are directly responsible for it.

Why this matters: for most resident, staff, and vendor data, the society is the responsible party and Garood follows its instructions. We have written this single policy to be transparent about both roles during the pilot.

3. Who uses Garood, and what data we hold

Garood is invitation-only. There is no open public sign-up. Access is extended by invitation in sequence — a Society Admin is set up first, who then invites Facility Managers and committee / treasurer / auditor / security roles; a society can also invite Vendor Managers and Vendor Technicians for the vendors it works with. Residents are not given accounts and cannot be invited to create one. A resident uses two pages that need no account — the report page and the resident information board — described in Section 4.

The list below is drawn from the structure of Garood's database as it stands on the date of this policy. It is complete as to the kinds of data the system is built to hold.

Your account and profile

Sign-in account (held in our authentication service): your email address; a one-way hash of your password (we never see or store the password itself); the dates you were invited, confirmed your email, and last signed in; and, for each sign-in session, the IP address and browser identifier it was made from. Our authentication service also keeps an authentication event log of account events — such as each sign-in, sign-out, sign-up and password-reset request — with the time and the email address used and, where the service records them, the IP address and browser identifier. This is separate from the audit trail of changes to records described below.
Profile: name, phone number (optional), flat / unit number (optional, where the invitation recorded one), language preference, and three notification-preference switches (email, push, WhatsApp). The switches are preferences only: Garood does not currently send push or WhatsApp messages.
Roles: which role you hold in which society or vendor, who granted it and when, and — if it was later removed — when and by whom. Removing a role does not delete its record; the removal is recorded as a revocation. Role records are deleted when the society they belong to closes its account (Section 7).
Consent record: when you accept an invitation, the date and time, the version of these terms you agreed to, and which screen you accepted from. Nothing else (no IP address or device) is recorded with it.
Deletion request (if you make one): when you asked, when the account becomes due for erasure, whether you cancelled, and when it was erased.

Invitations

When someone is invited, Garood records the invitee's email address; the name, phone number and flat number the inviter typed (all optional except the email); the intended role; who invited them; when the email was sent; and whether and when the invitation was accepted or revoked. Invitation links expire 7 days after they are issued. The page that opens from an invitation link tells whoever holds that link only the role it offers and when it expires.

Contact details of societies and vendors

Society: the society's address, and a primary contact name, email and phone, entered when the society is onboarded.
Vendor companies: a primary contact and an escalation contact (name, email, phone) for each vendor a society works with, and an escalation contact on each maintenance contract. These are entered by the society's administrators, not by the contact person, and each society keeps its own separate vendor record.

Operational records that name people

The working records of the platform carry the user id of the person who created or changed them, from which the app shows that person's current name. Some records also carry names or identifiers typed in as text:

Maintenance tickets and their timelines (comments, status changes, assignments, attachments). A ticket raised from the no-account page carries a label of the form "resident - E101" and a link to the flat chosen from the society's list — no name, phone or email.
Job cards for in-house work: the name of the worker who did the job, the name and role of the person who verified it, and the flat or common area where it was done. These people may not hold Garood accounts.
Preventive-maintenance submissions: optionally, the name of the person who actually performed the work when it was filed on their behalf.
Vendor gate log: a vendor's name as text, a visitor count, and which vendor user (if any) attended.
Service reports, readings, inventory movements, incidents, complaints, root-cause investigations, and shift handovers: who recorded them and when, plus the content.
Free-text fields. Descriptions, notes, comments and complaint text are free text. The system does not read or filter them. Anything a person types there — including another person's name, phone number or other details — is stored as typed and is visible to everyone in that society who can see the record. Please do not enter personal details that are not needed for the work.

Photographs and documents

Breakdown, ticket and preventive-maintenance photographs (up to 3 per submission, 5 MB each; JPEG, PNG or WebP), attached by staff and vendors, or by a resident from the no-account page.
Asset photographs of equipment, uploaded by a society administrator.
Contract PDFs for maintenance contracts and their amendments, and generated QR-label PDFs.
Photographs are meant to show equipment and its condition. The system cannot prevent a person appearing in one. Please avoid photographing people.
Location and camera metadata are removed from every photograph before it is stored — on every upload path, including the no-account page, where the removal is done on our server rather than in the browser. Since 30 September 2026 this includes any second image or short video that some phones add to the same file; a photograph stored before then may still carry one (Section 10). A photograph attached to a maintenance report can be seen by the society's administrators, committee members, treasurer, auditor and facility managers; by the vendor company assigned to that work; by a vendor company whose maintenance contract with the society covers that equipment, which can go on seeing it for the equipment's case history, including after declining the work; and by our operator — not by other residents. A vendor company whose contract does not cover that equipment loses sight of the report and its photographs if it declines the work. It is kept with the society's record and deleted when the society closes its account (Section 7).

Audit trail

For accountability, Garood records who changed what, and when, on 70 of the platform's 91 database tables. Each entry carries the acting user's id and role, a timestamp, and a copy of the record before and after the change. Because the copy is of the whole record, an audit entry about a profile or an invitation contains the personal fields of that record. Section 7 explains what happens to these entries when a person or a society leaves.

Technical and usage information

Web hosting logs at our hosting providers, which include IP addresses (Section 6).
Usage analytics and performance measurement in the app, provided by Vercel: a redacted page address — the query string and everything after a "#" are removed, and any identifier in the path (a record id or a link token) is replaced by the placeholder "[id]", so Vercel sees, for example, "/board/[id]" rather than the link itself — together with the page you came from, your device type, operating system and browser, an approximate location derived from your IP address (country, region and city), and page-load timings. The redaction happens in your browser before anything is sent. No cookies are set for this, and Vercel states that it does not store IP addresses or identify individual visitors (Section 6).
Bot-protection signals when you sign in, create or reset a password, submit a no-account report, or send the early-access form on our website: your IP address, browser identifier and a connection fingerprint, sent to Cloudflare Turnstile (Section 6).
Browser storage: the app keeps your sign-in session in your browser's local storage so that you stay signed in. It sets no advertising or tracking cookies.

What Garood does not collect

Garood has no fields for, and does not ask for: profile photographs, government identity numbers or KYC documents, vehicle details, financial or payment data, health data, biometric data, date of birth or age, or device location. Fields for profile photographs, vehicle plates and signatures that existed in early versions of the database were never used and were removed in August and September 2026. As noted above, free-text fields and photographs are the two places where the system's structure would allow such information to be entered; we ask you not to, and we treat any such entry as data belonging to the society's operations (Section 2(a)).

No payments through Garood (pilot). Garood does not process payments and does not integrate any payment gateway (such as UPI or a card processor). Any pilot fees are handled separately, outside the platform.

4. How we collect your data

By invitation and account creation. Most data is entered when a society sets up roles and invites people, and when invited users create their account and complete their profile. Each user has a Garood-specific login; Garood does not use third-party social logins (such as "Sign in with Google"). Creating an account requires confirming your email address by clicking a link we send you.
From residents, voluntarily and without an account. Residents are not given Garood accounts and are never invited to create one. What a resident chooses to send reaches us through the report page, described in the next item.
From the report page or the resident information board, without an account. Described in full under the heading just below.
From society staff entering records about others. Facility managers and administrators enter vendor contact details, worker names on job cards, gate-log entries and similar records about people who may never use Garood themselves. The society is responsible for the accuracy and lawfulness of those entries (Section 2(a)).
Through the early-access form on our website (garood.com). When you request early access, we collect your name, email address, and city (required), along with an optional phone number, society / community name, and message, so that we can contact you about Garood.
Automatically, as you use the service. The audit trail, sign-in session records, analytics and bot-protection signals described in Section 3 are generated by your use of the app.

If you use Garood without an account

A society can give its residents a link or a QR code to a report page (addresses beginning app.garood.com/report/ and, on equipment stickers, app.garood.com/q/) and to a resident information board (app.garood.com/board/). Neither creates an account or a login, and neither gives you any ongoing access. The Terms and Conditions and this policy are linked at the bottom of both pages; submitting a report, or opening the board, is your acceptance of them for that use.

What a report stores. Measured against the code that handles it, a report holds exactly:

the piece of equipment you chose;
your flat number, chosen from the society's own list of flats and stored as a link to that flat together with a label such as "resident - E101" — a flat that is not on the list cannot be entered;
your description of the problem, up to 2,000 characters of free text — do not put your name or phone number in it unless you want the staff to have them;
the date and time you sent it, a work reference number that is shown to you once, and the fact that it came from the report page;
up to three photographs (JPEG, PNG or WebP, 5 MB each), stored in the society's private storage folder with their original file name (letters, digits, dots and dashes only) and type.

Nothing else is asked for. The page does not collect your name, phone number or email address, sets no cookies, and does not read your location. The human-verification token from Cloudflare Turnstile is checked once and not kept. Our server uses your IP address for a per-minute limit on repeated submissions and does not store it in the report; it does appear in our providers' short-lived logs (Section 7). Analytics receives only the redacted page address (Section 3).

Photographs. Photographs you attach are uploaded to and stored in Garood. Because you have no account, your browser does not upload them directly: the report page sends them to our server-side function (public-request), which removes location and other camera metadata from each file — since 30 September 2026 including any second image or short video that some phones add to it (Section 10) — using the same stripping code the app uses, and only then stores it.

On the date of this policy we confirmed that the function running on our server is the code we describe. Afterwards the photographs can be seen by the society's administrators, committee members, treasurer, auditor and facility managers, by the vendor company assigned to fix the problem, by a vendor company whose maintenance contract covers that equipment (Section 3 explains when), and by our operator. Other residents cannot see them, and you cannot see them yourself once sent. They are kept with the society's maintenance record and deleted, with the rest of the society's files, when the society closes its account; our operator can remove a single photograph earlier on request.

This is not anonymous. A flat number together with a photograph — and often the description — can identify a household even without a name. Everyone listed above can see which flat reported what. We do not describe these reports as anonymous, and you should not assume they are.

The board shows nothing about you. It shows anyone who holds its link the society's equipment status and availability figures, shared-space closures and — whenever the society's staff have recorded the meter readings and the bill — the building's water use and its shared-area electricity use for the last complete month, including the amount of the electricity bill. Opening it collects nothing beyond the technical information in Section 3 and Section 6.

Your rights are the same as anyone else's (Section 8). Because there is nothing to sign in to, exercise them through your society's administrator or facility manager, who can see your report and, while the work on it is still open, correct its description or the equipment it names, or by writing to hello@garood.com with the society and your flat number so that we can find it. The flat number on a report cannot be changed in the app; write to us if it is wrong.

5. Why we use your data (purposes)

We use the data above only to:

Provide the facilities-management service to the society — logging and tracking assets, breakdowns, tickets, preventive maintenance, readings, inventory, and complaints;
Identify who performed an action, for accountability and audit integrity;
Communicate with you about the service — invitation, email-confirmation and password-reset emails. Garood sends no marketing email to app users;
Respond to early-access requests and enquiries you send us through the garood.com website;
Keep the service secure and operate it reliably, including bot protection on sign-in and public pages, and measuring how the app performs;
Carry out deletion and export requests, including the scheduled erasure described in Section 7;
Comply with applicable law.

We do not use your personal data for advertising, and we do not sell it.

6. Where your data is stored, and who else handles it

Garood operates two surfaces: the public marketing website at garood.com and the invitation-only app at app.garood.com. Different providers serve each, as set out below. Every provider listed here was identified from the deployed configuration of the service on the date of this policy.

The Garood app (app.garood.com)

Primary storage. Garood's database, authentication service, file storage and server-side functions are hosted on Supabase, in the South Asia (Mumbai) region (ap-south-1). Supabase runs its managed platform on Amazon Web Services (AWS); the underlying infrastructure for this region is AWS's Mumbai data centres. Requests from the app to Supabase pass through Cloudflare's network, which Supabase uses in front of its services. The database is backed up daily by Supabase; uploaded files are not included in those backups. Supabase's own engineers may be given temporary access to our project when we raise a support ticket; we keep a written log of each such occasion.

Other service providers (sub-processors). To run the app we also use:

Vercel (Vercel Inc.) — hosts the Garood web application. As a web host it processes technical information such as visitors' IP addresses in its server / edge logs. Since 22 June 2026 the app has also used Vercel Web Analytics and Vercel Speed Insights, which receive the redacted page address and the other information listed under "Technical and usage information" in Section 3 — never a query string, a link fragment or a token. Vercel states that these tools set no cookies, identify visitors only by a hash that is discarded after 24 hours, and do not store IP addresses.
Resend — delivers the emails Garood sends: invitations (from a garood.com address), and the email-confirmation and password-reset messages of the authentication service. It processes the recipient address, the email content, and delivery metadata.
Cloudflare Turnstile (Cloudflare, Inc.) — the human-verification check on sign-in, account creation, password reset, and the no-account report page. Cloudflare receives the visitor's IP address, a connection (TLS) fingerprint, the browser's User-Agent, and our site key, and states that it processes these solely to detect bots, as our processor.
GitHub (GitHub, Inc.) — runs the nightly schedule that triggers the deletion job described in Section 7. The schedule sends only a signal and a shared secret to our Supabase project, which does the work. GitHub keeps a log of each run, which lists the internal reference numbers of the accounts and societies that run processed (and, for a trial run started by hand, the names of societies due for deletion) — never a person's name, email address or phone number.

Analytics and monitoring. Other than Vercel Web Analytics and Speed Insights, the app uses no third-party analytics, advertising, session-recording or error-monitoring tools. The app does not load fonts or scripts from Google.

The Garood marketing website (garood.com)

Hostinger — hosts the public marketing website. Like any web host, it processes standard server-log technical data, such as visitors' IP addresses.
Google (Apps Script & Google Sheets). The early-access form on garood.com submits the name, email, and city, along with the optional phone number, society / community name, and message you provide, to a Google Apps Script web app, which stores them in a Google Sheet owned by the Company; a notification email is also sent to us. Google acts as a sub-processor for this data.
Cloudflare Turnstile (Cloudflare, Inc.) — the human-verification check shown on the early-access form, which tells people apart from automated traffic. Cloudflare receives the visitor's IP address, a connection (TLS) fingerprint, the browser's User-Agent, and our site key, and states that it processes these solely to detect bots, as our processor. The verification token it issues travels with your enquiry and is not stored with it.
Google Fonts. The marketing website loads the "Inter" font from Google's servers, so Google may receive visitors' IP addresses when the font loads. The app does not load anything from Google.

Data location and transfers. Garood's core personal data — the database, authentication records and uploaded files — is stored in India (Mumbai). Some of the providers above are operated overseas and may process limited data outside India in the course of providing their services: Vercel (edge logs, analytics and performance data), Resend (email content and delivery metadata), Cloudflare (bot-protection signals, on both the app and the website, and the network path to Supabase), GitHub (the deletion schedule's run logs), and, for the website, Google and Hostinger.

Under the DPDP Act (Section 16), transfer of personal data outside India is permitted except to countries the Central Government restricts by notification. We will update this policy if our providers or arrangements change.

7. How long we keep your data (retention), and how deletion works

We keep personal data only as long as it is needed for the purpose it was collected. What follows describes what the system actually does, including the points where erasure is not yet complete.

While you use Garood

Your profile, roles and records are kept for as long as you hold an active role in a society or vendor. If an administrator removes you, your role is marked revoked and you lose access immediately; your profile and the records you created are kept, because the society's maintenance history still refers to them.

Deleting your own account

You can request deletion of your account from your Profile page at any time. Your access is withdrawn immediately, and a 30-day grace period begins. During those 30 days you can sign in, return to your profile, and cancel the request, which restores exactly the roles that were withdrawn. Signing in does not cancel the request; only the cancel button on your profile does. Garood sends no email about the request, its cancellation or the erasure. You can also download a copy of your data from the same page (Section 8).
If you are the only administrator of a society, or the only platform administrator, the request is refused until someone else holds that role, so that a society is never left without an administrator.
When the grace period ends, an automated job that runs nightly (about 03:15 IST) erases the account. It removes your name, phone number and flat number from your profile; scrubs the same fields from every audit-trail copy of your profile; erases your email address, and the name, phone number and flat number the inviter typed, from every invitation sent to your address and from the audit-trail copies of those invitations; deletes your entries from the authentication event log (Section 3); and disables your sign-in account by replacing your email address and phone number with an irreversible hash, removing your password, and ending every session. The user id is kept so that the society's records remain consistent.
What remains after erasure. Your user id continues to appear on the records you created or changed (tickets, readings, comments, audit entries) together with the role you held at the time and the date, but it no longer resolves to a name: the app shows "Unknown user" instead. Photographs you uploaded stay with the society's records. Your consent record (which version of the terms you accepted, and when) and the record of your deletion request are kept as evidence that the erasure was requested and carried out. If you typed your own name into a free-text field, that text is not changed by the erasure.
A gap we are closing. An invitation sent to someone who never created an account — one that expired or was revoked — keeps that person's email address and the name, phone number and flat number the inviter typed. There is no account to delete, so the account-deletion job never reaches it. Until this is fixed, that person may ask us to remove it by writing to the contact in Section 1, and we will do so.

When a society closes its account

A society administrator can request deletion of the society. Access for everyone in that society is withdrawn immediately, and a 30-day grace period begins, during which the person who requested it can cancel from their profile page.
Before the request is accepted, the administrator must either have downloaded the society's files (Section 8) within the previous 30 days, or confirm on the screen that the files are not wanted.
When the grace period ends, the nightly job deletes every record belonging to the society across all 75 society-scoped tables, including the society's audit trail, and removes every file under the society's storage area. Vendor contact details entered by that society are erased when no other society uses that vendor record. The society's members keep their sign-in accounts and their records in any other society. A record that the deletion took place — the society's name and code, who asked for it, and when — is kept as evidence that it was requested and carried out.

Other retention periods

Invitations expire 7 days after issue. Expired and revoked invitations are currently retained; see the gap noted above.
Vendor company contacts are kept until the last society that entered them leaves Garood, and are then erased from the live record and from audit copies.
Job-card worker and verifier names, and other names typed into operational records, are kept with the society's maintenance history for as long as the society uses Garood. They are not covered by self-service account deletion, because they belong to the society's record rather than to an account. They are removed when the society closes its account.
Reports made without an account, and their photographs, are part of the society's maintenance record. They are kept for as long as the society uses Garood, are not covered by any user's self-service deletion (the reporter has no account), and are deleted, files included, when the society closes its account. Our operator can remove a photograph earlier on request; the report itself stays in the society's record.
Sign-in session records (IP address, browser identifier) end when you sign out or a session expires, and are removed when an account is erased. The authentication event log (Section 3) is kept in our database with no automatic expiry; account erasure deletes the erased account's entries from it. We will set a retention period for it and update this policy when we do.
Database backups are retained by Supabase for its standard rolling period and then overwritten, so erased data can persist in a backup for a short time after erasure.
Platform and hosting logs. Vercel keeps the app's request logs for about one hour. Supabase keeps its platform logs (API, authentication and database logs) for 7 days. Both contain IP addresses and requested page addresses, never the part of an address after "#". Account erasure cannot remove entries from these logs; they expire on those schedules.
Analytics data is aggregated by Vercel; the per-visitor hash it uses is discarded after 24 hours. Vercel keeps the aggregated figures for its reporting window (one month on our current plan) and states that it may retain them for longer.
Early-access enquiries submitted on garood.com are kept in our Google Sheet until we have responded and for a reasonable period afterwards; you may ask us to delete yours at any time.

8. Your rights, and the tools built for them

Under the DPDP Act (Sections 11 to 14), you have the right to:

Access a summary of the personal data we hold about you and how it is processed;
Correct, complete, or update your personal data;
Erase your personal data where it is no longer needed, subject to the records described in Section 7 that are retained for accountability;
Grievance redressal — raise a complaint with us and have it addressed;
Nominate another individual to exercise your rights in the event of death or incapacity.

Self-service tools in the app.

Download a copy of your data. From your Profile page, any signed-in user can download a file (in JSON format) containing their sign-in email, profile fields (including any flat number and the language and notification settings), role history, consent records, deletion requests, tickets reported, ticket activity including comments, readings, preventive-maintenance submissions, job cards they recorded (excluding other people's names on them), complaints, and a list of the audit entries recording their actions (dates and record types only — not the copies of records, which contain other people's data). The file does not include the invitations sent to your address, your sign-in sessions or the authentication event log, your comments and photographs on preventive-maintenance tasks, or copies of the photographs and files you uploaded; you can ask us for these by writing to the contact in Section 1. Operational records that merely carry your user id are not included.
Correct your details. Your name and phone number can be edited on your Profile page. Your flat number and your language and notification settings are not shown there and cannot be changed there; to correct them, write to the contact in Section 1. Corrections to records entered about you by your society (for example, a vendor contact or a job card) should be requested from your society's administrator.
Delete your account. From your Profile page, as described in Section 7.
For societies: a society administrator can download the society's data record as a file, and a separate archive of all its photographs and documents, from the Overview tab of the society's page. The record names every file the society owns; it does not include the society's audit trail, which is deleted with the society. The archive includes a manifest listing any file that could not be included and why. Once a society deletion has been requested, its administrators no longer have access, and during the 30-day grace period only our operator can download either one; ask us at the contact in Section 1.
If you used Garood without an account (the report page or the board), there is nothing to sign in to. Ask your society's administrator or facility manager, who can see your report and correct it, or write to hello@garood.com with the society and your flat number. We will act on or forward the request as described below.

How to exercise them otherwise. If your data relates to a society's operations (Section 2(a)), please raise the request with your society, since the society directs how that data is used. You may also contact us at hello@garood.com and we will act on or forward the request as appropriate. For data where the Company is the Data Fiduciary (Section 2(b)), contact us directly. We will acknowledge your request and respond within 30 days.

Platform administrators. The Company's own operator accounts (the "super admin" role) are managed by the Company. Such an account cannot delete itself while it is the last remaining operator account, so that the platform is never left without one.

9. Children

Garood is intended for adults — society members, staff, and vendors. It is not directed at children, and we do not knowingly collect personal data from anyone under 18. Garood has no field for age or date of birth, and accounts are created only by invitation. Because the system's free-text fields and job cards allow staff to write down any name, a society could enter information about a minor (for example, a child named in a complaint).

We ask societies not to do so, and we will delete such information on request. Where the DPDP Act (Section 9) requires verifiable parental consent for processing a child's data, that obligation falls on the society as Data Fiduciary for its operational records; we will assist on request.

10. Security

These are the specific measures in place on the date of this policy.

Access control in the database itself. Every one of the 91 tables in Garood's database has row-level security enabled, with 206 access policies that limit each user to the societies and vendors they belong to and to what their role permits. Anonymous visitors have no access to any table. The few functions reachable without an account return only the society's name, equipment names and status, flat labels, availability figures, shared-space closures and, whenever the society has recorded the meter readings and the bill, the building's water and shared-area electricity figures including the amount of the electricity bill, for the society named by the link's token — plus, on the invitation page, only the role the invitation offers and when it expires.
Files. All storage buckets are private. Files are read only through links that expire — after one hour for photographs and after five minutes for contract and QR-label PDFs — and the same role rules that apply to a record apply to its files.
Invitation-only access with email confirmation. Access is granted only against an invitation whose email address must match the account's confirmed email; an account without an accepted invitation holds no role and can see nothing. Invitation links expire after 7 days and an invitation can be accepted once.
Bot protection. Cloudflare Turnstile guards sign-in, account creation, password reset, the no-account report page, and the early-access form on our website; the report page's and the early-access form's verifications are both checked server-side rather than in the browser, and the database function the report page calls cannot be reached from a browser at all.
Transport and browser protections. The app is served only over HTTPS with HTTP Strict Transport Security, and with a Content Security Policy that allows the app to load code and data only from itself, Supabase and Cloudflare Turnstile.
Metadata removal. Before a photograph is stored, the parts of the file that carry camera and location details (EXIF and XMP data, and their equivalents in PNG and WebP files) are removed on every upload path, and this is enforced in the code so that a new upload path cannot skip it; the photograph's colour profile is kept. Some phones store a second image or a short video after the photograph in the same file, and it can carry its own camera or location details. Since 30 September 2026 that added part is removed too, and nothing after the end of the photograph is stored; on photographs attached to maintenance reports, tickets and preventive-maintenance tasks before that date, it may still be there. Equipment photographs are re-encoded before they are stored and carry no such addition.
Privileged credentials. The service key that bypasses access rules is held only inside Supabase and is used by six server-side functions; it never ships in the browser and is not held by GitHub or any other provider.
Audit trail and deletion ledger. Changes to 70 tables are logged with the actor, role and time; every deletion request, and every run of the deletion job, is recorded, including runs that found nothing to do. Our authentication service logs sign-ins, sign-outs, password resets and failed attempts (Section 3).
Backups. The production database is on a paid Supabase plan with automated daily backups.

No system is perfectly secure, and we cannot guarantee absolute security.

11. Data breaches

If a personal-data breach occurs, we will act in accordance with the DPDP Act (Section 8(6)) and the DPDP Rules, including notifying the Data Protection Board of India and affected individuals as required and within the timelines the Rules prescribe. Where the Company acts as a Data Processor for a society (Section 2(a)), we will inform and assist the society as the Data Fiduciary.

12. Changes to this policy

We may update this policy as Garood evolves — for example, when new features change what data we handle, or when our providers change. Material changes will be notified to account holders, and the "Last updated" date above will change. The app records the version of this policy that each person accepted, so we can tell who has and has not seen a later version.

13. Contact

Questions, requests, or complaints about this policy or your personal data:
Kapil B Vishnubhatla, Director — Vishwantara Innovation Pvt Ltd — hello@garood.com.
Registered office: Rajapushpa The Retreat, Gandipet Main Road, Hyderabad - 500075. CIN: U62011TS2024PTC185361.