Namecard 隱私權政策 / Privacy Policy
Namecard（以下稱「本 App」）是一款在裝置本機執行的名片辨識與管理工具。本政策說明本 App 如何處理您的資料，同時適用於 iOS 與 Android 版本。
1. 摘要
- 本 App 不需要帳號，預設不會把您的任何資料傳送到我們的伺服器。
- 名片影像、辨識出的文字與您編輯的欄位，全部儲存在您的裝置本機。
- 本 App 沒有廣告、沒有第三方分析或追蹤 SDK。
- 刪除資料的方式：在 App 內刪除名片，或解除安裝 App。
2. 我們處理哪些資料、在哪裡處理
| 資料 | 來源 | 用途 | 儲存位置 | 是否離開裝置 |
|---|---|---|---|---|
| 名片影像（原圖與裁切圖） | 相機或相簿，由您選擇 | 文字辨識、顯示於名片詳情 | 裝置本機 | 否 |
| 辨識文字與解析欄位（姓名、公司、職稱、電話、傳真、Email、網站、地址、備註）與解析信心 | 由影像在裝置上辨識，或由您手動輸入 | 建立、搜尋、編輯名片 | 裝置本機資料庫 | 否 |
| 視覺風格偏好 | 您的選擇 | 記住主題 | 裝置本機 | 否 |
| 匯出檔（ZIP / VCF / CSV） | 您主動點選匯出 | 備份或分享 | 先寫入裝置暫存，再由您透過系統分享面板決定去處 | 由您決定 |
| 匯入的備份 ZIP | 您主動選擇的檔案 | 還原名片 | 裝置本機 | 否 |
2.1 相機與相簿
本 App 只在您點選「使用相機」或「選擇圖片」時存取相機或相簿，且只用於辨識您選擇的那張名片。本 App 不會在背景存取相機，也不會掃描或上傳您的整個相簿。
2.2 文字辨識（OCR）完全在裝置上進行
- iOS：優先使用 Apple 系統內建的 Vision 框架；若系統不支援該語言，改用 Google ML Kit 內建模型。
- Android：使用 Google ML Kit 內建的中文文字辨識模型；低品質影像會以拉丁文字模型重試。
辨識模型隨 App 一併安裝，辨識時不需要將影像上傳到任何伺服器。
2.3 通訊錄
只有在您按下「加入聯絡人」時，本 App 才會把該張名片的資料交給系統的「新增聯絡人」畫面（iOS）或系統聯絡人表單（Android），由您在系統畫面中確認後才會寫入；若 Android 裝置上沒有可用的聯絡人 App，本 App 會在您授予通訊錄權限後直接建立該筆聯絡人。本 App 不會讀取、比對或上傳您既有的聯絡人。
2.4 匯出與匯入
匯出的 ZIP（含 cards.json 與影像）、VCF 與 CSV 檔未加密，內容包含名片上的個人資料。檔案透過系統分享面板送出後，其去向與保管由您負責。請勿將備份檔分享給不信任的對象。
3. 第三方軟體開發套件（SDK）
本 App 使用 Google ML Kit 文字辨識 SDK 於裝置上執行 OCR。依據 Google ML Kit 服務條款，該 SDK 可能會向 Google 回報 API 使用量與效能指標（例如辨識耗時、錯誤率），這些指標不包含您的名片影像或辨識出的文字。詳情請參閱 https://developers.google.com/ml-kit/terms。
本 App 未整合任何廣告、分析、當機回報或社群 SDK。
4. 可選的雲端同步功能（目前正式版未啟用）
本 App 的程式碼包含一項可選的同步功能，需由開發者在建置時設定伺服器位址並由使用者主動登入才會作用。目前於 App Store 與 Google Play 發布的版本並未設定此功能，因此不會顯示登入畫面，也不會有任何名片資料傳送到我們的伺服器。
若未來版本啟用同步，我們會在啟用前更新本政策，並揭露：登入所需的 Email、上傳到伺服器的名片欄位與影像、伺服器所在地、資料保留期間，以及在 App 內刪除帳號與伺服器資料的方式。
5. 資料保留與刪除
- 名片資料保留在您的裝置上，直到您在 App 內刪除該張名片，或解除安裝本 App。
- 解除安裝本 App 會一併移除本機資料庫、影像與偏好設定。
- 若您啟用了作業系統的裝置備份（iCloud 備份或 Android 自動備份至 Google 雲端硬碟），系統可能會把本 App 的本機資料一併備份到您自己的帳戶；這由您的作業系統設定決定，我們無法存取這些備份。
- 您透過「加入聯絡人」寫入系統通訊錄的聯絡人，需在系統「聯絡人」App 中刪除。
- 您匯出並分享出去的檔案，需由您在存放位置自行刪除。
- 由於我們不持有您的任何資料，無需向我們提出刪除申請；若有疑問仍可來信聯絡。
6. 本機記錄
本 App 會在裝置記憶體中保留少量技術性執行記錄以協助除錯，記錄內容依程式設計不包含名片個資，且不會傳送給我們。
7. 兒童
本 App 並非針對 13 歲以下兒童設計，亦不會刻意蒐集兒童的個人資料。
8. 安全性
名片資料儲存在 App 的私有儲存空間，受作業系統的沙盒保護。我們建議您為裝置設定螢幕鎖，並妥善保管匯出的備份檔。
9. 您的權利
由於本 App 不會將您的資料傳送給我們，您對資料的存取、更正與刪除皆可直接在 App 內完成。若您對本政策有任何疑問，或認為本 App 的行為與本政策不符，請來信 jasonwu513@buildpolis.com，我們會在合理時間內回覆。
10. 政策變更
本政策若有修改，我們會更新本頁的生效日期；涉及資料處理方式的重大變更，會在 App 更新說明中提示。
11. 聯絡我們
築邦科技有限公司（buildPolis）
Email：jasonwu513@buildpolis.com
網站：https://www.buildpolis.com
Namecard (the "App") is an on-device business card scanner and organizer. This policy explains how the App handles your data. It applies to both the iOS and Android versions.
1. Summary
- The App does not require an account and, by default, does not send any of your data to our servers.
- Card images, recognized text and the fields you edit are all stored locally on your device.
- The App contains no ads and no third-party analytics or tracking SDKs.
- To delete your data, delete cards inside the App or uninstall the App.
2. What data is processed and where
| Data | Source | Purpose | Stored | Leaves the device? |
|---|---|---|---|---|
| Card images (original and cropped) | Camera or photo library, chosen by you | Text recognition, display on the card detail page | On device | No |
| Recognized text and parsed fields (name, company, title, phone, fax, email, website, address, notes) plus a confidence score | Recognized on device from the image, or typed by you | Create, search and edit cards | Local database on device | No |
| Visual style preference | Your choice | Remember the theme | On device | No |
| Export files (ZIP / VCF / CSV) | Created when you tap Export | Backup or sharing | Temporary folder, then the system share sheet where you choose the destination | Your choice |
| Imported backup ZIP | A file you pick | Restore cards | On device | No |
2.1 Camera and photo library
The App accesses the camera or photo library only when you tap "Use camera" or "Pick image", and only to recognize the card you selected. It never accesses the camera in the background and never scans or uploads your whole library.
2.2 Text recognition (OCR) runs entirely on device
- iOS: Apple's built-in Vision framework is used first; if the system does not support the language, the bundled Google ML Kit model is used instead.
- Android: the bundled Google ML Kit Chinese text-recognition model is used; low-quality images are retried with the Latin model.
The recognition models ship inside the App. No image is uploaded to any server for recognition.
2.3 Contacts
Only when you tap "Add to contacts" does the App hand that card's data to the system "New Contact" screen (iOS) or the system contact form (Android); nothing is written until you confirm there. If an Android device has no contacts app available, the App creates the contact directly after you grant the contacts permission. The App never reads, matches or uploads your existing contacts.
2.4 Export and import
Exported ZIP (cards.json plus images), VCF and CSV files are not encrypted and contain the personal data printed on the cards. Once a file leaves the App through the system share sheet, its destination and safekeeping are up to you. Do not share backups with parties you do not trust.
3. Third-party SDKs
The App uses the Google ML Kit text-recognition SDK to perform OCR on device. Under the Google ML Kit Terms of Service, the SDK may report API usage and performance metrics (for example recognition latency and error rates) to Google. These metrics do not include your card images or recognized text. See https://developers.google.com/ml-kit/terms.
The App integrates no advertising, analytics, crash-reporting or social SDKs.
4. Optional cloud sync (not enabled in the current release)
The App's code includes an optional sync feature that only works when the developer configures a server address at build time and the user signs in. The versions published on the App Store and Google Play are not configured with this feature: no sign-in screen is shown and no card data is sent to our servers.
If a future version enables sync, we will update this policy beforehand and disclose: the email used to sign in, which card fields and images are uploaded, where the server is located, how long data is retained, and how to delete the account and server data from inside the App.
5. Data retention and deletion
- Card data stays on your device until you delete the card in the App or uninstall the App.
- Uninstalling removes the local database, images and preferences.
- If you have enabled your operating system's device backup (iCloud Backup, or Android auto backup to Google Drive), the system may include the App's local data in a backup stored in your own account. This is controlled by your OS settings; we cannot access those backups.
- Contacts you added through "Add to contacts" belong to the system address book and must be deleted in the system Contacts app.
- Files you exported and shared must be deleted wherever you stored them.
- Because we hold none of your data, there is nothing to request from us; you are still welcome to email us with questions.
6. Local logs
The App keeps a small amount of technical run-time logging in device memory to aid debugging. By design these logs do not include card data and are never sent to us.
7. Children
The App is not directed at children under 13 and does not knowingly collect personal data from children.
8. Security
Card data lives in the App's private storage, protected by the operating system sandbox. We recommend using a device passcode and keeping exported backups in a safe place.
9. Your rights
Because the App does not send your data to us, you can access, correct and delete it directly in the App. If you have questions about this policy, or believe the App behaves differently from what is described here, email jasonwu513@buildpolis.com and we will respond within a reasonable time.
10. Changes to this policy
If we change this policy we will update the effective date on this page; material changes to data handling will be noted in the App's release notes.
11. Contact
ZHU BANG TECHNOLOGY LIMITED (buildPolis)
Email: jasonwu513@buildpolis.com
Website: https://www.buildpolis.com