Legal

Privacy Policy

This policy explains how WizeFiles processes information when you browse storage, connect providers, share or inspect files, run transfers and synchronization, manage installed apps, sign or verify Android packages, import APKM containers, or protect content in a vault.

Last updated: 10 August 2026Applies to WizeFiles for Android and this website

1. Product scope

WizeFiles is an Android file manager. It helps users browse, organize, search, transfer, synchronize, share, archive, inspect and protect files on their own devices and on storage services they choose to connect.

2. Information processed

Depending on the features you use, the app may process file names, paths, metadata, folder structure, thumbnails, media or document metadata, search-index records, duplicate signatures, operation state, preferences, saved storage definitions, installed-package details and vault-related data.

3. Local processing

Browsing state, search indexes, cleanup results, transfer history, sync definitions, settings and vault metadata are intended to remain on the device unless a feature explicitly exports or backs them up at the user's request.

4. Connected storage

When you add a cloud, NAS or server account, WizeFiles communicates with that provider to list and manage the files you request. Provider authentication and service use are also governed by the provider's own terms and privacy policy.

5. Credentials and tokens

Connection secrets, OAuth tokens and vault credentials are used only to provide the selected feature and are intended to use Android-protected facilities. WizeFiles does not require a WizeFiles internet account for ordinary file management.

6. Permissions

The app may request broad file access, media or document-tree access, network access, nearby Wi-Fi and Bluetooth access, notifications, foreground-service access, biometric authentication, package visibility, APK install or uninstall access, usage access, root or Shizuku capability. Nearby-device permissions are requested only when Nearby Transfer is used. Each permission supports a user-facing feature.

7. Transfers and synchronization

Transfer Center and folder synchronization retain operation state and history so jobs can pause, resume, retry or recover. A job may include source and destination paths, progress, timing, result status and error details. Users can remove saved jobs and sync definitions.

8. Search and cleanup

Indexed search and cleanup tools may scan selected storage, record searchable metadata and calculate file signatures to find duplicates. These results support on-device organization and cleanup; WizeFiles does not need to upload file contents to perform them.

9. Vault and sensitive files

Vault and app-lock features are designed to protect private content locally. Users remain responsible for passwords, device security, backups and any content they export, decrypt or share.

10. Viewers and temporary files

When required for safe viewing or provider compatibility, WizeFiles may copy a selected archive entry, e-book, saved web document or other file into a private temporary cache. Bounded viewers are read-only, remove session files after use, and block embedded network requests where their format uses web rendering. A user-activated external link can still be handed to another app.

11. Nearby Transfer

Nearby Transfer uses Google Play services Nearby Connections to discover WizeFiles devices and establish an encrypted direct connection. Selected file contents and names are sent only to the recipient accepted by the user and are not routed through a WizeFiles server. Google states that the Nearby Connections SDK may collect connection-performance metrics and device or app information according to the device's Google usage-and-diagnostics setting. See Google's Nearby Connections information.

12. PC access and local sharing

When you start local sharing, WizeFiles exposes only the folders selected in that sharing profile to authenticated clients on the verified local network. Browser, FTP or FTPS clients receive the data and operations you authorize. Sessions are revocable, credentials expire, and stopping the service invalidates them.

13. App Manager and APK backup

App Manager reads packages visible to the current Android profile. Its inventory remains in memory and package names are not sent to analytics. Backups contain APK files and package metadata only; they never include application data, accounts, preferences, databases or private files.

14. Android package signing, verification and import

WizeFiles may stage a selected APK, AAB, APKS, XAPK or APKM container, key material and generated output in private temporary storage when a provider does not offer direct random access. Signing passwords are used only in memory for the current operation and are not saved. Durable Transfer Center state may include provider paths, the selected alias, signature schemes and a public certificate fingerprint, but never passwords or private-key material. Signing always creates a new output: APK signing may also create a separate v4 .apk.idsig; APKS re-signs every contained APK while preserving bundletool toc.pb; XAPK re-signs every contained APK while preserving its manifest, expansion files and other non-APK payloads. APKM import does not sign packages: it verifies the source, preserves contained APK bytes and signatures, and creates open APKS metadata. WizeFiles verifies the completed output, never overwrites the source, and removes temporary or partial files after completion, cancellation or failure.

15. Retention and deletion

Settings, search indexes, job history, sync pairs, saved connections, nearby resume checkpoints, recycle-bin items and vault content remain until removed by the user, cleared by the app's controls or deleted when the application is uninstalled, subject to Android and the selected storage provider. Temporary viewer, share-cache and Android-package staging sessions are removed according to their bounded cleanup rules.

16. This website

This static website does not use analytics, advertising trackers or advertising cookies. It stores only the selected light or dark theme in browser local storage. Following a link to GitHub, Google documentation or email opens a separate service governed by that provider's privacy terms.

17. Security

WizeFiles aims to use safeguards appropriate to a file manager, including protected secrets, explicit permissions, two-sided nearby authentication, bounded parsers and biometric-aware access. No device, storage medium or transmission method can be guaranteed completely secure.

Return to WizeFiles

Review current features and the competitive comparison.

Back to website