HiBye Privacy Policy

Effective date: June 21, 2026

Last updated: June 24, 2026

Adbrovz Private Limited ("we", "our", "us") operates HiBye, a privacy-first nearby discovery and chat app for adults 18+. This Privacy Policy explains what information HiBye collects, how we use it, how we share it, how long we keep it, and the choices available to users.

By using HiBye, you acknowledge that you have read and understood this Privacy Policy. If you do not agree with this Privacy Policy, please do not use HiBye.

1. Who Can Use HiBye

HiBye is operated by Adbrovz Private Limited, Bengaluru, Karnataka, India. HiBye is for adults 18+ only. It is not intended for children or minors. Users under 18 must not create an account or use HiBye. If we learn that a minor has created an account, we may restrict or delete the account and related data where legally permitted.

2. Information We Collect

Account and verification data

• Display name, email address, phone number where enabled, OTP verification records, account status, PIN authentication data, session records, device identifiers, platform, app version, login time, and security signals. Phone numbers may be normalized and stored in international format, such as E.164, for login, account recovery, support, and security.

Profile data

• Profile photos, bio, interests, profile completion state, visibility preferences, optional general area/city label, and profile area visibility setting.

Location and discovery data

• Location pings submitted by the app for discovery matching, including coordinates, approximate accuracy, source, capture time, and expiry time.
• General area/city may be detected from device location when the user enables profile area display.
• Encounter and HiBye History records created after the system processes nearby crossed-path events.
• HiBye does not show exact live location to other users.

People, requests, matches, and chat data

• People list relationship state, Hi requests, matches, chat summaries, chat messages, read receipts, typing indicators, buzz events, view-once media metadata, and chat safety actions.
• Double-tap buzz can insert a visible waving-hand message in chat.
• Users may choose whether text chat push notifications show short message previews. Preview is off by default.
• View-once media push notifications do not show media previews.

Photos, media, and user content

• Profile photos, supported chat media, report evidence metadata, support messages, reports, bios, interests, and other content users submit.

Safety and support data

• Blocks, reports, report categories, report status, moderation review data, support tickets, support replies, account restriction records, and safety/audit logs.

Ads, notifications, analytics, and diagnostics

• Ad gate completion state, ad provider events where applicable, push notification tokens, notification delivery state, Firebase Cloud Messaging data needed to deliver notifications, app readiness state, device/session records, rate-limit records, and backend operation logs.
• If analytics or crash diagnostics are enabled, they may process app usage, crash, device, and performance information needed to improve reliability and safety.

3. How We Use Information

We use information to:

• Create, verify, secure, and maintain user accounts.
• Restore sessions and refresh login tokens.
• Process private nearby discovery and HiBye History.
• Show registered HiBye users in People where allowed by privacy and safety rules.
• Enable Hi requests, double opt-in matching, chats, view-once media, and chat buzz.
• Show general area/city only when enabled and available.
• Provide profile, photo, visibility, invisible mode, discovery, notification, and message preview controls.
• Provide support, reports, blocking, moderation, and safety review.
• Prevent spam, fake accounts, fraud, harassment, abuse, scraping, fake GPS misuse, and unauthorized access.
• Operate ads, push notifications, analytics, crash reporting where enabled, app readiness checks, and service diagnostics.
• Maintain, debug, improve, and protect the app, website, and backend services.
• Comply with law, legal process, platform rules, safety obligations, and security requirements.

4. Legal And Operational Bases For Processing

We process data where necessary to provide HiBye, perform our agreement with users, pursue legitimate safety and business interests, comply with legal obligations, investigate misuse, protect users and the service, and where applicable, based on user consent or device permissions.

5. Location Privacy

HiBye uses location for proximity-based discovery. Other users do not receive exact live coordinates from HiBye. User-facing discovery is designed around approximate crossed-path context, not map tracking or live tracking.

Raw location pings are intended to expire automatically after a short retention period. Current default raw location ping retention is 24 hours. Minimized encounter/history records may be kept longer where needed for visible user history, requests, matches, chats, safety, abuse prevention, service integrity, or legal reasons.

If profile area display is enabled, HiBye may use device location to create a general area/city label such as "Indiranagar, Bangalore". This is not exact live location and can be disabled in Settings.

6. Chats, Communications, And Support

Messages sent through HiBye may be stored on our servers. HiBye chat is not end-to-end encrypted unless we explicitly state otherwise. We may review communications, reports, support messages, or related metadata when reasonably necessary for moderation, complaints, fraud review, user safety, legal compliance, or abuse prevention.

Chat access and availability may depend on match status, account status, moderation actions, app rules, or technical limits.

