BUILDOJA
Your data, clearly explained

Privacy Notice

This notice explains what personal data BUILDOJA requests through buildoja.com, BUILDOJA App and BUILDOJA Naka, why we need it, and how you can correct or delete it.

Plain-language summary: we use the minimum information needed to operate contractor, labour, booking and support services or respond to a website form. We do not sell personal data. You can request account deletion inside the app or at buildoja.com/delete-account.

1. Who is responsible

BUILDOJA, Pune, Maharashtra, India, is responsible for personal data processed through buildoja.com, BUILDOJA App and BUILDOJA Naka.

Email: info@buildoja.comPhone / WhatsApp: +91 95954 12397

2. Data we request

Project enquiries

Name, phone number, email address, project location, project type and scope, approximate area and budget, requirements, and an optional meeting preference.

Career applications

Name, phone number, email address, city, confirmation that the applicant is at least 18, department and role preference, experience, software skills, portfolio link, optional cover letter, and an optional interview preference.

Contractor and labour accounts

Registered phone number, account and public worker identifiers, name, profile details, preferred language, work category, team or business details, availability, service area, booking and attendance activity, Khata entries, support or booking messages, notification preferences, device and security records, and account-status history.

Identity verification

Where verification is required, we process a profile photo, masked Aadhaar details, the privately stored Aadhaar image supplied for review, review status, reviewer decision and limited audit evidence. The app must not display the full Aadhaar number publicly. Do not upload unrelated documents or share an OTP, password, UPI PIN, or bank/card secret.

For both forms, we also record a submission reference, submission and receipt time, form version, consent-notice version, and the website page from which the form was sent. These fields help us verify delivery, investigate failures and avoid confusing one submission with another.

Technical security logs may contain limited device, browser, timestamp and network information needed to prevent abuse and diagnose failed submissions.

3. Why we use it

4. Your choice and consent

Website forms and identity-upload flows ask for a clear acknowledgement before submission. You can choose not to submit optional information; however, we may then be unable to provide the related enquiry, application, booking or verification service. You can withdraw consent for future processing by contacting us. Withdrawal does not affect processing already lawfully completed or records that must be retained for another valid reason.

5. Service providers and sharing

Netlify hosts this website and runs the same-origin form-delivery function. That function validates a completed submission and forwards the approved fields to a Google Apps Script web app, which verifies a server-only delivery credential and records the submission in the Google Sheet selected and controlled by BUILDOJA. After the record is accepted, Google services process operational acknowledgement emails through a short queue that is checked every minute; delivery normally follows within a few minutes but may be delayed by the provider. A meeting or interview choice remains a preference: the initial submission does not create or confirm a Calendar event or Google Meet. If BUILDOJA later confirms a slot, Google may then process the related calendar information. Netlify and Google may process limited security and request logs. WhatsApp receives information only when you deliberately choose a WhatsApp contact option. We do not sell or rent personal data.

Supabase provides account authentication, database, private file storage and server-side functions used by BUILDOJA App, BUILDOJA Naka and authorised Admin operations. Hosting, app-distribution and security providers may process limited technical logs needed to deliver and protect the service. Access to Aadhaar and profile-review files is restricted to authorised review workflows; these files are not public app assets.

6. Storage and retention

The website does not intentionally keep unfinished form values in browser storage or a cloud draft. Public website files may be cached by the service worker, but submitted personal data is excluded from that cache.

Project enquiries that do not become an active client engagement are scheduled for anonymisation within 24 months of submission. Unsuccessful career applications are scheduled for anonymisation within 12 months of submission. A monthly retention check marks and anonymises eligible Sheet records while excluding active projects, hired applicants and documented legal holds. If an enquiry becomes an active project, or an applicant is hired, the necessary record moves to the applicable contract, accounting or employment schedule. We may keep a record longer where a legal obligation, dispute or documented legal hold requires it, and may delete it earlier after a valid request.

Identity documents remain private while manual review is pending and are not automatically deleted before that decision. After review, the file is scheduled for deletion under the controlled retention workflow unless a documented safety, fraud, dispute or legal hold requires longer restricted retention.

Account data remains while an account is active. A valid deletion request starts a 7-day grace period and immediately restricts new work access. Final deletion waits for active bookings, applications, team handover, workspace ownership transfer and pending identity review to be resolved. Direct personal data is then deleted or permanently de-identified. Minimum booking, payment, tax, fraud-prevention, dispute, safety and audit records may be retained only for the applicable purpose and period, with access restricted and direct identifiers removed where possible.

7. Security

BUILDOJA services are intended to use HTTPS, authenticated server calls, access controls and private storage for identity files. Website form submissions use a rate-limited same-origin delivery function, are validated again on the server, and are excluded from the service-worker cache. Account-deletion finalisation and identity-file removal run only through authorised server-side workflows. No internet service can guarantee absolute security. If you believe your data has been exposed or misused, contact us promptly.

8. Account deletion and privacy requests

Signed-in contractor and labour users can request deletion at Profile → Safety → Delete account and data. A 7-day grace period allows cancellation from the same screen. Users who cannot access the app can start a request at buildoja.com/delete-account or email info@buildoja.com.

Deletion is not the same as a temporary block or logout. After required blockers and review checks are resolved, the workflow deletes or permanently de-identifies the associated personal data and disables the authentication account. A requester may need to complete a secure ownership check. Never send an OTP, password, full Aadhaar, bank/card details or UPI PIN by email.

You may also ask for a summary of your personal data, correction or completion, withdrawal of consent, or a review of a privacy grievance. Where applicable law provides it, you may nominate another person to exercise your rights. We may verify identity before acting.

We will acknowledge a privacy complaint, explain the next steps, and provide any statutory escalation route that is available under applicable law.

9. Children

BUILDOJA contractor, labour, project and career services are intended for adults. Career applicants and account holders must meet the applicable minimum age requirement. We do not knowingly request account or identity-verification data from children.

10. Changes

We may update this notice when our forms, service providers or legal obligations change. Material changes will be reflected on this page with a new update date.

Last updated: 2 September 2026