Privacy Policy

1. Introduction

Welcome to Prism File Explorer. We value your privacy and are committed to protecting your personal information. This privacy policy explains how we handle your data.

Summary: We do NOT collect, store, or share your personal files, photos, contacts, or account information. All file operations are performed locally on your device.

2. Data Collection and Usage

2.1 Personal Data

We do not collect personally identifiable information (PII) such as your name, email, phone number, or address. We do not have any external servers to store your user data.

2.2 Usage Data and Crash Reports (Firebase)

To improve app stability and fix bugs, we use Google Firebase Analytics and Firebase Crashlytics. These services may collect anonymous usage data and crash logs (e.g., device model, OS version, crash stack traces). This data helps us identify and fix technical issues.

2.3 Installed Applications List

To provide app management features in the "Apps" tab, this application needs to read the list of installed applications on your device.

Information Collected:

• Application name and package name
• Version number
• Install date and last update date
• Application size
• Requested permissions list
• Target and minimum SDK version
• Application category
• Whether it is a system app
• Application icon

Purpose of Use:

• Display installed applications list in the "Apps" tab
• Provide search and filter functionality
• Provide sorting functionality (by name, size, installation date)
• Display application details
• Suggest compatible apps when opening files ("Open With" feature)

Data Processing:

Important: Your installed applications list information is only read and displayed locally. It will not be uploaded to any server or third-party service. All data processing is completed locally on your device.

User Control:

• When you first access the "Apps" tab, a data disclosure dialog will be displayed
• You can choose to agree or decline
• After declining, you can return to the previous page
• You can reset the consent status at any time by clearing the app data

Permission Requirement:

This feature requires the QUERY_ALL_PACKAGES permission. According to Google Play policy, using this permission requires explicit user consent and transparent data usage disclosure.

3. Third-Party Services

This application integrates the following third-party services for technical support:

• Firebase Crashlytics & Analytics: Used solely for crash reporting and anonymous usage statistics.

We do not use third-party advertising services (like AdMob) or sell your data.

4. Changes to Privacy Policy

We may update this privacy policy from time to time. Changes will be posted on this page.

5. Contact Us

If you have any questions, please contact us at: flychatink@gmail.com

Permission Usage Documentation

1. General Description

This application requires specific permissions to perform its core function as a file manager and app manager.

2. Permissions List and Usage

File System and Storage Permissions

• android.permission.MANAGE_EXTERNAL_STORAGE: Grants the app write access to all files on external storage. Example: Essential for the core functionality of the file manager to browse, copy, move, delete, and manage files across the entire device.
• android.permission.WRITE_EXTERNAL_STORAGE: Write to external storage. Example: Save downloaded files, generate log files (Legacy).
• android.permission.READ_EXTERNAL_STORAGE: Read contents from external storage. Example: Display images or play audio files (Legacy).
• android.permission.MOUNT_UNMOUNT_FILESYSTEMS: Allows mounting and unmounting file systems (used for device management tools). Example: Backup files, manage external storage devices.
• android.permission.WRITE_MEDIA_STORAGE: Manage files in media storage. Example: Clear cache, manage photos and videos.
• android.permission.READ_MEDIA_STORAGE: Access media storage contents. Example: Read user albums, music, or video files.

Location Permissions

• android.permission.ACCESS_COARSE_LOCATION: Obtain approximate location. Purpose: Required to scan for local network (LAN) devices and identify Wi-Fi networks for SMB/Samba connections.
• android.permission.ACCESS_FINE_LOCATION: Obtain precise location. Purpose: Necessary on newer Android versions to perform local device discovery and display network information during LAN scanning.

Network and Connectivity Permissions

• android.permission.ACCESS_WIFI_STATE: Access Wi-Fi network status. Example: Check Wi-Fi connection for local file transfers.
• android.permission.INTERNET: Allow access to the internet. Example: Fetch online content or enable communication.
• android.permission.ACCESS_NETWORK_STATE: Access network connection status. Example: Check connectivity before making data requests.

System-Level Permissions

• android.permission.REQUEST_INSTALL_PACKAGES

  Purpose: Install APK packages.

  Example: Install applications directly from the file manager.

• android.permission.QUERY_ALL_PACKAGES

  Purpose: Read the list of installed applications and their metadata.

  Use Case: Display, search, and sort installed applications in the "Apps" tab. Also used to suggest compatible apps when opening files ("Open With" feature).

  Data Collected: Application name, package name, version number, install/update date, size, requested permissions, SDK versions, category, and system app status.

  Data Processing: All data is processed and displayed locally on the device only. No data is transmitted, uploaded, shared, or sent to any server, cloud service, or third party.

  User Consent: A comprehensive data disclosure dialog is displayed when first accessing the "Apps" tab, requiring explicit user consent before any data is read.

  Example: Core functionality for the "App Manager" feature to list and view application details.

• android.permission.FOREGROUND_SERVICE & FOREGROUND_SERVICE_DATA_SYNC

  Purpose: Run foreground services for data synchronization.

  Example: Prevent system interruption during long-running file operations like copying, moving, or compressing large files.

• android.permission.POST_NOTIFICATIONS

  Purpose: Show notifications.

  Example: Display progress of file operations (e.g., copying, Compressing).

3. Permission Declaration and User Awareness

Dynamic Permission Requests

Sensitive permissions will trigger runtime authorization dialogs, allowing users to grant or deny access.

Transparent Use of Permissions

The purposes of each permission will be disclosed in the privacy policy to ensure user awareness.

Impact of Permission Denial

Denying certain permissions may limit app functionality, such as:

• Denying location permissions disables LAN device discovery and SMB scanning features.
• Denying storage permissions limits file saving or loading.

Developer Information

• Email: flychatink@gmail.com
• Developer: BRILLIANT LEAD LLC