File Studio Privacy Policy
We respect your privacy. This Policy explains how File Studio collects, uses, stores, shares, and protects information related to you. By using the app, you acknowledge this Policy.
Key commitment: File browse, edit, and management operations are performed locally on your device by default. We do not upload any of your file contents to our servers. The current release does not integrate ad SDKs, Firebase Analytics, Crashlytics, or other third-party analytics.
1. Introduction
This Policy applies to information processing when you use File Studio on Android. Mandatory law prevails if it conflicts with this Policy.
2. Information We Process
2.1 What We Do Not Collect or Upload
- File contents, folder structures, and edits on your device;
- Contacts, SMS, or call logs (not requested);
- Precise location (not requested);
- A location already stored in a photo file (EXIF): image details show it on the device only. It is not uploaded, and saving an edit does not write that location back into the new file;
- Advertising IDs or uploading your installed-apps list for ads or cross-app tracking (we do not perform such collection).
2.2 Locally Stored Information
The following information is stored on your device and is not uploaded to our servers:
| Type | Purpose | Storage |
|---|---|---|
| App settings | Theme, language, sort options | MMKV / SharedPreferences |
| Bookmarks & path history | Quick access | Local storage |
| Remote connection config | Host, port, username, password, and other settings you add for FTP, FTPS, SFTP, SMB, and WebDAV | MMKV (app-private, not additionally encrypted) |
| Editor recovery data | Large-file indexes, crash recovery | App-private directory |
| Root / Shizuku / custom su settings | Feature toggles and path preferences (all off by default) | Local storage |
| Subscription entitlement cache (Google flavor) | Whether a subscription is active, to unlock Premium features | MMKV (app-private) |
2.3 Subscriptions and Payments
Purchases are processed by Google Play Billing. Google may process account, order, and payment method information. We do not collect card numbers or full payment details.
We may receive de-identified subscription status (e.g., active or expired) to unlock premium features, and may cache that status locally (see 2.2).
2.4 Technical Logs and Analytics
Current release does not integrate Firebase Analytics, Crashlytics, ad SDKs (such as AdMob or AppLovin), or similar third-party analytics. We do not send personally identifiable information for ads or cross-app tracking.
Debug builds may log locally via Timber; release builds do not send such logs off-device.
If we add crash or analytics services later, we will update this Policy and Google Play Data safety declarations, and obtain consent where required.
2.5 Network Use
The app requests the Internet permission. The transfers below are started by you and stay between your device and a server or another device you choose. We do not intercept or store the contents, and we do not upload file contents to our servers.
- Remote client: you may connect with FTP, FTPS, SFTP, SMB, and WebDAV. SFTP and FTPS use SSH or TLS. FTP is cleartext. WebDAV encryption follows the http or https address you enter. SMB encryption depends on that connection's settings.
- On-device share: when you turn it on, the app may share a folder you choose on the local network over FTP, FTPS, SFTP (Android 8 and later), and WebDAV. SMB share is not offered. The on-device WebDAV share uses http. This runs as a foreground service and may show a notification.
- Nearby transfer: send or receive files with another File Studio device on the same local network. The transfer uses TLS (a self-signed certificate, a certificate fingerprint, and a PIN). The receiver accepts or declines each batch. This is not cleartext FTP.
- Google Play services and subscription verification.
The app's network security configuration permits cleartext so connections you configure, including FTP and http WebDAV, can be established. The app does not show an extra confirmation dialog before a public cleartext connection.
We do not sell your personal information.
2.6 Root / Shizuku / Custom su Advanced File Access (Optional)
The app offers an optional "advanced file access" feature, disabled by default, which you must turn on yourself in Settings. When enabled:
- The app may extract a local executable (a helper daemon) bundled in the install package to the app's private storage, then run it via Root privileges already present on your device, or via a Shizuku service you have separately installed and authorized, to perform advanced file operations (such as accessing restricted directories or adjusting file ownership) that are not possible with normal permissions;
- The app also bundles the
servicecomponent of the third-party library libsu (present asmain.jarin the install package), used to help start and manage the Root service above; it is not downloaded over the network and contains no signing-key material; - You may also point Settings at an su executable that is already on the device (custom su). That option is off by default and cannot be on at the same time as the Magisk/SuperSU option. The app does not supply that executable;
- This local process does not automatically collect, upload, or transmit your file contents; its read/write scope follows only the specific actions you initiate in the app;
- This feature relies on Root access already present on your device, or on the Shizuku app you install yourself and authorize; we do not bundle, provide, or help you obtain Root access;
- To call Shizuku, the package declares
moe.shizuku.manager.permission.API_V23. That permission is defined by Shizuku and is used to connect to a service you have authorized. It is not used while this feature stays off.
See the in-app Permission Description, "Root / Shizuku / custom su (Optional)" section, for details.
3. Permissions
| Permission | Purpose | Required |
|---|---|---|
| All files access (MANAGE_EXTERNAL_STORAGE) | Browse, manage, and edit files and folders (Android 11 and later) | Required for core features; prominent disclosure on first launch |
| Read/write external storage (READ_EXTERNAL_STORAGE / WRITE_EXTERNAL_STORAGE) | Declared on Android 12L (API 32) and below. Runtime permission for file management on Android 6.0–10; granted at install on Android 5.x. On Android 11–12L, file management uses all-files access. Not declared from Android 13 | Needed for file management on those versions |
| Internet | Remote client (FTP, FTPS, SFTP, SMB, WebDAV), on-device share, nearby transfer, and Google Play services | For related features |
| Network state (ACCESS_NETWORK_STATE) | Checks whether the device is online, and whether the connection is Wi-Fi or Ethernet, for nearby transfer, on-device share, and remote connections | Normal permission; granted at install |
| Wi-Fi state (ACCESS_WIFI_STATE) | Reads the current Wi-Fi connection state for local addresses and device discovery on the same network | Normal permission; granted at install |
| Wi-Fi multicast (CHANGE_WIFI_MULTICAST_STATE) | Holds a multicast lock while on-device LAN discovery, and nearby-transfer send and receive, look for nearby devices | Normal permission; granted at install |
| In-app billing (com.android.vending.BILLING) | Declared only on the Google Play build, to query subscription status with Google Play. Payment is handled by Google Play. The app does not collect card numbers. Other distributions do not declare it | Google Play build only; granted at install |
| Query all packages | In-app app list and APK analysis; the installed-apps list is processed only on-device and is not uploaded. The app does not install apps silently | For related features |
| Request install packages | Calls the system installer only after you confirm an APK install or update. No silent install | On user action |
| Usage access (PACKAGE_USAGE_STATS) | The "long unused" list in APK analysis. Queried on-device only and not uploaded. If access is denied or no last-used time is available, that list is sorted by app update time | Optional; you may decline |
| Foreground service / connected-device FGS / media-playback FGS | On-device share (FTP, FTPS, SFTP, WebDAV), nearby transfer, audio playback, and similar long-running features. Audio playback also uses a wake lock (WAKE_LOCK) so the processor can stay running during playback | When you enable those features |
| Camera | Google Play builds do not request Camera. Nearby-transfer QR scanning uses Google Play services Code Scanner; only the decoded text is returned to the app. Other distributions may request Camera only after you tap Scan QR and confirm an in-app disclosure; frames are processed on-device and are not saved or uploaded. You can type the address instead. | Optional; only if you choose to scan |
| Notifications (POST_NOTIFICATIONS) | Foreground-service and media notifications | When required by the system; you may disable in system settings |
| Vibrate | Haptic feedback | Non-sensitive |
| Shizuku API (moe.shizuku.manager.permission.API_V23) | Used only when you turn on advanced file access and Shizuku is installed and authorized on the device, to connect to that service. The permission is defined by Shizuku | Optional; unused by default |
See the in-app Permission Description. On Android 11 and later, some directories need a separate grant through the system document picker. On Android 14 and later, without Root, directories such as Android/data may be inaccessible.
4. Purposes of Use
- Provide and maintain the file-management features you choose to use (product updates are based on releases, not remote behavioral analytics);
- Verify subscription entitlements;
- Store preferences and connection configs;
- Keep on-device features running safely;
- Legal compliance.
5. Legal Basis for Processing
Where the EU GDPR or equivalent laws apply, our legal bases typically include:
- Contract: providing the file-management and subscription features you request;
- Legitimate interests: keeping on-device features running safely, balanced against your rights;
- Consent: system permissions you grant and optional features you enable (for example on-device share, nearby transfer, or Root/Shizuku/custom su);
- Legal obligation: compliance with applicable law.
Because processing is primarily on-device, we generally do not transmit your file contents or personal identifiers to our own servers.
6. Sharing and Disclosure
We do not sell personal information. We may share when:
- You give explicit consent;
- Required by law;
- Necessary to protect rights, safety, or security;
- Google processes data for Play Billing / Play services under its policies.
7. Third-Party Privacy Policies
The following third parties may process information in connection with their services. Please review their policies:
- Google Privacy Policy: https://policies.google.com/privacy
- Google Play / payments: Google Payments Privacy Notice; see also Google Play Help (subscriptions)
- Shizuku (optional helper app you install yourself): https://shizuku.rikka.app/
- libsu (on-device Root service bridge, open source): https://github.com/topjohnwu/libsu
This release does not include AdMob, Firebase Analytics, Crashlytics, AppLovin, or similar ad/analytics SDKs.
8. Retention and Security
- Local data remains until you clear app data or uninstall;
- Android system backup is disabled (
allowBackup=false); preferences, bookmarks, and remote connection configs are not included in device backups; - Data is kept in app-private storage; we use reasonable safeguards, but no method is 100% secure;
- Remote connection credentials (host, port, username, and password) in local MMKV are not additionally encrypted; avoid saving sensitive credentials on untrusted devices;
- The network security configuration permits cleartext. FTP and http WebDAV (including the on-device WebDAV share) may be sent in cleartext. SFTP and FTPS use SSH or TLS. SMB encryption depends on that connection's settings. Nearby transfer uses TLS. The app does not show an extra confirmation dialog before a public cleartext connection;
- Subscription records follow Google Play retention.
9. Your Rights
Depending on applicable law, you may have rights to access, copy, delete, withdraw consent, and complain to regulators.
- Clear data: Settings → Apps → File Studio → Clear storage (or uninstall);
- Revoke storage, notification, or other permissions in system settings (affects related features);
- Manage subscriptions via Google Play or in-app "Manage subscription";
- Contact: jingyouxingqu@gmail.com
In the EEA/UK you may also have rights to portability, restriction, and objection where applicable.
9.1 How to Exercise Your Rights
Email the privacy contact below with enough detail for us to understand and verify your request. We will respond within a reasonable time. Where CCPA or similar laws apply, we aim to respond to verifiable requests within 45 days (or notify you if an extension is permitted).
9.2 California Residents (CCPA)
If you are a California resident and CCPA applies: we do not sell personal information; you may request information about categories of personal information collected and request deletion of personal information we hold (local data can be cleared by clearing app data / uninstalling; payment data handled by Google Play must be managed through Google); we will not discriminate against you for exercising these rights. Send requests to the privacy email below.
10. Children's Privacy
Not directed to children under 13. We do not knowingly collect their personal information. Users who have not reached the age of majority where they live should use the app with a guardian's consent and guidance. Contact us to request deletion.
11. International Transfers
Google services may process data globally. See Google's policies and safeguards.
12. Changes
We may update this Policy in-app and on our public page with a new effective or last-updated date. Material changes will be notified as required by law. Continued use after an update constitutes acceptance unless law requires otherwise.
13. Contact
- Company: Guangzhou Jingyou Xingqu Technology Co., Ltd.
- Privacy email: jingyouxingqu@gmail.com
- This document does not display a full registered address.