← MaxManager

Privacy policy

Effective 18 November 2026 · applies to the MaxManager app and its Magisk/KernelSU module, version v5.0 and later · also available بالعربية.

The short version. MaxManager shows no advertising, links no analytics or crash-reporting SDK, and contains no third-party tracker. It works with no network at all. There is exactly one optional signal, and it is off by default: you have to switch it on, read the exact bytes first, and you can delete what was sent with one tap.

1. Who runs this

MaxManager is an independent project published by nader295. The app is distributed through the project repositories — the app repository (PanditJi-9/Xx) and the documentation repository (nader295/MaxManager). There is no company, no advertising network and no data broker behind it.

Contact: the Telegram group t.me/MaxManagerChat (channel: t.me/GetMaxManager), or an issue on either repository.

2. What the app keeps on your device

Everything the app does is local by default. These are the things that are stored, and they stay in the app's own private storage or in a file you chose yourself:

  • Your settings and profiles — control values, per-app and per-game profiles, and your preferences.
  • Readings and history — thermal, battery, CPU/GPU and health readings the app has measured, so a screen can show a trend rather than a single sample.
  • Backups you create — see section 5. A backup is a file written where you told it to write.
  • Media you record — screenshots and screen recordings you start yourself, saved to your own storage.
  • One optional identifier — install.id, a random UUID created on this device, used only by the optional signal in section 3. It is never derived from your hardware, your Google account or your phone number.

Uninstalling the app, or clearing its data, removes all of the above from the device.

3. The one optional signal (community statistics)

The app can send one small record per day so the project can see roughly how many installs exist and on which hardware the app is actually being used. Three conditions must all be true before a single byte leaves the device:

  • you switched the consent on yourself (it is off by default), and
  • the project's signed configuration has collection enabled, and
  • the app is starting up — it is one attempt per boot, with no background service, no scheduler and no retry loop.

The record contains exactly these fields, and nothing else:

FieldWhat it is
p_installThe random UUID described above — not a hardware or account identifier.
p_countryA country code derived from your device's language setting.
p_versionThe app version string.
p_manufacturer, p_model, p_sdk, p_releaseThe device make, model, Android API level and Android version.
p_envWhich root environment is present, from a short fixed list, or none.
p_healthA capped summary of the health readings the app already measures on your device.

It contains no account, no advertising identifier, no location, no contact, no message, no file name and no installed-app list. The consent screen renders the exact bytes that would be sent, built by the same code that sends them — so you can read the record before deciding.

Withdrawing. Switching consent off stops all sending immediately. The same screen offers a one-tap forget action: it asks the server to delete the record for your identifier and then deletes the local install.id. Deleting the identifier means a later return to the app starts with a fresh, unrelated identity — the two periods cannot be joined.

4. The only other network calls the app can make

  • Signed configuration — an anonymous read of one small signed JSON document (revision, payload, signature). No identifier is sent, and the document is verified against its signature before it is used. If the project has no endpoint configured, no call is made at all.
  • Licence activation — only if you open the licence screen and submit a code yourself. It sends the code you typed; it is not called in the background.

The app does not check for updates in the background. Updates are files you download yourself from the project repositories; when you choose to install one, the app verifies the file's SHA-256 digest first.

5. Permissions this app asks for, and why

MaxManager is a control panel for a rooted device, so it needs access that an ordinary app does not. Each permission below is requested at the moment you use the related screen — not collected at install time — and the data behind it is processed on the device.

PermissionUsed forLeaves the device?
Root / Magisk / KernelSU (module)Reading and writing the kernel and system interfaces you control, through one audited path, with a read-back after every change.No
Write secure settings, modify system settingsChanging the settings you asked to change (animation scale, doze, notification policy, and similar).No
Usage access (PACKAGE_USAGE_STATS)Showing per-app usage and foreground state so a profile can follow the app you are actually using.No
Installed-app visibility (QUERY_ALL_PACKAGES)Listing your apps so you can attach a profile to one, and showing install details in diagnostics.No
Storage and mediaWriting screenshots, recordings, exports and backups where you choose; reading a file you pick.No
NotificationsShowing the status of a running control task or recording.No
Location (ACCESS_FINE_LOCATION)Only the Wi-Fi channel scan in the device lab: Android requires the permission to return channel numbers. The app does not request, compute or store a location.No
Wi-Fi and network stateReading link state, channel and band for diagnostics.No
Microphone (RECORD_AUDIO)Only if you start a screen recording with audio yourself; the system dialog asks you first. Never used in the background.No
Screen capture (MediaProjection)Recording a clip you start yourself. The system shows its own consent dialog every session.No
Contacts, call log, SMS (READ_CONTACTS, WRITE_CONTACTS, READ_CALL_LOG, WRITE_CALL_LOG, READ_SMS)Only the local backup feature: reading these categories into a backup file you asked for, and restoring them from a backup you made. Read-only for SMS — the app does not claim to be a messaging app. Nothing in this category is ever uploaded.No
Install packages (REQUEST_INSTALL_PACKAGES)Installing an app update or a module file that you chose to install.No
Boot completedLetting the system re-register a backup schedule you created, so the schedule survives a restart.No
Battery optimisation exemptionKeeping a control task you started from being killed mid-run. Requested by you, never silently.No
Bluetooth, vibration, flashlight, audio settingsThe toggles on your own device; no nearby-device data is collected.No

6. What the app never does

  • No advertising, no ad identifier, no advertising SDK.
  • No analytics or crash-reporting SDK — the release build links none, and there is no third-party tracking library to disable.
  • No selling, renting or sharing of personal data, because none is collected for that purpose.
  • No access to your contacts, messages, call log, media or app list for any reason other than the on-device feature you opened — never for transmission.
  • No silent background uploads: the only outbound calls are the two in section 4 and the opt-in record in section 3.

7. Retention and deletion

On-device data lives until you delete it, clear the app's data, or uninstall the app. For the optional signal, the sent record is kept on the project's server until you use the forget action in section 3, after which the row for your identifier is deleted and the local identifier is removed.

8. Children

MaxManager is a system tool for rooted devices and is not directed at children. It is not offered to anyone under the age required to consent to data processing in their country.

9. Changes to this policy

If a future version changes what leaves the device, this page changes first and the effective date above moves with it. The app's own release notes link here, and the page's history is public in the documentation repository.

10. Your rights

Because the only personal data the project can hold is the opt-in record in section 3, your rights — access, correction, deletion, objection — are exercised by the forget action on the consent screen, or by writing in the Telegram group. If a request needs a written answer, ask there and it will be answered there.

← Back to MaxManager · سياسة الخصوصية بالعربية