Back to DebugPair Pro

Privacy Policy

Last Updated: November 12, 2026

Application: Debug Pair Pro • Package ID: com.briyoom.debugpair.pro

Developer: Yash Rayjada (YBR Digital) • Jurisdiction: India

Last updated: November 12, 2026

1. Introduction & Who We Are

Welcome to Debug Pair Pro (“we,” “our,” “us,” or the “App”). This Privacy Policy explains how Yash Rayjada, operating under the brand YBR Digital, based in Gujarat, India, collects, uses, protects, and discloses information when you purchase, download, install, and use our premium mobile application Debug Pair Pro (Package ID: com.briyoom.debugpair.pro).

Debug Pair Pro is a dedicated, standalone, professional-grade developer utility, diagnostic suite, and wireless Android Debug Bridge (ADB) client. It is engineered for software developers, QA engineers, system administrators, and Android power users to inspect device performance, stream live low-latency screen mirrors, debloat system packages, execute shell commands, and interact with Android devices over local Wi-Fi networks without requiring a physical computer.

Key Privacy Principle: Debug Pair Pro is built on a local-first, privacy-respecting architecture. Your cryptographic pairing credentials, device logs, command histories, transferred files, and real-time screen feeds remain strictly on your local host device and your private local network. We do not sell your personal data, nor do we operate remote user profiling databases.

2. Commercial & Architectural Model of Debug Pair Pro

Debug Pair Pro is distributed as a standalone paid application on the Google Play Store. It differs substantially in architecture and privacy profile from ad-supported or freemium utilities:

  • 100% Ad-Free (Zero Advertising SDKs): Debug Pair Pro contains no advertisements whatsoever. The Google Mobile Ads (AdMob) SDK is completely omitted from the application. We do not collect, request, or transmit Google Advertising Identifiers (GAID), nor do we integrate third-party ad networks or tracking trackers.
  • Zero In-App Billing or Subscription SDKs: You purchase Debug Pair Pro once upfront directly through the Google Play Store. The application contains no recurring subscriptions, no paywalls, and no third-party purchase tracking libraries (such as RevenueCat). All features are permanently unlocked out of the box.
  • Minimal Network Footprint: External internet communication is restricted solely to anonymous diagnostic crash reporting (Firebase Crashlytics), aggregated usage telemetry (Firebase Analytics), and lightweight operational status checks.

3. Information We Collect

We classify information handled by Debug Pair Pro into three distinct categories:

A. Information You Provide Voluntarily

  • Device Nicknames & Configuration: Custom labels or names you assign to your saved target ADB devices (e.g., “QA Test Android TV” or “Pixel Tablet 8”).
  • Console Commands & Custom Snippets: Shell commands, script parameters, and console snippets you save or organize within the Console feature.
  • Customer Support Communications: If you contact us directly via email (info@ybrdigital.in), we receive your email address, name, and any contextual diagnostic text or screenshots you choose to share to help resolve your inquiry.

B. Information Collected Automatically

  • Aggregated Usage Analytics (Firebase Analytics): We collect aggregated, de-identified telemetry about application usage, such as screen views, button clicks, feature navigation, pairing attempt outcomes (success or general failure code), APK installation success/failure counts, and in-app review triggers. We do not log shell outputs, device passwords, or personal file contents.
  • Crash & Diagnostic Reports (Firebase Crashlytics): In the event of an unexpected crash or framework exception, Crashlytics captures technical stack traces, device hardware model, operating system version, memory availability, and timestamp of the incident to help us diagnose and fix stability issues.
  • App Configuration & Status Checks: On launch, Debug Pair Pro securely connects to our configuration servers transmitting solely the application package identifier (com.briyoom.debugpair.pro) to verify operational status, check whether scheduled maintenance is active, and confirm the minimum supported application version. No personally identifiable information, user data, network address, or target device data is transmitted during this check.

