SnapStockKing · 懶人倉庫王

隱私權政策

生效及最後更新日期:2026 年 9 月 15 日

重點摘要:本 App 使用 Firebase 提供帳號與倉庫同步;單據照片目前在裝置上辨識;OCR 文字與 AI 倉庫資料只有在使用者分別明確同意後才會傳送給 OpenAI。本 App 不販售資料、不顯示廣告,也不進行跨 App 或網站追蹤。

1. 適用範圍

本政策適用於「SnapStockKing|懶人倉庫王」(以下簡稱本 App),由 BLACKNIU Studio 提供。本政策說明目前版本如何處理帳號、倉庫、OCR、PDF 與 AI 相關資料。

2. 帳號與雲端倉庫資料

3. 裝置端 OCR、PDF 與本機設定

4. OpenAI 資料分享與明確同意

OCR 雲端解析與 AI 倉庫顧問使用兩個獨立授權,預設皆為關閉。使用者可在 AI 設定中分別開啟或撤回。

撤回同意會阻止後續傳送,但無法收回撤回前已送交 OpenAI 處理的請求。請勿在單據、品名或問題中提供非必要的個人或機密資訊。

5. 第三方服務與診斷資料

本 App 使用 Firebase Authentication、Firebase Firestore 與使用者自行提供憑證的 OpenAI API。這些服務會依各自的條款與隱私政策處理其收到的資料。第三方服務應提供與本政策及適用規範相同或相當的資料保護。

目前內含的 Firebase Authentication 與 Firestore SDK 隱私清單宣告會收集不連結到使用者身分的其他診斷資料,用於分析服務穩定性,不用於追蹤。

6. 保存、刪除與撤回

7. 使用者權利與聯絡方式

使用者可在 App 內匯出庫存 PDF、關閉 AI 分享授權、清除 API Key,或在帳號管理永久刪除帳號與倉庫資料。若有存取、更正、刪除或其他資料權益需求,請寄信至 good1men1@gmail.com

8. 安全、兒童隱私與政策變更

本 App 以 Firebase 帳號隔離、iOS Keychain、App sandbox 與資料最小化方式保護資料。任何網路服務都無法保證絕對安全,使用者也應妥善保管帳號及 API Key。

本 App 並非專為兒童設計。我們不會故意收集兒童的個人資料。若資料處理方式改變,我們會更新本政策、App Store 隱私資訊及最後更新日期,並在需要時重新取得使用者同意。

SnapStockKing

Privacy Policy

Effective and last updated: September 15, 2026

Summary: The App uses Firebase for accounts and warehouse syncing. Receipt images are currently recognized on device. OCR text and AI warehouse data are sent to OpenAI only after separate, explicit user consent. The App does not sell data, show ads, or track users across apps or websites.

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.
Revoking consent prevents future sharing but cannot recall requests already sent to OpenAI. Do not include unnecessary personal or confidential information in receipts, item names, or questions.

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.