Privacy Policy

This is a working draft describing how Banjao handles personal data. We are committed to protecting your personal data in line with India's Digital Personal Data Protection Act, 2023 (the “DPDP Act”). The final, lawyer-reviewed policy will replace this page; until then, the wording here may change.

What we collect

To run attendance and build a worker's verified work record, we collect:

• Identity & contact: full name, phone number, and a Banjao ID (e.g. BJ-00046) assigned to each worker, plus a worker's primary role.
• Identity verification (KYC): if a worker chooses to complete identity verification, a government ID such as Aadhaar or PAN and its verification status. This is optional and used only to verify identity; the exact scope during the current pilot is being confirmed.
• Attendance proof: for each check-in / check-out, a selfie photo, the device's GPS location and whether it was inside the site's geofenced area, and timestamps.
• Work Stamps: the daily record of a worker's shift, built from those check-in / check-out events, together with the operator's confirmation of it.

Why we use it

We use this data to record attendance with proof, to build a worker's verified work history (their “Work Passport”), to let a worker carry that portable, consent- controlled credential across jobs, and to run day-to-day operations for the facilities and service providers who employ them.

Who can see what

Access is deliberately narrow, and different audiences see different things:

• The public verification page (banjao.in/verify) shows only a small, fixed set of fields — a worker's name, Banjao ID, role, active status, and two honest counts (proven shifts and employer-verified shifts). It never exposes a phone number, selfie, GPS coordinates, or exact site locations, and a worker controls whether their credential is shared publicly.
• Operators (the facility or service provider that employs a worker) see attendance for their own sites as status — for example whether a selfie and GPS were captured and whether a check-in was inside or outside the site area — with timestamps. Operator record views are designed to show these proof flags, not the raw selfie image or exact coordinates.

Service providers we work with

To provide the service we rely on a small number of third-party processors — for example database and file storage (hosted in India), application and website hosting, notifications, and messaging. The complete, current list of processors and their locations is being finalized and will be published in the final policy. (The specific vendors are being confirmed as part of the legal review.)

How we protect it

Selfies and other files are kept in private storage — never behind a public link — and are reached only through short-lived, access-scoped requests. Attendance records are visible only to authorized operators at a worker's own sites, and record list views show proof status rather than raw photos or coordinates. Traffic to the site and apps is served over HTTPS.

Keeping and deleting data

We are still finalizing how long different kinds of data are kept and how deletion requests are handled. This is genuinely nuanced: a worker's verified work history is designed to be an append-only record that employers and the worker themselves rely on to verify past work, so some records may need to be retained or de-identified rather than fully erased. We are not stating a fixed retention period here until that approach is settled and lawyer-reviewed. To ask a question about your data or make a request in the meantime, email support@banjao.in.

Your rights & how to reach us

You can contact us to ask about the personal data we hold about you, to correct it, or to request its deletion — subject to the retention approach above, which is being finalized. To raise a privacy concern, use our Grievance route or email support@banjao.in.

Working draft — under legal review. Last updated: July 2026.