Back to DebugPair

Privacy Policy

Last Updated: November 11, 2026

Privacy Policy

Application: DebugPair (com.briyoom.debugpair)
Developer: Yash Rayjada
Effective Date: November 11, 2026

Core Privacy Guarantee: DebugPair operates on a local-first, privacy-by-design architecture. DebugPair does NOT harvest, transmit, store, or sell personal files, ADB payloads, screen mirroring video frames, or command histories to external servers. All ADB communication occurs directly between your devices over your own local network.

1. Introduction

Welcome to DebugPair ("Application", "we", "us", or "our"), operated by Yash Rayjada. DebugPair is a wireless Android Debug Bridge (ADB) utility, remote control, and device diagnostics toolkit designed to help developers, system administrators, and Android power users manage and debug Android devices over a local Wi-Fi network without requiring a computer.

This Privacy Policy explains what information is collected, how it is handled, and what choices and rights you have when using DebugPair.

2. Data We Do NOT Collect or Transmit

To provide complete transparency, we explicitly declare that DebugPair does NOT:

  • Collect, upload, or inspect personal files: Any files browsed, transferred (pushed or pulled), edited, or uninstalled remain strictly within your local environment and target device.
  • Intercept or transmit keystrokes or text inputs: Keystrokes sent via the virtual keyboard or remote input features are transmitted directly over the authenticated local ADB socket connection to the target device and are never recorded or logged to any cloud server.
  • Record or broadcast screen mirror streams: Real-time screen mirroring (powered by local scrcpy server streams) renders directly on your display in real-time. Frames are never stored, cached remotely, or uploaded.
  • Share or sell your personal data: We do not sell, rent, monetize, or broker personal information to data brokers or advertising networks.

3. Information We Collect and How It Is Used

DebugPair collects only the minimal data strictly required to deliver app functionality, license authentication, and operational stability:

A. Local ADB Credentials and Keypairs

In accordance with the Android Open Source Project (AOSP) ADB protocol, DebugPair generates a cryptographically secure 2048-bit RSA keypair on your device to establish authenticated wireless ADB connections. This private key is stored exclusively within your device's sandboxed local application storage. It is never shared with, backed up to, or accessible by developer or any third party.

B. Diagnostic & Performance Telemetry (Firebase Analytics)

We utilize Google Firebase Analytics to measure anonymized user engagement, app stability, and navigation trends. This helps us identify usability hurdles, prioritize bug fixes, and optimize app performance. The collected data is strictly aggregated and anonymized:

  • Anonymized event identifiers (e.g., successful ADB pairing, command execution success/failure rate, screen navigations).
  • Device model, manufacturer, Android OS version, and language configuration.
  • Aggregated app interaction patterns (button taps, feature usage counts).

C. Crash Diagnostics (Firebase Crashlytics)

To maintain high application quality and resolve unforeseen crashes, DebugPair integrates Google Firebase Crashlytics. When an unexpected error occurs, Crashlytics captures:

  • Stack traces and error exception logs.
  • Device state indicators at the moment of the crash (operating system version, free storage, memory usage, device architecture).
  • Crash reports do not contain personal files, device serial numbers, or network passwords.

D. Subscriptions & In-App Purchases (Google Play Billing / RevenueCat)

When you purchase DebugPair Pro, transactions are processed directly and securely through the Google Play Store Billing API. DebugPair and YBR Digital do not process or store credit card numbers, banking information, or billing addresses. We utilize RevenueCat to securely validate purchase receipts and verify entitlement state (e.g., whether your Pro license is active).

4. Summary of Third-Party SDKs

Service Provider Purpose Data Processed Privacy Policy
Google Firebase Analytics App usage metrics & analytics Anonymized app events, device specifications, OS version Google Privacy Policy
Google Firebase Crashlytics Crash reporting & stability analysis Stack traces, exception logs, device state at crash time Firebase Privacy
RevenueCat In-app purchase validation & entitlements Anonymous App User ID, purchase receipt tokens, active Pro status RevenueCat Privacy
Google Play Services In-app updates, in-app reviews & billing Play account entitlement status, store update availability Google Play Terms

5. Android System Permissions and Why They Are Required

DebugPair requests specific Android permissions solely to perform its technical functions:

  • INTERNET & ACCESS_NETWORK_STATE: Required to establish local Wi-Fi TCP/IP socket connections to target ADB devices and verify network connectivity state.
  • CHANGE_WIFI_MULTICAST_STATE: Required to perform mDNS / ZeroConf network discovery for discovering Wireless Debugging devices automatically on your local area network (LAN).
  • VIBRATE: Required to provide tactile haptic feedback during remote control button presses, trackpad taps, and command confirmations.
  • FOREGROUND_SERVICE: Required to maintain uninterrupted live screen mirroring streams and persistent ADB background sessions when requested by the user.
  • READ_EXTERNAL_STORAGE / Storage Access Framework: Required only when you explicitly select a local file or APK to push to a connected device or save a screenshot to your gallery.

6. Security and Data Protection

We take administrative, technical, and cryptographic precautions to protect your data:

  • Local Sandboxing: ADB pairing credentials and private RSA keys are stored in private internal application storage protected by Android's application sandbox.
  • Direct Sockets: All ADB command execution, file pushes/pulls, and live mirroring stream packets travel directly over your local Wi-Fi network without relaying through third-party proxy servers.
  • Encrypted Transport: Any remote configuration or purchase validation requests use industry-standard HTTPS/TLS encryption.

7. Children's Privacy (COPPA / GDPR Compliance)

DebugPair is a technical developer tool intended for general audiences, developers, and technicians. The Application is not directed to children under the age of 13 (or under 16 in the European Economic Area). We do not knowingly collect personal information from children. If you believe that a child has provided us with personal information, please contact us immediately, and we will take prompt steps to delete such data.

8. Your Rights Under GDPR and CCPA/CPRA

Depending on your location, you may possess statutory rights regarding personal data, including:

  • Right to Access & Portability: You may request confirmation and details of data processed.
  • Right to Deletion / Erasure: You can wipe all local keys and cached data at any time by clearing the application storage via Android Settings or tapping "Reset ADB Keys" in the app.
  • Right to Opt-Out: You can disable analytics tracking or disconnect the app from network access at any time.

9. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect modifications in our features, legal requirements, or operating practices. We will notify users of material changes by updating the "Last Updated" date at the top of this document and, where appropriate, displaying an in-app notice.

10. Contact Us

If you have any questions, feedback, or privacy-related inquiries regarding this Privacy Policy or DebugPair, please contact us at: