1. Introduction
This Privacy Policy applies to the File Manager mobile application ("Application", "App", "Service"), developed by Mohan RKS ("Developer", "We", "Us", "Our"). We respect your privacy and are committed to protecting it through compliance with this policy. This policy describes the types of information we may collect from you or that you may provide when you download, install, register with, access, or use the Application, and our practices for collecting, using, maintaining, protecting, and disclosing that information.
Please read this policy carefully to understand our policies and practices regarding your information and how we will treat it. If you do not agree with our policies and practices, your choice is not to download, install, or use this Application. By downloading, installing, or using this Application, you agree to this Privacy Policy.
2. Data Handling Architecture & Local Storage Policy
File Manager is primarily designed as an offline-first tool dedicated to local storage management, file browsing, archivity, media playback, document editing, and biometric file security. The core features of the Application operate locally on your client device.
- Local File Data: All file indexing, directory metadata creation, thumbnail generation, media rendering, archive manipulation (ZIP, TAR, RAR, 7Z), and code editing occur locally on your device. We do not transfer, mirror, or back up your personal files, photos, videos, audio, or documents to external cloud servers operated by us.
- Biometric Credentials & Encryption: Secure folder authentication relies on Android System Biometric APIs (BiometricPrompt / FingerprintManager) and local cryptographic primitives. Your biometric data (fingerprints, facial metrics) is processed exclusively by your device's Secure Enclave / Trusted Execution Environment (TEE). We never access, store, or transmit your biometric identifiers.
- App Database: Local app state, tags, custom categorization, favorites, and settings are stored locally in a sandboxed SQLite database via SQLite3 / Drift engine on your device.
3. Device Permissions & Purpose Breakdown
To provide full file navigation and execution functionality, the Application requests runtime and system permissions. Below is a detailed account of how each permission is utilized:
- MANAGE_EXTERNAL_STORAGE / READ_EXTERNAL_STORAGE / WRITE_EXTERNAL_STORAGE: Granted to allow full file operations across shared device storage, including creating, renaming, deleting, copying, moving, archiving, and editing documents and media files.
- READ_MEDIA_IMAGES / READ_MEDIA_VIDEO / READ_MEDIA_AUDIO: Required on Android 13+ to filter, organize, render thumbnails, and play media files stored on your local device storage.
- CAMERA: Utilized solely if you use the document scanner or built-in camera capture features within the Application to capture photos directly into specific target folders.
- USE_BIOMETRIC / USE_FINGERPRINT: Required to authenticate user identity before unlocking protected or hidden folders within the Application.
- QUERY_ALL_PACKAGES / REQUEST_DELETE_PACKAGES / PACKAGE_USAGE_STATS: Used for app manager utilities, allowing you to view installed application storage usage, back up APK files, or trigger package uninstallation upon explicit request.
- ACCESS_FINE_LOCATION / ACCESS_COARSE_LOCATION / NEARBY_WIFI_DEVICES / ACCESS_WIFI_STATE / CHANGE_WIFI_STATE / CHANGE_NETWORK_STATE: Requested exclusively to enable high-speed direct peer-to-peer (P2P) file transfers over Wi-Fi Direct or local Wi-Fi Hotspot networks. Location services are required by the Android operating system to scan for nearby Wi-Fi devices. Location data is never recorded, stored, or transmitted to any server.
- POST_NOTIFICATIONS / FOREGROUND_SERVICE: Used to display persistent status updates during background operations, such as ongoing file transfers, batch compression/extraction, or storage cleanup tasks.
4. Third-Party Advertising & Analytical Data Collection
The Application integrates Google AdMob (provided by Google LLC) to serve advertisements. While we do not collect personal data directly, Google AdMob may collect and process certain telemetry data automatically via Google Mobile Ads SDK for ad personalization, analytics, reporting, and fraud prevention.
Types of Data Collected by Google AdMob:
- Device Identifiers: Advertising ID (e.g., Google AAID), IP address, hardware model, operating system version, and system language.
- App Usage & Performance Data: Ad interaction logs, impression metrics, click tracking, crash reports, and app diagnostics.
- Approximate Location Data: Non-precise location inferred from IP address for geo-targeted advertising.
For more detailed information regarding Google's data handling practices, please refer to:
5. User Data Protection & Global Regulatory Rights
Depending on your jurisdiction, you possess specific statutory rights regarding your personal information under applicable global privacy laws, including the European Union General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA/CPRA), the Brazilian General Data Protection Law (LGPD), and the Indian Digital Personal Data Protection Act (DPDP):
- Right of Access & Control: Because your file data remains exclusively on your local device, you maintain 100% control over your data. You can inspect, modify, export, or delete any file at any time directly through the Application or system file browser.
- Right to Opt-Out of Personalized Ads: You can reset or disable your Advertising ID at any time via your device settings (Go to Settings > Google > Ads > Delete Advertising ID or Opt out of Ads Personalization).
- Data Retention & Deletion: Uninstalling the Application permanently removes all sandboxed local database records, app caches, and stored configuration settings from your device. Files created in general shared storage remain under user control.
6. Children's Online Privacy Protection (COPPA / GDPR Compliance)
Our Application is not directed toward children under the age of 13 (or under 16 in certain European jurisdictions). We do not knowingly solicit or collect personal data from children. Google AdMob is configured to comply with COPPA and relevant child safety frameworks. If we learn that personal data of a minor has been collected without verifiable parental consent, we will take immediate steps to remove or restrict such information.
7. Data Security Safeguards
We enforce industry-standard security practices. Local application storage and database connections are secured using platform-standard access control sandboxing. Sensitive actions, such as access to protected storage vaults, require hardware-backed biometric verification. However, no electronic storage method or transmission over wireless networks is 100% secure; we urge users to maintain strong device passcodes and device encryption.
8. International Data Transfers
Since core app functions operate offline, no file content is transferred across borders by us. AdMob SDK telemetry data may be processed on servers located in the United States or other countries where Google operates infrastructure, subject to standard contractual clauses and rigorous global privacy frameworks.
9. Amendments & Policy Updates
We reserve the right to modify or update this Privacy Policy at any time. Any changes will be published directly on this page with an updated "Effective Date". We encourage users to review this policy periodically to stay informed about how we safeguard privacy.
10. Contact Us & Legal Inquiries
If you have any questions, concerns, or formal legal inquiries regarding this Privacy Policy or our privacy practices, please contact us at:
Developer: Mohan RKS
Official Support Email: Mohanrks26@gmail.com
GitHub Repository: Mohan2123.github.io