7. Sharing Information

We do not sell personal information. We may share limited information with:

• Other HiBye users, only as needed for visible profile, People, discovery, Hi request, match, chat, and safety features, subject to privacy controls.
• Service providers that help operate hosting, email/OTP, storage, push notifications, ads, analytics, crash reporting, security, moderation, support, and backend infrastructure.
• Platform providers such as app stores, device operating systems, Firebase, Google services, ad networks, and payment/ad-related providers where required for app features.
• Authorities, legal parties, or safety reviewers when required by law, legal process, safety, fraud prevention, abuse prevention, or protection of rights.
• Business transfer parties if we merge, reorganize, sell assets, or transfer some or all of the HiBye service, subject to appropriate safeguards where required.

8. Ads

HiBye may use Google Mobile Ads or similar ad services. Ads may appear before opening a first chat with a matched user. Ad providers may process device, app, advertising, and ad interaction data according to their own policies and user/device settings. Ads do not block safety, support, report, block, legal, logout, or account deletion actions.

9. Push Notifications, Analytics, And Diagnostics

HiBye may use Firebase Cloud Messaging to send notifications for Hi requests, matches, chat messages, view-once media, safety, account, and service updates. Users may control notification permission through device settings and app settings where available.

Message notification previews are optional and off by default. When enabled, normal text chat notifications may show a short sanitized text preview. View-once media notifications stay generic.

If Firebase Crashlytics, Firebase Analytics, or similar tools are enabled, they may help us understand app reliability, crashes, app performance, and aggregate usage. We do not use analytics to collect private chat contents or exact live location for advertising.

10. Cookies, Local Storage, And Device Permissions

The public website may use only basic browser functionality needed to display pages. The app may use device storage, secure storage, notification permission, location permission, camera/photo picker access, network access, vibration/haptic features, and similar platform services when needed for app features.

Users can manage browser cookies in browser settings and app permissions in device settings.

11. User Choices

Users can:

• Start or pause discovery.
• Use invisible mode.
• Manage profile photo visibility.
• Manage profile area/city visibility.
• Manage notification categories and message preview preference.
• Delete individual HiBye History entries or clear visible history.
• Send, accept, decline, or manage Hi requests where controls are available.
• Unmatch, block, or report users.
• Manage logged-in sessions.
• Contact support for account, privacy, safety, or technical help.
• Request account deletion from the app.

12. Data Retention

Retention varies by data type:

• OTP records are short-lived and cleaned after expiry or use.
• Raw location pings are short-lived and cleaned after expiry.
• View-once chat media is designed to be deleted after viewing or expiry.
• HiBye History may be kept for the visible history period unless needed for requests, matches, chats, safety, abuse prevention, service integrity, or legal reasons.
• Account, support, report, audit, moderation, safety, security, and legal records may be retained longer where needed for operation, legal compliance, platform compliance, or abuse prevention.
• Deleted accounts are soft-deleted first, then may be permanently deleted after required retention and review periods.

13. Account Deletion

Users can request account deletion from the app. Some records may be retained for a limited period when needed for safety, fraud prevention, dispute handling, legal compliance, audit requirements, or platform compliance. Visible profile and app access are removed or restricted according to the account deletion flow.

We may require reasonable verification before acting on account deletion, access, correction, or privacy-related requests.

14. Security

We use reasonable technical and organizational safeguards, including HTTPS transport, hashed tokens/PINs where applicable, server-side validation, access control, rate limiting, audit records, and cleanup jobs. No system is completely secure, and users should protect their device, email, phone, and PIN.

15. International Processing

Data may be processed where our hosting, service providers, app stores, ad providers, Firebase/Google services, or operational systems are located. By using HiBye, users understand that data may be processed outside their country or region.

16. Third-Party Links And Services

The app or website may link to third-party websites, app stores, payment/ad providers, platform services, or external resources. Their privacy practices are governed by their own policies.

17. User Responsibilities

Users are responsible for the accuracy of information they provide. Users must not upload, send, request, or share unlawful, infringing, misleading, abusive, harassing, threatening, hateful, sexually exploitative, privacy-violating, fraudulent, spam, scam, malware, or other prohibited content through HiBye.

18. Changes To This Policy

We may update this Privacy Policy. When changes are important, we may show an in-app notice, update the website, or require users to accept updated terms before continuing.

19. Contact And Grievance

For privacy questions, support, requests, complaints, or grievance concerns:

Email: adbrovz@outlook.com

Grievance/contact email: adbrovz@outlook.com

Company: Adbrovz Private Limited

Location: Bengaluru, Karnataka, India

App: HiBye