隱私權政策
生效及最後更新日期:2026 年 9 月 15 日
1. 適用範圍
本政策適用於「SnapStockKing|懶人倉庫王」(以下簡稱本 App),由 BLACKNIU Studio 提供。本政策說明目前版本如何處理帳號、倉庫、OCR、PDF 與 AI 相關資料。
2. 帳號與雲端倉庫資料
- 電子郵件與 Firebase 使用者 ID 由 Firebase Authentication 處理,用於建立帳號、登入及隔離每位使用者的資料。
- 密碼交由 Firebase Authentication 驗證,不會寫入本 App 的庫存資料庫。
- 品號、品名、數量、庫位、庫存門檻、交期與進出貨紀錄會儲存在該帳號的 Firebase Firestore 路徑,用於庫存管理、查詢、報表及操作紀錄。
- 這些帳號與倉庫資料會連結到該 Firebase 使用者 ID,但不會用於廣告或追蹤。
3. 裝置端 OCR、PDF 與本機設定
- 單據照片目前使用 Apple Vision 在裝置上辨識,不會把原始照片傳送到 Firebase 或 OpenAI。
- 庫存 PDF 在裝置上產生。分享或保存後的副本由使用者選擇的 App、檔案位置或服務管理。
- 使用者提供的 OpenAI API Key 存放於此裝置的系統鑰匙圈,不同步到 Firebase。
- AI 答案評價最多保留最近 200 筆問題、回答與評價於本機,不會由本 App 上傳。
4. OpenAI 資料分享與明確同意
OCR 雲端解析與 AI 倉庫顧問使用兩個獨立授權,預設皆為關閉。使用者可在 AI 設定中分別開啟或撤回。
- OCR 雲端解析:只有開啟「允許將 OCR 文字送到 OpenAI」後,辨識文字才會送到 OpenAI 做欄位結構化。未同意時只使用本機規則。
- AI 倉庫顧問:只有另行開啟顧問授權後,每次提問才會把問題、最近對話,以及相關品號、品名、數量、庫存門檻、交期與進出貨紀錄送到 OpenAI。
- 本 App 不會在顧問請求中附加 Firebase 使用者 ID、電子郵件或庫位,但使用者輸入的品名、問題或 OCR 文字本身仍可能包含個人或機密資訊。
5. 第三方服務與診斷資料
本 App 使用 Firebase Authentication、Firebase Firestore 與使用者自行提供憑證的 OpenAI API。這些服務會依各自的條款與隱私政策處理其收到的資料。第三方服務應提供與本政策及適用規範相同或相當的資料保護。
目前內含的 Firebase Authentication 與 Firestore SDK 隱私清單宣告會收集不連結到使用者身分的其他診斷資料,用於分析服務穩定性,不用於追蹤。
6. 保存、刪除與撤回
- 倉庫資料會保留到使用者刪除個別內容或永久刪除帳號。
- 永久刪除帳號會刪除 Firebase 中目前帳號的庫存、操作紀錄、使用者文件與登入帳號,並清除該帳號的 App 操作紀錄快取及本機 AI 評價。為保護帳號,Firebase 可能要求近期重新登入。
- 第三方服務的備份、安全紀錄或先前請求,依各服務當時的政策與適用法律處理。
- OpenAI API Key 可在 AI 設定中另行清除。App 無法刪除使用者已保存或分享至其他位置的 PDF。
- 裝置系統或 Firebase SDK 的暫存資料可能依系統及 SDK 生命週期保留在 App sandbox;刪除本 App 會移除其 App sandbox,裝置備份則由 Apple 系統設定管理。
7. 使用者權利與聯絡方式
使用者可在 App 內匯出庫存 PDF、關閉 AI 分享授權、清除 API Key,或在帳號管理永久刪除帳號與倉庫資料。若有存取、更正、刪除或其他資料權益需求,請寄信至 good1men1@gmail.com。
8. 安全、兒童隱私與政策變更
本 App 以 Firebase 帳號隔離、iOS Keychain、App sandbox 與資料最小化方式保護資料。任何網路服務都無法保證絕對安全,使用者也應妥善保管帳號及 API Key。
本 App 並非專為兒童設計。我們不會故意收集兒童的個人資料。若資料處理方式改變,我們會更新本政策、App Store 隱私資訊及最後更新日期,並在需要時重新取得使用者同意。
Privacy Policy
Effective and last updated: September 15, 2026
1. Scope
This policy applies to SnapStockKing, provided by BLACKNIU Studio. It describes how the current version handles account, warehouse, OCR, PDF, and AI-related data.
2. Account and cloud warehouse data
- Email addresses and Firebase user IDs are processed by Firebase Authentication to create accounts, sign users in, and separate each user's data.
- Passwords are verified by Firebase Authentication and are not written to the App's inventory database.
- Item codes, names, quantities, storage locations, inventory thresholds, lead times, and inbound or outbound records are stored under the account's Firebase Firestore path for inventory management, search, reports, and activity records.
- Account and warehouse data are linked to the Firebase user ID, but are not used for advertising or tracking.
3. On-device OCR, PDFs, and settings
- Receipt images are currently recognized on device with Apple Vision. Original images are not sent to Firebase or OpenAI.
- Inventory PDFs are created on device. Copies saved or shared by the user are managed by the selected app, file location, or service.
- The user's OpenAI API Key is kept in the device Keychain and is not synced to Firebase.
- Up to 200 recent AI feedback records, including the question, answer, and rating, remain on device and are not uploaded by the App.
4. OpenAI sharing and explicit consent
Cloud OCR parsing and the AI Warehouse Advisor have separate permissions, both off by default. Users can enable or revoke either permission in AI Settings.
- Cloud OCR parsing: Recognized text is sent to OpenAI for field structuring only after the user enables OCR sharing. Otherwise, the App uses local rules.
- AI Warehouse Advisor: After separate advisor consent, each question sends the prompt, recent conversation, and relevant item codes, names, quantities, thresholds, lead times, and activity records to OpenAI.
- The App does not add the Firebase user ID, email address, or storage locations to advisor requests. Item names, prompts, or OCR text entered by the user may still contain personal or confidential information.
5. Third-party services and diagnostics
The App uses Firebase Authentication, Firebase Firestore, and the OpenAI API with credentials supplied by the user. These providers process received data under their respective terms and privacy policies. Third-party services are expected to provide protection equivalent to this policy and applicable requirements.
The bundled Firebase Authentication and Firestore privacy manifests declare collection of other diagnostic data that is not linked to identity, for analytics and service reliability, and not for tracking.
6. Retention, deletion, and withdrawal
- Warehouse data remains until the user deletes individual content or permanently deletes the account.
- Permanent account deletion removes the current account's inventory, activity records, user document, and Firebase Authentication account, plus the App-managed activity cache and on-device AI feedback. Firebase may require a recent sign-in.
- Provider backups, security records, and requests already delivered are handled under the provider's current policy and applicable law.
- The OpenAI API Key can be removed separately in AI Settings. The App cannot delete PDFs already saved or shared elsewhere by the user.
- System or Firebase SDK cache data may remain in the App sandbox according to system and SDK lifecycles. Deleting the App removes its sandbox. Device backups are governed by Apple system settings.
7. User choices and contact
Users can export an inventory PDF, turn off AI sharing, clear the API Key, or permanently delete the account and warehouse data from Account Management. For access, correction, deletion, or other privacy requests, email good1men1@gmail.com.
8. Security, children, and changes
The App uses Firebase account separation, iOS Keychain, the App sandbox, and data minimization. No network service can guarantee absolute security, and users should protect their account and API Key.
The App is not designed specifically for children, and we do not knowingly collect children's personal data. If data practices change, we will update this policy, the App Store privacy information, and the update date, and request consent again when required.