FileSync ("the App") treats user privacy as its highest priority. This Privacy Policy describes what information the App handles, and how. The App is a file manager that integrates Google Drive, Dropbox, WebDAV-compatible storage (Koofr, pCloud, and others), SFTP / FTP servers, USB storage, and on-device local storage in a single interface.
The following are not collected for advertising or tracking:
The App does not use third-party analytics platforms for advertising or behavioral tracking purposes (Google Analytics, Firebase Analytics, Amplitude, etc.).
The App does not automatically send crash reports, diagnostic logs, usage statistics, or performance information externally.
Diagnostic logs are also stored on the device. Exporting logs and automatically transmitting them are separate operations. If you manually share a log, review its contents and recipient first. Diagnostics and access logs collected independently by the OS or your chosen services follow their respective settings and policies.
The following information is stored on your device. Necessary credentials are sent to your chosen service when connecting. Local diagnostic logs are described above.
Credentials use iOS Keychain or Android secure storage. Metadata, settings, and history are also stored in databases and other app-private storage isolated by the OS; the App does not separately encrypt all such data.
When you use backup, upload, or transfer features, target files are sent to the destinations you specify (cloud storage services, WebDAV / SFTP / FTP servers, etc.). These are direct transmissions to services you have explicitly chosen; they do not pass through the developer's servers.
FileSync's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
FileSync accesses Google Drive data to provide the browsing, preview, backup and transfer features you choose. Transfers you initiate or configure can send selected data to your chosen storage destinations. Google-derived data is not sold or used for advertising or training general-purpose AI or machine-learning models.
For Google Drive connections, the App handles your Google account email and account identifiers to select and verify the intended account; file and folder names, IDs, sizes, types, modification times and revision metadata to browse and manage files; and file contents when you request previews, downloads or transfers. These data support the features you select, including operations on existing Drive files, rather than advertising or profiling.
Google-derived files may be sent to another cloud service or server only as part of a transfer or sync you initiate or configure. The destination provider receives those selected files under its own privacy policy. Google API connections use HTTPS; protection of a selected destination depends on its protocol, as described in section 6.
The App communicates under your account with the services you choose to connect. The developer only acts as a client; credentials are used to authenticate your chosen connections.
Data handling at these services is governed by each provider's privacy policy.
The following permissions support these features. Request timing depends on the OS, app initialization, and feature settings:
The App does not use cookies. None of the following are present:
The App does not knowingly collect personal information from children under 13.
File contents do not pass through the developer's servers. Your chosen services may store data outside your country. See each service's privacy policy for details.
For questions about data handling or deletion, please use the contact information below. Deletion of device credentials and uploaded files is described in the next section.
Delete them directly from each cloud / server's management UI or official app. The App also supports delete operations.
Saved account identifiers, connection settings, file metadata and transfer history are retained on the device to restore connections, show history and resume configured work. There is no single automatic expiry period for all these records. Use the App's applicable connection, history and cache deletion controls; clearing ordinary cache does not revoke authorization or necessarily delete every history or sync record. App-private data can also be removed by clearing app data or uninstalling, subject to OS behavior and the Keychain exception above.
Previews and transfers can create temporary local copies. The App attempts to remove owned preview files when the preview closes, but interruption or cleanup failure can leave temporary files until later removal by the App or OS. Files you explicitly download or export, and copies already transferred to other services, remain until you delete them in the selected location. Removing a FileSync connection does not delete those copies.
Material changes will be announced via in-app notification, App Store / Google Play release notes, and an update to the "Last updated" date on this page.
For privacy-related questions, please file an issue on the App's GitHub repository.
FileSync is built on the principles of "local-first" and "privacy by design":