Legal Agreement

Privacy Policy

A clear explanation of how DevUtils Mobile manages local permissions and preserves your absolute privacy.

Last Updated: June 2026
Version: v2.1.2

1. Offline Philosophy & No Collection

DevUtils Mobile operates entirely offline. We do not run external collection analytics, telemetry scripts, or background servers. Your data is 100% yours and never leaves your phone.

DevUtils Mobile (the "Application"), identified by the package name com.amiraliliaqat.devutils, is designed and built by Amir Ali Liaqat. The Application is built as a offline-first utility toolkit. All tools operate entirely offline, processing data locally on your device.

We do not collect, store, upload, or transmit any user data, clipboard contents, scanned barcodes, configuration parameters, or locations to external servers. Your developer telemetry and raw payloads remain strictly on your own hardware.

2. Native Permissions & Data Usage

To deliver native utilities, the Application requests permissions to access certain native features. The information requested is retained on your device and is not collected by us in any way:

Camera Access

Used to scan QR codes and barcodes. Visual frames are processed dynamically in local memory to extract code values and are immediately discarded. We never snap photos or upload files.

Location Services

Used in the Map and GPS inspector tool. Displays live coordinates, speed, and heading. Local lookup is performed for reverse geocoding. This data is not shared.

Contacts (Address Book)

Used to show contact parameters locally or create contacts backup JSON files. The backup JSON files are saved to the application's secure cache directory and are not uploaded.

Clipboard Monitor

Used to show your history list and enable 1-click copies of generated JSON, password hashes, and units. Data stays localized in SQLite/AsyncStorage memory.

3. Service Providers & Network Connections

The Application contains network-dependent tools (like the SEO Inspector and YouTube Fetcher). When using these tools, the Application makes HTTPS requests directly to the respective target services (e.g., target websites, YouTube API). These connections are direct from your device; no intermediary proxy or logging server is used.

4. Sandbox & Local Security

We value your trust in providing us access to native device components, thus we strive to use commercially acceptable means of protecting it. Since all operations occur offline and locally on your sandbox environment, your risk is minimized compared to cloud-based alternatives.

5. Changes to This Privacy Policy

We may update our Privacy Policy from time to time. Thus, you are advised to review this page periodically for any changes. We will notify you of any changes by posting the new Privacy Policy on this page.

6. Contact Us & Support

If you have any questions or suggestions about our Privacy Policy, do not hesitate to contact us:

Developer
Amir Ali Liaqat
Support Email
GitHub Account
LinkedIn Profile