Privacy & Policy

Mostly local processing. Most diagnostics are processed locally on your device. The app does not require account sign-in, does not include a developer-owned analytics backend, and does not require a personal account system.

Device information access. The app accesses installed packages, hardware and OS signals, storage, memory, SIM state, Bluetooth state, Wi-Fi state, camera characteristics, and sensor readings only to render the feature screens you open, including Installed Apps, System Apps, All Apps, Hidden Apps, and the local App Security Audit.

Security audit scope. The App Security Audit is a local heuristic review of installer trust, launcher visibility, permission exposure, and selected package capabilities. It is not a cloud antivirus scan and does not guarantee malware detection.

AdMob placements. The app includes Google AdMob native ads in selected screens and occasional app-open ads after longer background inactivity. Ad requests may send device, app, and network metadata to Google or its advertising partners according to the Google Mobile Ads SDK behavior and Google policies.

Microphone test behavior. The microphone test records a short local sample only when you start the test. That sample is used for on-device playback, stays in app cache for the active test session, and is deleted when you leave the microphone test screen.

Crash logs. Crash logs are stored locally in app-private storage so you can inspect the latest failure report from Settings or the crash screen. They remain there until you clear them, clear app data, or uninstall the app.

Public IP lookup. The Public IP action sends a request to ipwho.is only when you tap that button. That request exposes your current network IP address and standard request metadata to that third-party service.

Package visibility justification. App inventory access is used to populate Installed Apps, System Apps, All Apps, Hidden Apps, package details screens, and the local App Security Audit. Without broad package visibility, those features would return partial results on modern Android.

No intentional sale or analytics profiling. The app does not intentionally sell data. External sharing is limited to explicit user actions such as opening links, sending email, opening the Play Store, opening the legal website, requesting public IP details, or loading Google-served ads.

Support and policy questions. For support or privacy questions, use the Contact page in this site or the Contact tab inside the app legal dialog.

Apps & Security tab. The app includes Installed Apps, System Apps, All Apps, Hidden Apps, package-details screens, and a local App Security Audit. Those features need broad package visibility to return the complete device inventory instead of a filtered subset.

Security audit. The security module performs a local heuristic review of installer trust, launcher visibility, risky permissions, and suspicious control surfaces such as accessibility, notification listener, VPN, overlay, and package-install capabilities.

Network and Bluetooth pages. Wi-Fi, transport state, and Bluetooth state are shown only when those screens are opened. The app does not maintain a background connection log or analytics stream.

Sensor and testing pages. Sensor values, microphone, vibration, flashlight, speaker, and button tests are user-facing diagnostics. They are initiated by direct user interaction and used for on-device verification.

Public IP button. External network access is limited and user-triggered. The public IP lookup is a deliberate button action, not a background sync.

Ad-supported surfaces. Selected screens can show compact native ads, and the app may show an app-open ad only after the app has stayed in the background long enough and after several foreground returns have already been skipped.

Crash logs. Only the latest captured crash report is stored. You can delete it from the Crash Logs screen at any time. It is also removed when app data is cleared or the app is uninstalled.

Microphone samples. Microphone loopback samples are temporary cache files used for the active test session. They are overwritten by a new recording and deleted when you leave the microphone test screen.

Device and package details. Most hardware, app-inventory, and sensor details are re-read from Android at runtime and are not persisted to a developer-owned server.