Terms & Conditions
and Privacy Policy

Summary

ADBTweaks connects to Android devices over Wireless ADB. It can read device information and, when you approve an action, change settings, display behavior, game configuration, ART compilation state, memory state, or installed-app state.

Terms & Conditions

1. Acceptance

By installing or using ADBTweaks, you agree to these Terms & Conditions and the Privacy Policy below. If you do not agree, do not use the application.

2. Authorized use

You may use ADBTweaks only with devices that you own or control, or for which you have clear permission from the owner or administrator. You are responsible for complying with local laws, workplace rules, device policies, and carrier or manufacturer restrictions.

3. Device changes

ADB commands can change device state. Depending on the action, ADBTweaks may:

• Read device properties, display metrics, package lists, temperature, memory, storage, and other diagnostic values.
• Change Android settings, display resolution, refresh behavior, game overlay configuration, or other supported system values.
• Compile or reset ART/Dex state for one app, third-party packages, or system packages when you explicitly enable that scope.
• Ask Android to release cached and background processes. Apps may reload afterward.
• Disable packages or request a user-scoped uninstall. Protected packages may be rejected by Android.
• Apply experimental or vendor-specific commands that may have no effect or may behave differently across devices and firmware versions.

4. Warnings and responsibility

Changes can affect battery life, heat, app behavior, storage use, performance, stability, connectivity, or access to device features. ADBTweaks does not guarantee that a tweak will work, improve performance, increase FPS, or remain supported after an Android or vendor update.

You are responsible for reviewing the selected package, mode, scope, and warning before confirming an operation. Do not use system-wide compilation or package removal without a specific reason and a recovery plan.

5. No bypass of Android protections

ADBTweaks does not promise to bypass Android security protections, permissions, package safeguards, thermal limits, carrier policies, or manufacturer restrictions. Actions that require Wireless ADB or developer access require the normal device authorization.

6. Backups and restoration

Where supported, ADBTweaks captures baselines and offers restore actions. Baselines may be unavailable, incomplete, changed by another tool, or invalid after a device reset or system update. Restoration is not a substitute for a complete device backup.

7. Third-party services and content

The application may use public online resources for optional package recommendations and may check for updates through Google Play mechanisms. External websites, YouTube, GitHub, Google Play, device manufacturers, and other third parties have their own terms and privacy policies.

8. Availability and changes

Features may change, be removed, or become unavailable because of Android, OEM firmware, Wireless ADB, package-manager, or library changes. We may update these terms when the application or its data practices change.

9. Disclaimer

ADBTweaks is provided "as is" and "as available" without warranties of any kind, to the fullest extent permitted by law. No guarantee is made regarding availability, accuracy, compatibility, security, fitness for a particular purpose, or uninterrupted operation.

10. Limitation of liability

To the fullest extent permitted by law, the developer is not responsible for loss of data, device instability, unavailable features, overheating, battery drain, app failure, package loss, or any direct, indirect, incidental, or consequential damage arising from use or inability to use ADBTweaks.

11. Acceptance storage

Your first-run acceptance is stored locally on the device. It can be reset by clearing the application data.

Privacy Policy

1. Scope

This Privacy Policy explains what ADBTweaks stores, what it can access, and when information leaves the device. The policy applies to the ADBTweaks Android application package com.mrp.adbt.

2. Information stored locally

ADBTweaks stores application data locally on the device where it is installed. Depending on the features you use, this may include:

• Wireless ADB pairing identities, saved device names, hosts, ports, and connection preferences.
• Captured tweak baselines, selected settings, game profiles, and local application preferences.
• Action history, failed-action details, crash reports, error reports, and diagnostic logs.
• Cached package recommendation data used by the optional debloat database.
• First-run terms acceptance, notification preferences, update preferences, and monitor settings.

3. Information accessed through ADB

After you authorize a Wireless ADB connection, the app can request information from the connected target device, including package names, package state, device properties, display values, memory, storage, temperature, and settings needed for a requested operation. This information is used to display results and execute the action you selected.

4. No account profiling or advertising

ADBTweaks does not require an account, does not sell personal information, and does not use the app's local logs to build advertising profiles. The app does not intentionally collect your contacts, messages, photos, files, microphone recordings, or precise location.

5. Network connections

The application may use network access for Wireless ADB transport, optional public package-database retrieval, update checks, and external links. The optional package database is read from a public GitHub resource; the application does not need to upload your device package list to retrieve it. Google Play and linked websites may process information under their own policies.

6. Sharing is user initiated

Captured logs, error reports, device information, and feedback are shared only when you choose a send or share action. Android's share or email application controls the destination. Attachments and report text may contain device properties, package names, command results, timestamps, and error details. Review the content before sending it.

7. Notifications and permissions

Notification permission is used for pairing-related notifications when you enable or request that feature. Internet and network permissions support ADB, public-resource retrieval, and update or external-link flows. Package visibility access supports app and package selection. Android still controls the final device authorization and permission boundaries.

8. Retention and deletion

Local data remains until you delete it or clear the app data. You can clear saved reports from Settings, forget saved devices from Settings, and remove other application data through Android system settings. Clearing app data also removes local acceptance state, preferences, baselines, profiles, and history.

9. Security

We use Android local storage and the Wireless ADB authorization model provided by the platform. No method of storage or transmission is guaranteed to be perfectly secure. Do not authorize unknown devices and do not share pairing credentials.

10. Children

ADBTweaks is a device administration and development tool and is not directed at children. Do not use it without the permission and supervision required by the device owner or administrator.

11. Policy updates

This Privacy Policy may be updated when features, third-party services, or data practices change. The date at the top of this document identifies the latest revision.

Contact

For project information and updates, visit @mister_p27official on YouTube. For support, use the feedback and problem-report tools available in ADBTweaks when provided.