返回隱私權政策中心 / Back to Privacy Policy Center
SyncBridge 隱私權政策
開發者／發布者：Jensen Chou（Jensen）
隱私問題聯絡信箱：jensen0915@gmail.com
本隱私權政策適用於 SyncBridge 的 Android 與 Windows 版本（以下合稱「本應用程式」）。 SyncBridge 用於在同一區域網路內，於 Windows 與 Android 裝置之間，以及 Windows 裝置之間、 Android 裝置之間，進行支援的檔案傳輸或同步操作。各平台提供的功能可能不同。
本政策說明本應用程式與開發者如何存取、使用、分享、保護、保存及刪除資料。
1. 資料存取與本機儲存
為提供配對與檔案傳輸功能，本應用程式可能在裝置本機儲存：
- 使用者設定的裝置名稱及隨機產生的裝置識別碼
- 已配對裝置的名稱、網路位址、驗證權杖及 TLS 憑證指紋
- 使用者選擇的目的地資料夾存取授權
- 傳輸狀態、同步快照、歷史紀錄及中斷續傳資訊
- 尚未完成傳輸的暫存檔案
上述資料主要保存在本應用程式的私有儲存空間，用於辨識與配對裝置、安全驗證、執行傳輸、 顯示進度及中斷續傳。本應用程式不要求註冊帳號。
2. 使用者選擇的檔案與資料夾
Android 版使用系統的 Storage Access Framework，依使用者透過系統介面選擇的檔案、資料夾及
授予的存取權限處理內容；Android 版不使用 MANAGE_EXTERNAL_STORAGE 權限。
Windows 版以一般使用者權限執行，依使用者在應用程式中的選擇與設定，讀取來源檔案或資料夾， 並將接收的檔案寫入指定目的地。Windows 版不使用 Android 的 Storage Access Framework， 其檔案存取受 Windows 帳戶及檔案系統權限管理。
執行使用者要求或已設定的傳輸與同步工作時，所需的檔案內容、檔名、大小、修改時間及完整性 雜湊等資料，會直接傳送至使用者核准的區域網路裝置。接收行為依接收端的核准及目的地設定處理； 使用者可依支援的功能設定受信任裝置的自動接受。
這些資料傳輸不是將檔案傳送給開發者。開發者不營運用來中轉或儲存這些檔案的雲端伺服器。
3. 資料使用方式
本應用程式僅在提供下列功能所需的範圍內使用資料：
- 尋找及辨識已配對的區域網路裝置
- 驗證連線與防止未配對裝置存取
- 執行使用者要求的檔案傳輸、同步與中斷續傳
- 顯示傳輸進度、狀態與歷史，並允許使用者取消
- 透過通知、前景服務及背景排程維持使用者要求的工作
本應用程式不含廣告、行銷追蹤或開發者自建分析服務。開發者不販售使用者資料，也不會將 使用者檔案提供給廣告商、資料仲介商或其他與傳輸無關的第三方。
4. 資料分享與裝置間傳輸
本應用程式依使用者主動操作或已設定的同步與傳輸規則，將必要資料直接提供給使用者核准的裝置。 配對的另一台裝置可能保存收到的檔案及其本機配對或傳輸紀錄；該裝置上的資料需由使用者 在該裝置另行管理與刪除。
除此必要傳輸及下方所述 Google Code Scanner 服務外，本應用程式不會將資料提供給無關第三方。 若法律要求開發者揭露其實際持有的資料，開發者可能依法處理；但開發者通常不會收到或持有 使用者傳輸的檔案。
5. 第三方服務：Google Code Scanner
本節所述 Google Code Scanner 僅用於 Android 版的配對掃碼功能。Windows 版不使用此服務。
本應用程式使用由 Google Play services／ML Kit 提供的 Google Code Scanner 掃描配對 QR Code， 因此本應用程式本身不直接要求相機權限。依 Google 文件，掃描影像在裝置上處理，Google 不會 儲存掃描影像或掃描結果。
本應用程式已啟用自動縮放功能。依 Google 文件，此功能可能收集不具辨識特定使用者或實體裝置 用途的動態掃描工作階段 ID、自動縮放事件的縮放等級變更，以及可能包含條碼的預測邊界座標， 用於診斷與使用情況分析。第三方服務的資料處理由 Google 的條款與政策規範。詳情請參閱 ML Kit 資料揭露說明 及 Google 隱私權政策。
6. 網路、通知與背景執行
本應用程式使用區域網路及必要的連線資訊，以辨識裝置、驗證連線及執行檔案傳輸或同步。
Android 版可能使用通知、前景服務及背景排程來維持使用者要求的工作、顯示進度及提供取消操作。 Windows 版在程式執行期間，可啟動本機 HTTPS 服務以處理配對及區域網路傳輸。可用的通知與 背景執行方式依平台及版本而異。
網路位址等連線資訊僅在完成上述功能所需的範圍內處理。
7. 資料安全
裝置間連線使用 HTTPS，並以 TLS 憑證指紋及配對權杖驗證裝置。配對資訊與權杖主要儲存在 本應用程式的私有儲存空間。這些措施旨在降低未經授權存取的風險，但任何電子儲存或傳輸方式 都無法保證絕對安全。使用者仍應只與信任的裝置配對，並使用受信任的區域網路。
8. 資料保存與刪除
本應用程式會在提供相關功能所需期間，於本機保存設定、裝置識別資訊、配對資料、驗證權杖、 傳輸歷史、成功時間摘要、同步快照、中斷續傳資訊及暫存檔案。實際保存項目依平台與功能而異。
解除配對用於撤銷相關裝置的信任與存取授權，不代表刪除所有傳輸歷史、應用程式資料或已接收的檔案。
Windows 版的「清除已結束紀錄」會清除歷史清單中的展示紀錄，不刪除實際檔案、不解除配對， 也不清除正在傳輸或等待續傳工作所需的資料。裝置的上次成功時間摘要會保留。
使用者可透過各平台提供的應用程式資料管理功能清除本機資料。解除安裝後是否仍保留部分設定或資料， 取決於平台、安裝方式及系統行為；不應將解除安裝視為保證刪除所有資料的方式。
已保存至使用者所選資料夾的檔案，須由使用者自行管理與刪除。配對的另一台裝置若已保存檔案或紀錄， 也須在該裝置另行刪除。
本應用程式沒有使用者帳號，因此沒有帳號刪除流程。
9. 兒童隱私
本應用程式不是專為兒童設計，開發者也不會刻意透過本應用程式蒐集兒童的個人資料。 若您認為兒童在未獲適當同意下向開發者提供了個人資料，請透過下方信箱聯絡開發者。
10. 政策變更
本政策可能因功能、法律要求或資料處理方式變更而更新。更新內容將公布於本頁，並修改頁面 頂端的最後更新日期。重大變更時，開發者會在合理可行的範圍內提供適當通知。
11. 聯絡方式
若您對本隱私權政策或資料處理方式有任何疑問，請聯絡：
開發者／發布者：Jensen Chou（Jensen）
電子郵件：jensen0915@gmail.com
SyncBridge Privacy Policy
Developer/Publisher: Jensen Chou (Jensen)
Privacy contact: jensen0915@gmail.com
This Privacy Policy applies to the Android and Windows versions of SyncBridge (collectively, the “App”). SyncBridge provides supported file-transfer or synchronization operations between Windows and Android devices, between Windows devices, and between Android devices on the same local network. Available features may differ by platform.
This policy explains how the App and the Developer access, use, share, secure, retain, and delete information.
1. Data Access and Local Storage
To provide pairing and file-transfer functions, the App may store the following on your device:
- Your chosen device name and a randomly generated device identifier
- Paired-device names, network addresses, authentication tokens, and TLS certificate fingerprints
- Access authorization for destination folders selected by you
- Transfer status, synchronization snapshots, history, and resume information
- Temporary files for transfers that have not yet completed
This information is stored primarily in the App's private storage and is used to identify and pair devices, authenticate connections, perform transfers, show progress, and resume interrupted transfers. The App does not require account registration.
2. Files and Folders You Select
The Android version uses the system Storage Access Framework to access content according to the files
and folders you select and the permissions you grant through the system interface. The Android version
does not use the MANAGE_EXTERNAL_STORAGE permission.
The Windows version runs with standard user permissions. Based on your selections and settings in the App, it reads source files or folders and writes received files to the designated destination. The Windows version does not use Android’s Storage Access Framework; file access is governed by Windows account and file-system permissions.
When performing transfers or synchronization tasks you request or configure, necessary information such as file contents, filenames, sizes, modification times, and integrity hashes is sent directly to local-network devices you approve. Receiving follows the receiving device’s approval and destination settings. Where supported, you may configure automatic acceptance for trusted devices.
These transfers do not send your files to the Developer. The Developer does not operate a cloud server that relays or stores these files.
3. How Data Is Used
The App uses information only as needed to:
- Discover and identify paired devices on the local network
- Authenticate connections and prevent access by unpaired devices
- Perform file transfers, synchronization, and transfer resumption requested by you
- Display transfer progress, status, and history and allow cancellation
- Use notifications, foreground services, and background scheduling to continue work requested by you
The App contains no advertising, marketing tracking, or Developer-operated analytics service. The Developer does not sell user data or provide user files to advertisers, data brokers, or unrelated parties.
4. Data Sharing and Device-to-Device Transfers
The App sends necessary information directly to approved devices based on actions you initiate or synchronization and transfer settings you configure. The other paired device may retain received files and its own local pairing or transfer records. You must manage and delete that information separately on that device.
Apart from these necessary transfers and the Google Code Scanner service described below, the App does not provide information to unrelated third parties. If legally required, the Developer may disclose information actually in the Developer's possession; however, the Developer ordinarily does not receive or possess files transferred by users.
5. Third-Party Service: Google Code Scanner
Google Code Scanner described in this section is used only by the Android version for scanning pairing QR codes. The Windows version does not use this service.
The App uses Google Code Scanner, provided through Google Play services/ML Kit, to scan pairing QR codes. The App therefore does not directly request camera permission. According to Google, scan images are processed on the device, and Google does not store the scan images or scan results.
The App enables auto-zoom. According to Google, this feature may collect a dynamically generated scanning session ID not intended to identify a particular user or physical device, zoom-level changes for auto-zoom events, and predicted bounding-box coordinates that may contain a barcode. Google uses this data for diagnostics and usage analytics. Google's terms and policies govern this third-party processing. See the ML Kit data disclosure guidance and Google Privacy Policy.
6. Network, Notifications, and Background Operation
The App uses the local network and necessary connection information to identify devices, authenticate connections, and perform file transfers or synchronization.
The Android version may use notifications, foreground services, and background scheduling to continue requested tasks, display progress, and provide cancellation controls. While running, the Windows version may operate a local HTTPS service for pairing and local-network transfers. Available notification and background-operation features vary by platform and version.
Connection information, such as network addresses, is processed only as needed for these functions.
7. Data Security
Device connections use HTTPS. The App authenticates devices using TLS certificate fingerprints and pairing tokens. Pairing information and tokens are stored primarily in the App's private storage. These safeguards are intended to reduce unauthorized access, but no electronic storage or transmission method can guarantee absolute security. Pair only with devices you trust and use a trusted local network.
8. Data Retention and Deletion
The App retains local settings, device identifiers, pairing information, authentication tokens, transfer history, successful-transfer summaries, synchronization snapshots, resume information, and temporary files for as long as needed to provide the related functions. The information retained varies by platform and feature.
Unpairing revokes the relevant device’s trust and access authorization. It does not mean that all transfer history, application data, or previously received files are deleted.
In the Windows version, clearing finished history removes records from the displayed history. It does not delete actual files, unpair devices, or remove information needed by active transfers or tasks awaiting resumption. Device summaries showing the most recent successful operation are retained.
You may clear local data using the application-data management options available on your platform. Whether some settings or data remain after uninstallation depends on the platform, installation method, and system behavior. Uninstallation should not be treated as a guarantee that all data has been deleted.
You must manage and delete files saved to your selected folders yourself. Files or records retained on another paired device must be deleted separately on that device.
The App has no user accounts, so there is no account-deletion process.
9. Children's Privacy
The App is not designed specifically for children, and the Developer does not knowingly collect children's personal information through the App. If you believe a child has provided personal information to the Developer without appropriate consent, contact the Developer at the address below.
10. Changes to This Policy
This policy may be updated when the App's features, legal requirements, or data practices change. Updates will be posted on this page, and the “Last updated” date above will be revised. For material changes, the Developer will provide appropriate notice where reasonably practicable.
11. Contact
If you have questions about this privacy policy or the App's data practices, contact:
Developer/Publisher: Jensen Chou (Jensen)
Email: jensen0915@gmail.com