Privacy Policy
Last updated: 16 July 2026
This policy is published by KanopyKat Technologies Pvt. Ltd., operating as Bihaw ("Bihaw", "we", "us" or "our"), at 704, Indira Iris, Thanisandra Main Road, Bengaluru – 560077, India.
1. Data we collect
- Account data: phone number, name, authentication and account-status records, and, if you sign in with Google, your Google account name and email address.
- Subscription records: purchase records for paid subscriptions, received from Google Play. Card and payment-instrument details stay with Google or Razorpay.
- Community and matching data: profile details, preferences, family or matrimonial information, match activity and invited community participation.
- Marriage planning data: events, guests, invitations, RSVP status, messages, notifications, vendor interactions and optional address details.
- Media data: photos, attachments and associated file metadata that you choose to provide.
- Financial planning data: budgets, expense categories and payment records you enter. These fields are part of the one marriage-assistance purpose and do not require separate acknowledgement.
- Maya data: instructions, context and responses needed for Maya to assist with matching and marriage planning.
- Device, diagnostic and safety data: device model, operating-system version, device and push identifiers, IP-derived security signals, redacted diagnostics, audit events, abuse reports, rights requests and grievance records.
We do not collect biometric data. Bihaw is for adults aged 18 or older.
Information about another person: only share a family member's profile or other personal data when you are authorised to do so. You are responsible for the accuracy and lawfulness of what you submit.
2. One purpose and how we use data
Bihaw is a single-purpose service. We use personal data only to help a person find a match and get help organising a marriage. The purpose code is bihaw_marriage_assistance_v1 and the notice version for new accounts is bihaw_account_notice_v3. Existing v2 receipts and v1 receipts remain valid and do not require re-consent.
That purpose includes account authentication; community and matching; events, guests, invitations and RSVP handling; messages and notifications; media handling; user-initiated vendor discovery and coordination; Maya assistance; reliability diagnostics; fraud and abuse prevention; rights and grievance handling; support; and legal compliance.
No advertising or paid ranking: we do not use personal data for advertising, sell access to it, train unrelated models with it, or rank vendors or matches because they paid us. We do not use data for a purpose unrelated to marriage assistance.
3. Sharing and service providers
We do not sell, rent or trade personal data. We disclose only the data needed for the following activities:
- A vendor selected by you: contact or coordination details needed for the engagement you initiated.
- MSG91: phone number and OTP-delivery data for configured WhatsApp or SMS authentication.
- Google Sign-In: if you choose to sign in with Google, Google shares your Google account name, email address and a signed ID token with us to verify your identity and log you in.
- Google Play Billing: for subscription purchases made on Android, Google processes the payment and we receive purchase records (product, purchase token and status). We never see your card or other payment-instrument details.
- Razorpay Software Pvt. Ltd.: on Android in India, you may choose Razorpay to pay for a Group PRO subscription. Bihaw creates the Razorpay subscription for a plan and amount we set, tagged with internal intent and group identifiers; the app opens Razorpay's own checkout showing the name "Bihaw" and does not pre-fill your name, phone number or email. You enter card, UPI or bank details only inside Razorpay's checkout; they never reach Bihaw. We keep the Razorpay payment and subscription IDs, the signature used to verify the payment, the amount, currency, payment time, refund records, payment status and the tax invoice we issue for each charge.
- Google Firebase Crashlytics: crash diagnostics only (redacted stack traces, app version, build channel, coarse screen category and sign-in state). We do not send analytics events to Firebase and redact phone numbers and tokens before reporting.
- Google Firebase Cloud Messaging: device push token and notification-delivery data for Android notifications.
- Apple Push Notification service: device push token and notification-delivery data for iOS notifications.
- Cloudflare: network and request data needed to deliver and protect the public Bihaw website and its edge traffic.
- Authorities or advisers: incident-linked information when required by law, to protect users, establish or defend a legal claim, or facilitate a complaint to law enforcement such as cyber police.
Self-hosted systems: PostgreSQL, Keycloak, Valkey, object storage, observability, and primary Maya inference run on infrastructure controlled for Bihaw rather than an external SaaS processor. Limited technical data handled by the named external providers may be processed in India or other locations where they operate, subject to applicable contractual and legal safeguards. We do not make a blanket promise that every processing operation occurs only in India.
4. Retention, closure and bans
We retain data while an account is active and while needed to provide Bihaw's single purpose.
Closing your account: When you close your account, Bihaw first erases your past data, then closes the account and signs you out everywhere. Nothing is archived and the account cannot be restored, so export your data first if you want a copy.
13 May 2027 schedule sunset: closure keeps no archive of ordinary product data, so there is nothing for this date to purge, revive or extend.
Separate current statutory records: registration information and removed content with its associated evidence are retained for the applicable 180-day lanes required by the IT Rules. Those narrow records are not an account archive and never reopen a closed account. The registration phone of a closed account is kept for 180 days, reachable through no part of the app, then erased.
Narrow evidence hold: a report or automatic flag alone never extends any retention period and never creates a permanent ban. An authorised reviewer must open a named evidence case or legal hold tied to a specific abuse or safety incident, fraud investigation, legal claim, competent order, authorised government direction, or cyber-police complaint. Only incident-linked items are copied; integrity is recorded; access is restricted; encryption and re-encryption requirements continue to apply; and a reviewer must periodically confirm the documented need. Items are deleted when the case, legal duty, complaint or claim no longer requires them.
Permanent ban: a permanent ban requires approval by two distinct authorised people. We retain only the minimum keyed identity or phone restriction and necessary incident reference needed to enforce it, not an unrestricted copy of ordinary product data. The person may appeal, and Bihaw will review credible error, identity-change and recycled-phone-number claims without exposing another person's data.
5. Account controls and voluntary DPDP-equivalent controls
Self-service export is available in the app and requires a fresh OTP for each export preparation and download. Profile erasure and account closure are available in the app with a fresh OTP, and consent withdrawal is available from Settings. Correction and nomination are not yet available in this activation canary. A grievance or support email can record and route those requests, but email alone cannot complete a sensitive account action. From 13 May 2027, corresponding statutory rights and duties will govern to the extent they apply.
Withdrawal of consent
Withdrawing consent restricts the current account because Bihaw cannot provide its service without the single marriage-assistance purpose. The same account cannot be re-consented or reactivated. Withdrawal does not undo earlier processing and does not remove incident evidence, a narrow legal hold or the minimum record required to enforce a permanent ban.
Export, erasure and closure
Use Privacy & Data → Export My Data for self-service export. Preparing and downloading the export require separate fresh OTP confirmations. Use Settings → Close account to close your account with a fresh OTP. If you cannot use the app, see how to request account and data deletion. Self-service correction and nomination are not yet available in this activation canary. File an in-app grievance or email support@bihaw.net to have another request recorded and routed. Email alone cannot complete it; never send an OTP by email.
Erasure and closure remain subject to the limited retention rules in Section 4. Ordinary closure and erasure are separate requests and may be made together.
6. Grievances and urgent removal requests
Under the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, as amended, our Grievance Officer is:
Name: Aruna BP (resident in India)
Email: grievance@kanopykat.com
Address: 704, Indira Iris, Thanisandra Main Road, Bengaluru – 560077, India
We acknowledge a grievance within 24 hours and resolve it within 7 days from receipt, unless a faster category below applies.
- Depicted-person complaint: action within 2 hours of a complete complaint by the depicted person or an authorised representative about exposed private areas, nudity, a sexual act or conduct, or electronic impersonation, including artificially morphed imagery.
- Other qualifying Rule 3(1)(b) removal or disablement requests: resolution within 36 hours of a complete report.
- Binding removal direction: action within 3 hours of a valid order from a competent court or a reasoned written intimation from a properly authorised government officer.
Safe intake: prefer the in-app grievance form. In email, include the category, a request or content reference if available, and a short description. Do not email an OTP, password, intimate image, full government ID, financial record or other unnecessary sensitive material. Email alone cannot complete an identity-sensitive action; a fresh OTP will be required when the verified workflow ships.
Report an issue to the Grievance Officer
A person dissatisfied with the Grievance Officer's decision may appeal to the Grievance Appellate Committee within 30 days under the IT Rules. Before 13 May 2027, this policy does not promise an immediate appeal to the Data Protection Board of India for voluntary controls. From that date, a person may use the Board remedy after exhausting Bihaw's grievance process where the DPDP Act and Rules provide it.
7. Security and breach response
We use encryption in transit, access controls, audit records and other technical and organisational measures appropriate to the data and risk. No service can promise absolute security.
We respond to a breach under laws in force at the time. The DPDP breach-notification duties scheduled for 13 May 2027 will apply from that date to the extent legally required; this sentence replaces any earlier promise that those uncommenced duties already apply.
8. Children
Bihaw is intended only for people aged 18 and older. If we learn that a child submitted personal data, we will take appropriate steps to remove it.
9. Changes
We may update this policy and will revise the date above and give an appropriate in-app notice. An update does not expand Bihaw beyond its single marriage-assistance purpose. There is no re-consent flow that can reactivate an account after consent is withdrawn.
10. Contact
Email support@bihaw.net or write to 704, Indira Iris, Thanisandra Main Road, Bengaluru – 560077, India.
गोपनीयता नीति — हिंदी
अंतिम अपडेट: 16 जुलाई 2026
हम कौन-सा डेटा लेते हैं और क्यों
Bihaw का केवल एक उद्देश्य है: जीवनसाथी खोजने और विवाह आयोजित करने में मदद करना। हम फोन नंबर, नाम और खाते की स्थिति (Google से साइन इन करने पर Google खाते का नाम और ईमेल); सदस्यता की खरीद के रिकॉर्ड (Google Play से, कार्ड विवरण Google या Razorpay के पास रहता है); community/matching, profile और परिवार की जानकारी; event, guest, invite, RSVP, message और notification; media और metadata; आपके चुने vendor से जुड़ी जानकारी; budget/expense/payment plan; Maya instruction/context; तथा device, push, redacted diagnostic, safety, audit, rights और grievance data लेते हैं। वित्तीय योजना के अलग-अलग field के लिए अलग स्वीकृति नहीं ली जाती। हम biometric data नहीं लेते और सेवा केवल 18 वर्ष या अधिक आयु के लोगों के लिए है।
डेटा का उपयोग authentication, community और matching, event/guest/invite/RSVP, message/notification, media, आपके द्वारा शुरू किए vendor coordination, Maya assistance, reliability, support, rights/grievance handling, security, fraud/abuse रोकने और legal compliance के लिए होता है। हम डेटा नहीं बेचते, advertising के लिए उपयोग नहीं करते, unrelated model training में नहीं लगाते और भुगतान के कारण vendor या match को ऊपर नहीं रखते।
साझाकरण और सेवा प्रदाता
- आपके चुने विक्रेता को केवल आपके शुरू किए समन्वय की आवश्यक जानकारी;
- MSG91 को configured WhatsApp या SMS OTP के लिए फोन और delivery data;
- Google Sign-In: यदि आप Google से साइन इन करना चुनते हैं, तो Google आपकी पहचान सत्यापित करने और लॉगिन के लिए आपके Google खाते का नाम, ईमेल और हस्ताक्षरित ID token हमें देता है;
- Google Play Billing: Android पर सदस्यता खरीद का भुगतान Google प्रोसेस करता है; हमें खरीद रिकॉर्ड (उत्पाद, purchase token और स्थिति) मिलते हैं। आपके कार्ड या भुगतान साधन का विवरण हम कभी नहीं देखते;
- Razorpay Software Pvt. Ltd.: भारत में Android पर आप Group PRO सदस्यता के भुगतान के लिए Razorpay चुन सकते हैं। Bihaw हमारे तय plan और राशि का Razorpay subscription बनाता है, जिस पर आंतरिक intent और group पहचानकर्ता लगे होते हैं; ऐप Razorpay का अपना checkout खोलता है जिसमें नाम "Bihaw" दिखता है, और आपका नाम, फोन या ईमेल पहले से नहीं भरता। कार्ड, UPI या बैंक विवरण आप केवल Razorpay के checkout में डालते हैं; वे Bihaw तक कभी नहीं पहुँचते। हम हर भुगतान के लिए Razorpay payment व subscription ID, सत्यापन signature, राशि, मुद्रा, भुगतान का समय, refund रिकॉर्ड, भुगतान स्थिति और जारी tax invoice रखते हैं;
- Google Firebase Crashlytics: केवल crash diagnostics (redacted stack trace, app version, build channel, मोटी screen श्रेणी और साइन-इन स्थिति)। हम Firebase को analytics events नहीं भेजते और रिपोर्ट से पहले फोन नंबर व token redact करते हैं;
- Google Firebase Cloud Messaging और Apple Push Notification service को पुश टोकन/डिलीवरी डेटा;
- Cloudflare को सार्वजनिक वेबसाइट और एज ट्रैफिक की डिलीवरी/सुरक्षा का नेटवर्क डेटा;
- कानून, उपयोगकर्ता सुरक्षा, कानूनी दावा या साइबर-पुलिस शिकायत के लिए जरूरी घटना-संबंधित जानकारी।
Self-hosted systems: PostgreSQL, Keycloak, Valkey, object storage, observability और primary Maya inference Bihaw के लिए नियंत्रित infrastructure पर चलते हैं, external SaaS processor पर नहीं। नामित external provider का सीमित technical data भारत या उनके संचालन वाले अन्य स्थानों पर लागू सुरक्षा उपायों के साथ process हो सकता है; हम यह पूर्ण दावा नहीं करते कि हर processing केवल भारत में होती है।
अवधि, खाता बंद करना और प्रतिबंध
खाता बंद करना: जब आप अपना खाता बंद करते हैं, तो Bihaw पहले आपका पिछला डेटा मिटाता है, फिर खाता बंद करता है और आपको हर जगह से साइन आउट करता है। कुछ भी archive नहीं होता और खाता वापस नहीं खोला जा सकता, इसलिए अगर आपको कॉपी चाहिए तो पहले अपना डेटा एक्सपोर्ट कर लें।
खाता बंद करने पर ordinary product data का कोई archive नहीं रहता, इसलिए 13 मई 2027 की तारीख से purge, revive या extend करने के लिए कुछ नहीं है।
अलग current statutory record: registration information और removed content/associated evidence लागू IT Rules के 180-day lanes में रहते हैं। ये narrow records account archive नहीं हैं और बंद खाते को कभी वापस नहीं खोलते। बंद खाते का registration phone 180 दिन तक रखा जाता है, app के किसी भी हिस्से से उस तक पहुँच नहीं होती, फिर उसे मिटा दिया जाता है।
केवल report या automatic flag से कोई retention अवधि नहीं बढ़ती और permanent ban नहीं लगता। authorised reviewer को specific incident, investigation, claim, competent order, authorised government direction या cyber-police complaint के लिए named evidence case/legal hold खोलना होगा। केवल incident-linked item copy होंगे; integrity record, restricted access, encryption/re-encryption और periodic human review जरूरी हैं; need समाप्त होने पर delete होंगे। Permanent ban के लिए दो अलग authorised human approvals जरूरी हैं। केवल minimum keyed identity/phone restriction और incident reference रहेगा; error, identity-change या recycled-number claim पर appeal और review उपलब्ध है।
निर्यात, सुधार, मिटाना, सहमति वापस लेना और बंद करना
app में self-service export, profile erase और account closure उपलब्ध हैं, हर एक के लिए fresh OTP पुष्टि जरूरी है; export तैयार करने और download करने, दोनों के लिए अलग OTP चाहिए। सहमति वापस लेना Settings से उपलब्ध है। self-service correction और nomination इस activation canary में अभी उपलब्ध नहीं हैं। in-app grievance या support@bihaw.net उन request को record और route कर सकता है, लेकिन email अकेले sensitive action पूरी नहीं करता। OTP कभी email न करें। 13 मई 2027 से लागू statutory rights/duties जहाँ लागू हों वहाँ govern करेंगे।
खाता और डेटा हटाने का अनुरोध कैसे करें: खाता हटाने का पृष्ठ देखें।
सहमति वापस लेने पर मौजूदा खाता प्रतिबंधित हो जाता है और उसी खाते में दोबारा सहमति देकर सक्रिय नहीं किया जा सकता। इससे पहले हुई प्रोसेसिंग, सीमित कानूनी/घटना प्रमाण या स्थायी प्रतिबंध का न्यूनतम रिकॉर्ड नहीं मिटता। खाता बंद करना और पुराना डेटा मिटाना अलग अनुरोध हैं और साथ भी किए जा सकते हैं।
शिकायत और तुरंत हटाने के अनुरोध
शिकायत अधिकारी: Aruna BP, grievance@kanopykat.com, 704, Indira Iris, Thanisandra Main Road, Bengaluru – 560077। शिकायत की acknowledgement 24 घंटे में और resolution 7 दिन में होगा।
in-app grievance को प्राथमिकता दें। email में category, उपलब्ध request/content reference और छोटा विवरण दें। OTP, password, intimate image, पूरा government ID, financial record या unnecessary sensitive material न भेजें। identity-sensitive request के verified flow ship होने पर fresh OTP जरूरी होगा। pictured person/private area, nudity, sexual act/conduct या electronic impersonation (artificially morphed image सहित) की complete complaint पर 2 घंटे; दूसरे qualifying Rule 3(1)(b) removal/disablement request पर 36 घंटे; और competent court order या properly authorised officer की reasoned written intimation पर 3 घंटे में action होगा। Grievance Officer के decision के खिलाफ 30 दिन में Grievance Appellate Committee में appeal की जा सकती है। 13 मई 2027 से पहले Data Protection Board में immediate appeal का promise नहीं है; उसके बाद लागू कानून के अनुसार remedy उपलब्ध होगा।
सुरक्षा, बच्चे और संपर्क
हम transit encryption, access controls और audit records जैसे उचित उपाय अपनाते हैं। 13 मई 2027 से लागू होने वाले DPDP breach नियम उस तारीख से लागू होंगे; तब तक उस समय लागू कानून के अनुसार प्रतिक्रिया होगी। Bihaw केवल 18 वर्ष या अधिक आयु के लोगों के लिए है। संपर्क: support@bihaw.net।