Privacy policy
Who this covers
gatecheck.in records who crosses the gate of a private house. Four groups of people appear in it, and only the first is our paying customer:
- Household members: the owner and family who approve entries.
- Gate staff: the watchman who records arrivals and departures.
- Domestic staff: maids, drivers, cooks and similar, saved by the household.
- Visitors and couriers: anyone else who arrives at the gate.
The household is responsible for its own gate records. We operate the software on its behalf.
What is collected
Described by category rather than by field, so it stays accurate as the product changes. Anything listed as an example is illustrative; the purpose column is the limit — data is collected for the purposes below and not for others.
| Person | What may be collected | Purpose, which is the limit |
|---|---|---|
| Household member | Account and contact details, the houses you belong to, your vehicles, and a record of the decisions you make | To run your account, let you approve entries, and show who decided what |
| Gate staff | Name, mobile number, the device they are signed in on, and every gate action with its time | So the record shows who admitted whom, which is the point of the product |
| Domestic staff | Name, mobile number, a schedule label, a photograph enrolled by the household, and entry and exit times | So the gate recognises them by sight and waves them in without asking the household each time |
| Visitor | A name, either typed by the guard or spoken into a short voice note, together with details the visitor chooses to give, such as a mobile number, the purpose of the visit or a vehicle number, and the entry and exit times. Visitors are not photographed | To ask the household for a decision and to record the crossing |
| Courier | One photograph taken at the gate, and the time | So the household has a record that a delivery happened. No name, no mobile number and no delivery company is recorded |
A visitor is not photographed.The app is built for a watchman who may not be able to read, so rather than making him type, he can hold a microphone and say the visitor's name; that short recording, or a typed name, is what the household sees when it decides. A household member enrols a photograph of their own domestic staff so the gate can recognise them by sight, and a delivery is recorded by one photograph — a courier has no name to give and none is asked for. Whatever is captured is shown to a household member and nothing else: there is no facial recognition, no face matching, no face database, no fingerprints, and no video or CCTV anywhere in the product.
These are commitments about the product, not descriptions of a setting, and they hold however the rest of this policy changes:
- Nothing here is sold, rented, or shared for anyone else's advertising or profiling, and none of it is used to train a machine-learning model.
- No facial recognition, face matching, face database, fingerprints, iris or any other biometric identification. A photograph is shown to a person and compared by that person, never by a machine.
- No video, no CCTV, no continuous recording, and no location tracking of anyone.
- Nobody outside your household sees your household's activity. Platform staff can see counts and health, never who visited whom — enforced in the database, not by policy alone.
- Data is disclosed to an authority only where the law actually requires it, and never to a neighbour, an association, an employer, or another household.
How long it is kept
- Photographs and spoken notes: deleted 30 days after the visit they belong to by default. A household can shorten that; it can also lengthen it, and never beyond one year.
- Visitors and couriers: identifiable for 90 days after their most recent visit by default, and never longer than the period the household has set, which it will tell you on request. After that the name and phone number are replaced with a non-reversible label. The entry and exit times survive, so the household keeps a verifiable record of the crossing without keeping the person identifiable.
- Domestic staff: kept while the household has them enabled. Their enrolled photograph is deleted as soon as they are removed — at once, not on a timer — unless the same person is also enrolled by another household, whose copy is theirs and is unaffected. Everything else about them follows the 90-day rule once they are removed or paused.
- Household members and gate staff: kept while the account exists.
- Deleted households: purged 7 days after the owner requests deletion. The 7 days exist so a mistaken request can be undone.
Who can see what
- The household sees its own gate activity and nothing from any other house.
- The gate staff membersees today’s activity and whoever is currently on site. He cannot see the household’s older visitor history and cannot see household phone numbers. This is enforced by the database, not only by the app.
- We can see accounts, billing and aggregate counts. Visitor identities, resident details, phone numbers and per-household activity are not accessible to us through the platform console.
Your rights
You may ask for access to your personal data, correction of it, or its erasure, whether or not you are our customer. If you were recorded at a gate and want your details removed, write to us with the house and the approximate date and we will action it, or route it to the household that holds the record where it is theirs to decide.
A household owner can erase an entire house and everything in it from the account screen in the resident app.
Where it is stored
Data is held in Supabase (PostgreSQL) in the Mumbai region and served through Vercel in the Mumbai region. Notifications are delivered via Expo’s push service, which receives a device token and the notification text (a visitor name and the fact that someone is at the gate), but not the wider record.
Contact
Questions, corrections and erasure requests: sashwatsjain@gmail.com.
This policy describes the software as it is built today. It is not legal advice, and a household operating a gate register has its own obligations for that register.