☀KBKBकाम भी • कमाई भी
PRIVACY • DATA MINIMISATION

Privacy Notice / गोपनीयता सूचना

What KBKB collects, why it is used, what is optional, and what control you have.

Effective: 11 October 2026This notice covers KBKB discovery, matching, communication, mobile verification and PayU-enabled transaction processing. KBKB is operated by Koochbhi Private Limited. The same formally approved Koochbhi Private Limited Data Fiduciary / grievance, registered-address and customer-service details apply to KBKB and must be inserted by IT from the current compliance records.

1. Data we may process

हिंदी: KBKB केवल matching, communication, safety और platform operation के लिए जरूरी जानकारी लेने का उद्देश्य रखता है.

2. Why we use it

To understand intent, rank nearby matches, let peers communicate, remember your selected language and context, verify mobile control, create and reconcile PayU transactions and payouts when enabled, prevent abuse, investigate reports, maintain service reliability, comply with law, and improve the user journey. KBKB should not use precise location for unrelated advertising or publicly expose exact coordinates on match cards.

3. Location

Location permission is optional for the current service. If you allow precise location or provide a DIGIPIN/location code, it may be used to calculate distance and nearby relevance. Public cards should display only an appropriate area-level location, not raw coordinates or exact private location.

4. Sharing

Information may be shown to or shared with another user when needed for discovery, matching or connection; with service providers acting on KBKB’s instructions; with PayU, banks/UPI/payment and payout providers where needed to process or reconcile an enabled transaction; with SMS/OTP delivery providers where needed to verify a mobile number; where required by law; or where necessary to protect users, rights, safety or platform integrity. KBKB should disclose only what is reasonably needed for the purpose.

5. External opportunity sources

If KBKB surfaces India-wide external opportunities from documented APIs, approved partners or public government datasets, those items must remain labelled separately from KBKB-native postings. Clicking or applying through an external source may subject you to that source’s privacy terms.

6. Retention

KBKB should retain personal data only for as long as reasonably necessary for the purpose collected, active user needs, fraud/safety records, legal obligations, dispute handling and legitimate platform operations. Retention periods should be reduced where data is no longer needed.

7. Your choices and rights

Subject to applicable law and the feature being available, you may ask to access, correct, update or erase personal data, withdraw consent where processing is based on consent, or raise a grievance. Withdrawing optional location permission does not by itself prevent use of KBKB; you can enter an area manually.

8. Children and vulnerable users

KBKB is not intended to facilitate unlawful child labour, child exploitation or unsafe arrangements involving minors. Age and consent requirements for any work must comply with applicable Indian law. Where special handling is legally required for a child’s personal data, KBKB must follow that requirement before processing it.

9. Security

KBKB should use reasonable technical and organisational safeguards appropriate to the data and service. No online system can promise absolute security. Users should never send OTPs, bank PINs, passwords or unnecessary identity documents through ordinary job messages.

10. DPDP framework

India’s Digital Personal Data Protection Act, 2023 and Digital Personal Data Protection Rules, 2025 use a phased commencement model. KBKB’s operational controls should be maintained against the provisions that are in force at the relevant time, and updated as additional provisions commence.

11. Contact and grievance

Use the in-product Report function for immediate platform issues. The approved KBKB legal operator, grievance officer, postal address and dedicated privacy/grievance contact must be inserted after formal operator confirmation. They are intentionally not copied from another platform.