C. Technical & Operational Data Processed Locally

  • Cryptographic ADB Authentication Keys: To establish authenticated ADB sessions over Wi-Fi, Debug Pair Pro generates a 2048-bit RSA keypair and a self-signed X.509 certificate on your Android host device. These cryptographic keys are stored exclusively in internal sandboxed app storage and are never uploaded to any remote server.
  • Local Network Discovery Data: IP addresses (RFC 1918 private subnet addresses), TCP ports, and mDNS service names (such as _adb-tls-connect._tcp. and _adb-tls-pairing._tcp.) broadcast on your local Wi-Fi network are processed solely in memory and local storage to connect to your devices.
  • Target Device Telemetry: CPU usage percentages, RAM statistics, internal storage breakdowns, running process lists, installed package names, battery health, and display properties queried via ADB commands are rendered temporarily on your screen and are never transmitted to our servers.
  • Local Screen Mirroring Feed: Live screen mirroring is delivered via an on-device H.264 video stream decoded directly through Android's hardware MediaCodec onto a local texture. No video stream data ever leaves your local network.

4. Android Permissions & Hardware Access

Debug Pair Pro requests only permissions strictly necessary to deliver its core wireless debugging, device pairing, and utility capabilities. The table below details every permission declared in our application manifest:

Permission Type Purpose & Scope in Debug Pair Pro Data Involved
INTERNET Normal Enables raw TCP socket communication with target ADB devices over local Wi-Fi (ports 5555, pairing ports) and enables secure HTTPS communication for Firebase crash reporting, analytics, and remote maintenance checks. Local socket packets; anonymized diagnostic logs and crash stack traces.
ACCESS_NETWORK_STATE Normal Allows Debug Pair Pro to detect whether an active network connection exists before initiating ADB connections or attempting network operations. Network state (connected/disconnected, Wi-Fi vs. cellular).
ACCESS_WIFI_STATE Normal Enables inspecting Wi-Fi connection parameters required to support local wireless ADB device discovery and pairing. Wi-Fi connection status.
CHANGE_WIFI_MULTICAST_STATE Normal Allows acquiring a Wi-Fi Multicast Lock (WifiManager.MulticastLock) to receive local mDNS / DNS-SD broadcast packets for discovering wireless ADB services on the subnet. mDNS service advertisement packets on the local network.
NEARBY_WIFI_DEVICES Runtime (Android 13+) Required by Android 13+ (API 33+) to scan for and connect to nearby Wi-Fi devices. Configured with android:usesPermissionFlags="neverForLocation" in our manifest. Local Wi-Fi device names and ADB service endpoints. Never used to derive physical location.
ACCESS_LOCAL_NETWORK Runtime (Android 16/17+) Required on next-generation Android releases with Local Network Protection (LNP) to allow direct socket communication with devices on local private subnets (RFC 1918). Local subnet IP addresses and ports of target ADB devices.
POST_NOTIFICATIONS Runtime (Android 13+) Displays an ongoing foreground notification while an active ADB connection is maintained, informing the user of the connected device and providing a one-tap Disconnect action. Connection status text and device name shown locally.
FOREGROUND_SERVICE Normal Allows running the ongoing background service (AdbForegroundService) so Android does not kill active ADB terminal, file transfer, or screen streaming sessions when minimized. Service operational lifecycle.
FOREGROUND_SERVICE_CONNECTED_DEVICE Normal (Android 14+) Declares to Android 14+ (API 34+) that the foreground service manages an active connection to an external peripheral or networked computing device (the target ADB device). Connected device identifier and session state.
No Invasive Hardware Access: Debug Pair Pro does NOT request camera, microphone, or GPS location permissions. Screenshots saved to your gallery utilize Android's Scoped Storage (MediaStore.Images.Media.EXTERNAL_CONTENT_URI in the Pictures/DebugPair directory) without requesting legacy wide-storage permissions. File sharing is facilitated securely via Android's FileProvider.

5. How We Use Information

We process collected and local data strictly for the following legitimate operational purposes:

  1. Delivering Core ADB Functionality: Facilitating wireless pairing, executing ADB shell commands, deploying the local screen mirroring agent, transferring selected files, and managing apps with unlimited access.
  2. Maintaining Connection Stability: Displaying foreground service notifications to prevent operating system task-killers from aborting long-running operations.
  3. App Diagnostics & Crash Mitigation: Investigating stack traces and error logs via Firebase Crashlytics to resolve software crashes and compatibility issues across diverse Android hardware.
  4. Analytics & Performance Optimization: Evaluating aggregated feature engagement (e.g., which commands or diagnostic tools are most utilized) to optimize app ergonomics and performance.
  5. Service Maintenance & Updates: Checking whether scheduled maintenance is ongoing and notifying users of critical app updates via Google Play In-App Updates.

