Privacy Policy
This Privacy Policy explains how the HoneyPair Android app, published by the Web Naksha team, handles information while providing consent-based partner status sharing, app usage tools, premium features, notifications, and account services.
Privacy Summary
HoneyPair is built for transparent, consent-based sharing. The app should only be used when both connected people understand what the app does and agree to use it.
- We do not sell, rent, or trade user information.
- Google sign-in is required so HoneyPair can protect accounts, coins, premium access, and partner features.
- We store limited account, device, connection, partner, usage, app list, app-rule, coin, premium, notification, and diagnostic data needed for the app to work.
- When activity sharing is enabled, your connected partner may see your online state, screen state, current foreground app, call-state label if enabled, battery status, and app usage summaries.
- We do not read your chats, typed text, passwords, OTPs, contacts, SMS, screen contents, photos, videos, microphone audio, camera images, files, or precise location.
- Optional call detection uses notification access only to detect call state/app label; HoneyPair does not store message text, sender names, or contact names.
- External links, earning tasks, blog/tutorial pages, update links, support links, and ad or smartlink destinations may be handled by third-party websites or ad providers.
- You can stop sharing by disconnecting your partner, disabling permissions, signing out, requesting deletion, clearing app data, or uninstalling HoneyPair.
1. Scope
This policy applies to the HoneyPair Android app published by Web Naksha. HoneyPair helps two consenting users connect and share limited presence, app activity, usage history, partner actions, and account-based premium features with each other.
This policy does not control third-party websites or services that may open outside HoneyPair, such as social links, support pages, tutorial pages, blog pages, update links, earning-task links, ad links, or smartlink destinations. Those services may have their own privacy practices.
2. Consent and Activity Sharing
HoneyPair must not be used to secretly monitor, supervise, or track another person. Activity sharing is intended only for connected users who have both agreed to use the app.
When you enable activity sharing, HoneyPair uses Android Usage Access to identify the app currently open on your device. HoneyPair does not see what you are typing, reading, sending, watching, or viewing inside that app.
Your connected partner may see limited status information such as whether you are online, whether the screen is on or off, the currently active app name, ongoing call-state label if you enable call detection, battery status, app usage summaries, permission readiness, and the latest update time. You can turn sharing off at any time in Android Settings or inside HoneyPair by disconnecting your partner.
Some HoneyPair features allow one connected partner to send a nudge, ring the partner device, request usage sync, or set app-block rules. These features are designed for mutually connected partners and may require premium access and device permissions before they work.
3. Information Handled by HoneyPair
HoneyPair is designed to handle only the information needed for account login, partner connection, live sharing, app usage tools, premium access, rewards, security, and support. HoneyPair does not ask for phone login, payment card details, banking information, or identity documents.
| Category | Examples | Purpose |
|---|---|---|
| Account and profile data | Google/Firebase user ID, HoneyPair account ID, display name, email address, profile photo URL, sign-in state, and account creation/update times. | To keep accounts, coins, premium access, device binding, partner features, and support requests tied to the correct user. |
| App connection data | App-generated connection code, device connection UID, partner connection, partner display name you choose, mutual connection state, and connection timestamps. | To connect two users and keep each person linked to the correct partner. |
| Presence status | Online/offline state, screen on/off state, live socket state, latest status update time, sharing enabled state, battery percentage, charging state, and permission readiness. | To show your connected partner whether HoneyPair is active and whether sharing is currently working. |
| Activity status | Current foreground app name and app package name after you enable Android Usage Access, plus a call-state/app label if optional call detection is enabled. | To show limited activity status to your connected partner after consent. |
| App list, icons, and usage history | Installed launcher app names, package names, app versions, app icons or icon URLs, usage duration, last-used time, daily totals, and synced usage windows. | To show your own and your connected partner's app usage history, recent apps, app management, and app-rule screens. |
| Partner app rules | Blocked package name, app name, rule mode, daily limit minutes, schedule start/end time, immediate block state, rule creator, and sync timestamps. | To apply partner-managed app limits and show the blocked-app screen on the target device when required permissions are enabled. |
| Coins, tasks, and premium data | HoneyCoin balance, earning history, task attempts, verification state, package purchases, premium plan, expiry time, device binding, purchase keys, and premium notices. | To manage rewards, prevent modified-app abuse, activate premium features, send expiry reminders, and keep premium purchases server-verified. |
| Partner actions and inbox data | Nudge messages, ring requests, stop-ring actions, partner disconnect notices, permission-off notices, system notices, optional image/open links, read state, and timestamps. | To deliver HoneyPair notifications, show the in-app notification inbox, and let users review recent partner/system messages. |
| Device and app health data | App version, Android version, SDK level, device model, manufacturer, language setting, FCM token, stability reports, startup timing, connectivity, socket health, and network performance signals. | To fix crashes, improve reliability across Android versions, and understand whether the app is working properly. |
| Notification data | Notification routing information, message title, message body, optional image link, optional open link, and delivery-related technical signals. | To send app updates, service notices, announcements, and important HoneyPair messages. |
| App settings and content links | Support link, privacy link, tutorial link, update message, maintenance message, social links, banner image/link, earning category/tutorial link, blog link, and smartlink task URL. | To show current app information, updates, earning tasks, Web Naksha-managed content, and external destinations inside HoneyPair. |
| Security signals | App authenticity checks, request validation signals, and abuse-prevention information. | To protect HoneyPair from unauthorized access, spam, modified app abuse, and service misuse. |
4. Information We Do Not Collect
HoneyPair is not designed to collect sensitive personal content from your device. In particular, HoneyPair does not intentionally collect or store:
- Your phone number, home address, government ID, identity documents, or payment card details.
- Precise GPS location or live location tracking.
- Contacts, call logs, SMS messages, chat messages, OTPs, or third-party notification message contents.
- Photos, videos, files, microphone audio, camera images, or media library contents.
- Typed text, passwords, keystrokes, screen recordings, screenshots, or screen contents.
- Browser page contents, search history, or private content inside other apps.
- Bank account information or financial account credentials.
If you voluntarily type personal information into a partner name, nudge message, support request, or other app field, that information may be visible or handled only for the feature or request you used. Please avoid entering sensitive personal details.
HoneyPair's optional call detection does not require or store contact names, message text, OTPs, or notification body text. It is used only to detect whether a supported calling app appears to have an active call state.
5. How Information Is Used
To connect two consenting users and show the correct partner status.
To authenticate users, protect account IDs, keep coins/premium server-verified, and prevent duplicate or abusive access.
To show limited online, screen, battery, call-state, and active-app status only after the required settings are enabled.
To show app usage history, sync partner app lists, and apply partner app-block rules when both connection and permissions allow it.
To verify earning tasks, update HoneyCoin balances, activate premium packages, send expiry reminders, and prevent modified-app abuse.
To improve connection stability, background reliability, startup speed, and compatibility across Android devices.
To send important app messages, update alerts, maintenance notices, and support information.
To prevent abuse, reject unauthorized requests, protect the service, and reduce risks from modified apps.
To identify crashes, performance problems, failed connections, and device-specific issues.
6. When Information Is Shared
Web Naksha does not sell, rent, or trade HoneyPair user information. Limited information may be shared only in the following situations:
- With your connected partner: limited presence and activity status is shown to the partner you connect with.
- With your connected partner for partner features: app usage summaries, permission readiness, nudge/ring events, partner disconnect notices, and app-rule status may be visible to that partner.
- With trusted service providers: secure cloud, authentication, messaging, diagnostics, analytics, hosting, database, and storage providers process technical data needed to operate HoneyPair.
- With Google/Firebase services: HoneyPair uses Firebase Authentication, Cloud Messaging, App Check, Analytics, Crashlytics, and Performance Monitoring for login, notifications, protection, reliability, and diagnostics.
- With external task/ad destinations: if you open earning tasks, blog/tutorial pages, update links, support links, banner links, smartlinks, or ad links, those third-party destinations may receive normal web request information under their own policies.
- For security and legal reasons: information may be used or disclosed if required by law, to investigate abuse, to protect users, or to protect the app and service.
7. Android Permissions and Special Access
| Permission or setting | Why HoneyPair uses it |
|---|---|
| Internet and network state | To sign in, sync partner status, load app settings, verify premium/coins/tasks, receive notifications, and check connectivity. |
| Usage Access | To detect the current foreground app, build app usage summaries, and enforce app-block rules when partner app rules are enabled. |
| Display over other apps | To show HoneyPair's blocked-app screen over an app that has been limited by a connected partner. |
| Notifications | To show ongoing sharing status, partner status alerts, ring/nudge notices, premium notices, app notices, and important updates. |
| Notification access for call detection | Optional. Used only when you enable call detection to identify generic call state from supported calling apps. HoneyPair does not store message text, sender names, contacts, or OTPs. |
| Foreground service | To keep consent-based sharing active while showing an ongoing notification. |
| Start after device restart | To restore sharing after reboot when you previously enabled sharing and required permissions remain granted. |
| Battery and background settings | To guide you to Android or device-brand settings that help HoneyPair stay connected reliably. |
| Install update files | To support direct APK updates when you choose to install an update provided through HoneyPair because the app may be distributed outside Google Play. |
8. Your Choices
- Control Google sign-in: you can sign out of HoneyPair, but account-based features require Google sign-in.
- Turn off activity sharing: disable Usage Access for HoneyPair in Android Settings or use HoneyPair's activity-sharing controls.
- Turn off app blocking: remove Display over other apps permission or disconnect your partner.
- Turn off call detection: disable the call-detection toggle or remove Notification Access for HoneyPair.
- Disconnect your partner: use the disconnect option inside HoneyPair to stop sharing with that person and clear local partner app rules.
- Disable notifications: turn off HoneyPair notifications in Android Settings, although some foreground-service behavior may require an ongoing notification.
- Control background behavior: change battery, background, and auto-start settings from your device settings.
- Control earning tasks: you can choose whether to open external task, blog, tutorial, ad, or smartlink destinations.
- Clear local data: clear HoneyPair app data or uninstall the app from your device. Server records may remain until deleted under a valid deletion request or normal retention rules.
- Request deletion: contact Web Naksha through the official support channel or at webnakshabd@gmail.com and include your HoneyPair account ID or connection code if available.
9. Retention and Deletion
HoneyPair keeps only limited service data for as long as needed to operate the app, maintain security, troubleshoot issues, comply with legal obligations, or respond to deletion requests.
- Presence and activity status may be overwritten as new status updates are sent.
- Account, connection, partner, premium, and coin records may remain while your account exists or while needed for support, security, accounting, abuse prevention, or legal reasons.
- App usage summaries, app lists, and app icons may remain while usage-history, app-management, or partner features need them, and may be refreshed or overwritten by newer syncs.
- Partner app-block rules remain until removed, replaced, disconnected, or no longer eligible. Local cached block rules may be cleared when premium access is not valid.
- Notification inbox records may remain locally on your device until you clear them, and related server delivery records may be kept for troubleshooting and abuse prevention.
- Diagnostics, crash, performance, and security records are kept only as needed to investigate crashes, improve reliability, protect accounts, and maintain the service.
- Deletion requests are reviewed through the official support channel. Some records may be retained when required for legal, security, anti-abuse, or accounting purposes.
10. Security
HoneyPair uses encrypted network connections, Firebase authentication, server-side request validation, device-binding checks for premium access, app authenticity checks, rate limits, access controls, and Android platform security features to help protect the service.
No mobile app can be guaranteed impossible to reverse engineer. Web Naksha avoids placing private server credentials or unrestricted service keys inside the HoneyPair Android app.
If you believe you have found a security issue, please contact Web Naksha through the official support channel or the support link shown in HoneyPair.
11. Children
HoneyPair is not intended for children. Web Naksha does not knowingly collect information from children under 13, and HoneyPair should not be used by anyone who is not old enough to understand and consent to the app's partner-sharing features. If you believe a child has provided information through HoneyPair, contact Web Naksha so the information can be reviewed and removed where appropriate.
12. International Processing
HoneyPair may use service providers that process technical data in countries other than your own. By using HoneyPair, you understand that limited service data may be transferred and processed where those providers operate, subject to applicable security and data-protection measures.
13. Changes and Contact
Web Naksha may update this Privacy Policy from time to time, including when HoneyPair changes, when service providers change, or when legal requirements change. Web Naksha reserves the right to publish an updated Privacy Policy whenever needed to keep this policy accurate and legally compliant. The updated policy will show a new effective date.
For privacy questions, support requests, or deletion requests, use the official HoneyPair support channel, the support link shown inside the app, or email webnakshabd@gmail.com.