nurupoga
  • FileSync
  • Privacy
  • Terms
日本語 English

FileSync Privacy Policy

Last updated: June 15, 2026 / First published: May 3, 2026

Summary: FileSync does not use advertising or tracking, and does not send file contents or cloud credentials to the developer's servers. Credentials and metadata for cloud services are generally stored on your device (Apple Keychain / Android KeyStore). To improve quality and investigate failures, crash reports and diagnostic logs may be sent to Sentry. File contents, credentials, passwords, and access tokens are masked and are not intentionally sent.

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 the App does NOT collect

The App does not collect any of the following on any server:

  • 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 may use Sentry to send crash reports and diagnostic logs for quality improvement, bug investigation, and crash analysis. These reports may include error details, device / OS / app version, timestamps, stack traces, and technical state related to screens or features. File contents, cloud service credentials, passwords, access tokens, and SSH keys are masked by the App and are not intentionally sent.

2.3 Information stored only on your device

The following information is stored only on your device. It is never transmitted to the developer's servers.

  • 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

On iOS this information is stored in the Apple Keychain and the app's encrypted private storage; on Android, it is stored in the Android KeyStore and encrypted internal storage. The OS isolates this data per app.

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.

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 never sent to the developer's servers.

  • 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 App requests the following OS permissions only when you use the corresponding feature:

  • 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 continue transfers while the app is closed
  • 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 are stored in iOS Keychain / Android KeyStore, protected by the OS secure enclave
  • All network communications use encrypted protocols such as HTTPS / SSH / TLS
  • 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. Because the App does not collect any personal information at all, no information is recorded on the developer's side regardless of the user's age.

8. International Data Transfers

The App itself does not transmit data to the developer's servers. However, the cloud services you choose (e.g. Google Drive) may store data outside your country. See each service's privacy policy for details.

9. GDPR / CCPA

Because the App does not collect or store personal data on the developer's servers, the developer is generally not a "data controller" under GDPR or a "business" under CCPA. You can delete locally stored credentials by uninstalling the app or by using the disconnect option in the app's settings.

10. Data Deletion

10.1 Credentials and connection settings

  • Logging out / disconnecting in each service's screen removes the corresponding tokens from the device
  • Uninstalling the app removes all app data except Keychain / KeyStore items
  • Keychain / KeyStore items can also be removed from the OS 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.

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":

  • No credentials are sent to the developer's servers
  • File contents do not pass through the developer's servers
  • Credentials are encrypted in Keychain / KeyStore on the device
  • No data is sold or provided to third parties
  • No ads or tracking
Changelog
  • 2026-06-15: Added explanation of crash reports and diagnostic logs through Sentry
  • 2026-05-03: First published

FileSync / Terms of Service

© nurupoga