ADB Nexus Privacy Policy

Last updated: August 28, 2026

ADB Nexus is an Android device-management utility operated by MetaCyberGuru. This policy explains
what the app processes, what leaves the phone running ADB Nexus, and the choices available to users.

Data processed locally

When you use ADB Nexus, the app may process connection addresses, authorized device information,
ADB command input and output, package details, local command history, selected files, network scan
results, and pairing information. This data is used to perform the action you requested.

The Host Apps feature can read the installed-app inventory on the phone running ADB Nexus only
after you accept its in-app disclosure. This can include app and package names, icons, versions,
install and update times, installer information, app type, APK metadata, permissions, components,
and signing-certificate fingerprints exposed by Android. Complete inventory uses Android’s
QUERY_ALL_PACKAGES access because installed-app analysis is a core device-management feature.
The inventory stays on the phone unless you deliberately use an Android sharing action.

The Host Data Usage feature opens only after you grant Android’s special Usage Access. It reads
Android’s local Wi-Fi and mobile accounting totals for the period you select. ADB Nexus resolves
those totals to app names and package names only when Host Apps access is also enabled. Usage
totals, app identities, and package identities from this screen are not sent to Firebase, GA4, or
advertising services by ADB Nexus.

ADB target-device content is processed locally. ADB Nexus does not intentionally upload commands,
pairing codes, target serial numbers, target IP addresses, package names, file names, file contents,
file paths, or target-device output to MetaCyberGuru, Firebase Analytics, or advertising services.
Pairing codes are not stored. The ADB host identity is protected in app-private no-backup storage
using a non-exportable Android Keystore key. Saved command history can be disabled or cleared in
Settings.

Data collected through Firebase

ADB Nexus uses selected Firebase services provided by Google. Share usage analytics, sanitized
crash reporting, performance diagnostics, and the Firestore installation registry are four
separate choices in Settings and are off by default. Google’s advertising consent does not enable
any of these choices.

• When you enable Share usage analytics, Firebase Analytics receives app interaction events, such as which app feature or screen was used,
  whether an operation succeeded, and coarse count or size ranges. Event parameters are designed to
  exclude target-device content and connection details.
• When you enable sanitized crash reporting, Firebase Crashlytics receives crash stack traces, app and operating-system versions, device model,
  app state, and identifiers generated by Firebase or Crashlytics. Handled error reports generated by
  ADB Nexus omit raw exception messages and include only a sanitized error type and app location.
• When you enable Share performance diagnostics, Firebase Performance Monitoring receives app
  lifecycle and named custom operation timing data. ADB Nexus does not enable Firebase’s automatic
  HTTP/S instrumentation, and custom traces exclude target addresses, commands, package names,
  paths, file names, pairing codes, and target-device output.
• Firebase Installations creates an identifier scoped to this app installation.
• When you enable Register this installation, Cloud Firestore receives the Firebase installation ID, this phone’s model, Android version, app
  version, and a last-seen timestamp. This supports abuse prevention, installation-level support,
  remote access suspension, and ad-free entitlements.
• Firebase Remote Config provides app settings such as maintenance notices, feature availability,
  minimum supported versions, review prompts, ads availability, and installation-level access rules.
• Firebase App Check sends integrity information used to protect backend services from unauthorized
  clients and abuse.

Remote Config, App Check, and Firebase Installations can operate for configuration, service
security, and installation-scoped access controls even when all four optional collection choices
remain off. ADB Nexus does not place Android ID or Advertising ID in its custom registry, analytics
events, Crashlytics reports, or shared support reports.

ADB Nexus reads Android ID only when you open the hidden diagnostics page and reads the host phone’s
Advertising ID locally to evaluate the optional ad_free_devices Remote Config list. Both values
are copyable in diagnostics for support. ADB Nexus custom code does not upload either value to its
Firestore registry, Analytics, Crashlytics, or support reports, and never reads identifiers from an
ADB-connected target for these controls. Firebase and Google SDKs can generate and process their own
app-scoped identifiers.

Advertising and consent

ADB Nexus may display ads through Google Mobile Ads. Depending on your device, region, consent
choices, and Google settings, the advertising SDK may process device or app identifiers, IP address,
approximate location inferred from IP address, app interactions, ad interactions, diagnostics, and
performance data to deliver, limit, secure, personalize, and measure advertising.

Where required, Google’s User Messaging Platform presents consent choices before ads are requested.
If privacy options are required in your region, you can reopen them from Settings under Ad privacy
choices. You can also manage ad personalization in Google’s My Ad Center.

Permissions

ADB Nexus requests only permissions needed for its visible features. Network and Wi-Fi permissions
support wireless ADB, discovery, and network tools. Location permission may be required by Android
for Wi-Fi scanning. Nearby-device access supports Bluetooth state where Android protects it.
Notification and foreground-service permissions keep active connections and transfers visible.
Usage Access supports the user-opened Host Data Usage screen. Installed-app visibility supports the
user-enabled Host Apps inventory. File selection uses Android’s system picker. Broad storage access and
MANAGE_EXTERNAL_STORAGE are not requested.

Permission-protected data used for ADB, file, and network operations remains on the phone unless you
explicitly transfer it to an authorized target device or another app through Android’s sharing tools.

Sharing and service providers

MetaCyberGuru does not sell or rent personal information. Data described above may be processed by
Google as a service provider for Firebase, Play Integrity, consent management, and advertising. Google
may also process advertising data under its own terms and privacy policy. Information may be disclosed
when required by law, to protect users and services, or during a business transfer subject to
appropriate safeguards.

Retention and deletion

Local app data remains until you clear it, uninstall the app, or Android removes the app’s storage.
Firebase and advertising data is retained according to Google’s service-specific retention controls.
Firestore installation-registry records are retained only while needed for app operation, abuse
prevention, support, or legal compliance.

You may request deletion of an ADB Nexus installation-registry record or support correspondence by
emailing info@metacyberguru.com. Include the Installation ID shown by tapping the version line three
times in ADB Nexus Settings. Do not include pairing codes, passwords, target-device output, or private
file paths. Uninstalling the app stops future collection from that installation but may not delete data
already retained by a service provider.

Security

Cloud communications use encrypted transport. Firebase services used by the app encrypt supported
data in transit and at rest. ADB Nexus restricts its Firestore client to writes that match a narrow
schema, denies client reads and deletes, and uses Firebase App Check as an additional abuse-control
layer. No security method can guarantee absolute protection.

Children

ADB Nexus is a technical device-administration tool and is not directed to children under 13. It is
not intended for use by anyone who cannot lawfully consent to the applicable data practices in their
region.

Your rights and choices

Depending on your location, you may have rights to request access, correction, deletion, restriction,
or objection concerning personal data. You can control Android permissions and Usage Access in system
settings, turn Host Apps access and each optional Firebase purpose on or off independently, clear local
command history in ADB Nexus Settings, use available ad privacy choices, or uninstall the app.

Changes

This policy may be updated when the app, legal requirements, or service-provider practices change.
The updated date will be revised when material changes are published.

Contact

MetaCyberGuru

Email: info@metacyberguru.com

Website: https://www.metacyberguru.com/