6. Third-Party Services & SDKs

Debug Pair Pro incorporates trusted third-party software development kits (SDKs) solely to provide infrastructure, diagnostics, and update capabilities. Each provider operates under its own privacy policy:

Service / SDK Provider Role in Debug Pair Pro Privacy Policy Link
Firebase Analytics Google LLC Measures aggregated, de-identified user engagement events and screen views. Google Privacy Policy
Firebase Crashlytics Google LLC Captures crash stack traces and diagnostic logs for stability troubleshooting. Firebase Privacy Policy
Google Play In-App Review & Updates Google LLC Enables in-app Play Store ratings and flexible/immediate application updates. Google Play Terms
Open Source Engines (libadb-android & scrcpy-server) Open Source Community Local ADB protocol implementation and local H.264 screen mirroring encoder. Runs 100% locally on device. N/A (Local Code Execution Only)

7. Data Storage, Security & Retention

A. Where Data is Stored

  • Local Host Storage (SharedPreferences): Your saved device profiles (host IP, port, nickname, auto-connect preference), custom shell commands, favorite command IDs, onboarding completion status, and daily action counts are stored locally on your device.
  • Internal Key Storage: Generated RSA private keys (adb_key.pk8) and public certificates (adb_cert.der) are stored exclusively in the app's sandboxed internal directory (context.filesDir/adb_keys).
  • Temporary Files: Files downloaded via the File Manager or temporary screenshot captures are stored in internal cache (context.cacheDir) and are overwritten or cleared automatically.

B. Security Measures

  • Encrypted Communications: All remote network communications with YBR Digital and Google Firebase are encrypted using industry-standard Transport Layer Security (TLS / HTTPS).
  • Local Cleartext Exception: In accordance with Android's network_security_config.xml, cleartext communication is permitted solely for local private subnets (RFC 1918) and loopback addresses to connect to local ADB daemon ports that do not support CA-signed TLS certificates.
  • Backup Prevention: We declare android:allowBackup="false" in our manifest to prevent ADB backup tools from extracting your private ADB authentication keys or local configurations.
  • Secure File Sharing: All inter-app file exchanges (e.g., viewing an image or opening a pulled text file) are isolated through an Android FileProvider using ephemeral content URIs rather than exposing public file paths.

C. Data Retention

Local application data persists until you manually delete saved items, reset ADB keys in Settings, clear app data via Android Settings, or uninstall Debug Pair Pro. Diagnostic crash logs retained by Google Firebase are subject to Firebase's default 90-day retention window before automatic deletion.

8. Data Sharing & Disclosure

We do not sell, rent, lease, or monetize your personal information to third parties.

We disclose information only in the limited circumstances outlined below:

  • Infrastructure Providers: We share diagnostic data with Google (Firebase) solely to deliver crash reporting and analytics as described in this policy.
  • Legal Obligations: We may disclose information if required to do so by applicable law, regulation, legal process, or lawful governmental request from a competent authority.
  • Protection of Rights: We may disclose information where necessary to enforce our Terms & Conditions, investigate potential violations, or protect the rights, property, or safety of Debug Pair Pro, our users, or the public.

9. Zero Advertising & Anonymized Diagnostics

A. Zero Advertising Commitment

Debug Pair Pro is completely ad-free. We do not integrate the Google Mobile Ads SDK, banner networks, interstitial ads, or any behavioral tracking trackers. We do not gather or monetize advertising identifiers.

B. Analytics Disclosures

Firebase Analytics helps us understand how features are used in the aggregate (e.g., frequency of remote control usage vs. file manager operations). We do not record user keystrokes, personal file names, or terminal command arguments containing sensitive data. You may opt out of personalized tracking via your Android device settings under Google > Ads > Delete advertising ID.

10. User Rights & Data Deletion Choices

Depending on your jurisdiction, you have specific legal rights regarding your personal information under applicable data protection laws (such as India's DPDPA 2023, EU/UK GDPR, and California's CCPA/CPRA):

  • Right of Access & Portability: You may request confirmation of whether we process any personal data relating to you and request a copy of such data.
  • Right to Rectification: You may update or correct your locally stored device names and commands directly within the app.
  • Right to Erasure (“Right to be Forgotten”): Because Debug Pair Pro does not require user accounts or maintain a remote user profile database, you can erase your data instantly through the following methods:
    1. Reset ADB Keys: Navigate to Settings > Reset ADB RSA Keys to permanently delete your host cryptographic keypair.
    2. Delete Saved Devices / Commands: Swipe or tap delete on any saved device in the Devices tab or snippet in the Console tab.
    3. Clear App Storage: Open your phone's Settings > Apps > Debug Pair Pro > Storage > Clear Storage / Clear Data to instantly wipe all local preferences, database records, and cached files.
    4. Uninstall the App: Removing Debug Pair Pro from your device completely deletes all sandboxed internal files.
  • Right to Withdraw Consent: You may revoke Android runtime permissions (Notifications, Nearby Devices, Local Network) at any time via your device's system settings under Settings > Apps > Debug Pair Pro > Permissions.
  • Requesting Erasure of Support Records: If you have communicated with us via email and wish to have your support correspondence permanently purged, email your request to info@ybrdigital.in with the subject “Data Deletion Request.” We will process your verified request within 30 days.

11. Children's Privacy

Debug Pair Pro is a specialized technical developer tool intended for software engineers, IT professionals, and adult technology hobbyists. It is not directed to children under the age of 13 (or under 16 for residents of the European Union/UK, or under 18 for minors in India without parental consent).

We do not knowingly collect, solicit, or process personal data from children. If we discover that a child has provided us with personal information, we will take immediate steps to delete such information from our records. If you are a parent or guardian and believe your child has provided us with personal information, please contact us immediately at info@ybrdigital.in.

12. International Data Transfers

Our diagnostic service provider (Google LLC) is headquartered in the United States and maintains server infrastructure globally. If you use Debug Pair Pro outside the United States, your de-identified diagnostic crash logs and analytics data may be transferred to, stored, and processed in jurisdictions that may have different data protection laws than your country of residence.

Google utilizes lawful transfer mechanisms approved by competent regulatory bodies, including Standard Contractual Clauses (SCCs) and adherence to recognized data privacy frameworks, ensuring adequate levels of data protection.

14. Changes to this Privacy Policy

We may update this Privacy Policy from time to time to reflect modifications in our features, changes in legal requirements, or operational updates. When revisions occur, we will update the “Last updated” date at the top of this document.

Material modifications will be notified within the application via an on-screen notice or update banner. We encourage you to review this Privacy Policy periodically to stay informed about how we safeguard your data. Continued use of Debug Pair Pro following the posting of changes constitutes acceptance of the revised policy.

15. Contact Information

If you have any questions, inquiries, complaints, or data deletion requests regarding this Privacy Policy, please contact us at:

16. Google Play Data Safety Summary (Pro Edition)

To assist you and provide complete transparency in alignment with Google Play's mandatory Data Safety declaration form for paid standalone applications, the following table summarizes all data types collected, shared, or processed by Debug Pair Pro:

Data Category Data Type Collected or Shared? Purpose Ephemeral or Stored? Optional or Mandatory?
Location Approximate / Precise Location Not Collected N/A (NEARBY_WIFI_DEVICES is flagged with neverForLocation) None N/A
Personal Info Name, Email Address Collected Only if Contacting Support Customer support & troubleshooting communications. Stored in support inbox until resolved. Optional (User-initiated)
Financial Info Payment / Credit Card Details Not Collected by App Upfront paid purchase processed exclusively by Google Play Store; app collects zero financial data. None (Processed by Google Play) N/A
App Activity App interactions, screen views, button clicks Collected (Firebase Analytics) Analytics, feature optimization, bug diagnostics. Aggregated on Firebase (90-day retention). Mandatory for basic app telemetry
App Info & Performance Crash logs, fatal exceptions, performance diagnostics Collected (Firebase Crashlytics) Crash mitigation, application stability, bug fixes. Stored on Firebase Crashlytics servers. Mandatory
Device or Other IDs Advertising ID (GAID) Not Collected Debug Pair Pro is completely ad-free and contains no advertising SDKs. None N/A
Files & Media User-selected files, screenshots Processed 100% Locally Local ADB push/pull file transfers and local screenshot saving to Pictures gallery. Stored locally on device / gallery. Never uploaded. Optional (User-initiated)