nurupoga
  • FileSync
  • Privacy
  • Terms
日本語 English

FileSync Privacy Policy

Last updated: November 12, 2026

Summary: FileSync does not use advertising or tracking. File transfers go directly to your chosen service, and credentials are used to authenticate those connections. Credentials use OS secure storage; metadata, settings, and history are also stored in app-private storage. The App does not automatically send diagnostic information externally. Section 2.2 describes local logs and manual sharing.

Governing Language: This Privacy Policy has been prepared in Japanese as the original and governing version. The English translation is provided solely for convenience and reference. In the event of any discrepancy, ambiguity, or conflict between the Japanese original and this English translation, the Japanese version shall prevail in all respects.

1. Introduction

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.

2. Information Handled

2.1 Information not collected for advertising or tracking

The following are not collected for advertising or tracking:

  • Personally identifiable information (name, address, phone number, email address, etc.)
  • The contents of files you operate on
  • Location data
  • Advertising identifiers (IDFA / GAID)
  • Usage history or behavioral analytics for advertising purposes

The App does not use third-party analytics platforms for advertising or behavioral tracking purposes (Google Analytics, Firebase Analytics, Amplitude, etc.).

2.2 Crash Reports and Diagnostic Logs

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.

2.3 Information stored on your device

The following information is stored on your device. Necessary credentials are sent to your chosen service when connecting. Local diagnostic logs are described above.

  • OAuth access tokens / refresh tokens for each cloud service
  • Connection details and credentials (username, password, SSH key) for WebDAV / SFTP / FTP
  • Temporary cache of file listings (metadata)
  • Sync settings, view preferences, and favorites
  • History of backup and transfer jobs, and local diagnostic logs

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.

2.4 Information transmitted externally by user action

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.

2.5 Google API data and Limited Use

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.

3. Third-Party Services

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.

  • Google Drive (Google LLC Privacy Policy)
  • Dropbox (Dropbox Privacy Policy)
  • pCloud (pCloud Privacy Policy)
  • WebDAV / SFTP / FTP servers (any server you specify)

Data handling at these services is governed by each provider's privacy policy.

4. OS Permissions

The following permissions support these features. Request timing depends on the OS, app initialization, and feature settings:

  • Photo library: for automatic photo/video backup
  • Local network: for WebDAV / SFTP / FTP server connections
  • Face ID / Touch ID / biometrics: for the app lock
  • File sharing / document browser: for file import/export
  • Background processing: to perform background transfers when permitted by the OS; continuous transfer after the app is closed is not guaranteed
  • External storage (Android): to access USB / SD card content

5. Cookies and Tracking

The App does not use cookies. None of the following are present:

  • Collection of advertising identifiers (IDFA / GAID)
  • Cross-site or cross-app tracking
  • Connections to third-party ad networks
  • Tracking subject to App Tracking Transparency (ATT)

6. Security

  • Credentials and tokens use OS secure storage
  • Encryption depends on the connection type and settings. HTTPS and SFTP are encrypted; plain FTP and HTTP connections are not. Choose an encrypted connection for sensitive information
  • The app supports a biometric app lock (Face ID / Touch ID / fingerprint)
  • SFTP supports public-key authentication

7. Children's Privacy

The App does not knowingly collect personal information from children under 13.

8. International Data Transfers

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.

9. GDPR / CCPA

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.

10. Data Deletion

10.1 Credentials and connection settings

  • Deleting a saved connection removes its saved connection record and connection-specific credentials. Closing a connection or leaving a screen is not the same as deleting it.
  • For Google, removing a connection does not necessarily sign out the Google SDK or remove its retained authorization. Credentials may remain in iOS Keychain after uninstalling. Revoke FileSync access in your Google Account third-party connections settings to withdraw Google authorization.
  • You can also revoke app access in the service's authorization settings

10.2 Files already uploaded

Delete them directly from each cloud / server's management UI or official app. The App also supports delete operations.

10.3 On-device retention

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.

11. Changes to This Policy

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.

12. Contact

For privacy-related questions, please file an issue on the App's GitHub repository.

  • Contact: GitHub Issues
  • Operator: FileSync development team (independent developer)

13. Summary

FileSync is built on the principles of "local-first" and "privacy by design":

  • Credentials authenticate your chosen connections
  • File contents do not pass through the developer's servers
  • Credentials are protected in secure storage on the device
  • Data is not sold
  • No ads or tracking

FileSync / Terms of Service

© nurupoga