1. 私密文字零知識架構 (Zero-Knowledge for Descriptive Text)
所有輸入至 Wysem 的交易描述與備忘錄文字，在同步至雲端伺服器之前，皆已在您的本地瀏覽器中，使用由您帳戶憑證衍生的金鑰，透過 AES-GCM 演算法進行端到端加密。由於此程序完全在用戶端執行，任何網頁管理員、伺服器營運商或資料庫所有者，皆完全無法讀取、存取或解密您的私密描述文字。數值與分類欄位另行處理 — 請參閱第 2 條。
2. 雲端資料同步與架構隔離 (Cloud Synchronization & Infrastructure Isolation)
您的加密交易字串，連同低熵數值欄位（如交易金額、分類項目與帳戶支付媒介），將安全地同步並儲存於由我們基礎設施夥伴 Supabase 管理的遠端雲端資料庫中。所有資料存取皆受到伺服器端「資料列安全性（Row-Level Security, RLS）」協定的嚴密保護，強制與您獨一無二的經認證用戶識別碼（UID）進行比對。用戶之間完全隔離，任何帳戶皆絕對不可能查看、修改或干涉其他用戶的財務流水賬目。
3. 帳戶還原與變更電子郵件之限制聲明 (Account Recovery & Email Mutation Limitations)
由於您的加密金鑰是直接由您的唯一帳戶憑證衍生而來，若您在系統設定中修改您的登入電子郵件地址，本地加密金鑰將會隨之改變。變更電子郵件後，您的總資產淨值、支出分類、交易日期與支付方式仍可完全從雲端資料庫中正常還原與計算，但您歷史紀錄中的「交易項目描述」與「備忘錄名稱」將會永久轉為空白字串且無法復原。修改登入信箱即代表您明確同意此項隱私安全權衡條款。
4. Cookie 與運行記憶體快取配置 (Cookie & Memory Cache Configurations)
我們使用本地瀏覽器儲存空間（如 localStorage 與 JavaScript 運行時暫存記憶體 RAM）來安全地保存您的使用者介面偏好、語系動態切換、12/24小時制時間格式，以及 Supabase 登入工作階段安全代記（Session Tokens）。這些檔案完全受到網頁瀏覽器的沙盒機制保護，絕不與任何第三方廣告或追蹤網路共享。
5. 第三方外匯網路動態整合 (Third-Party Currency Network Integration)
當您登入時，本應用程式會自動向我們白名單列出的匯率服務商（ExchangeRate-API，網址 open.er-api.com）發出背景請求，以載入最新的全球匯率。此請求僅會傳輸您瀏覽器的標準 User-Agent 與 IP 地址；絕不會包含任何您的私密財務資訊、帳戶餘額或交易紀錄。
1. Zero-Knowledge for Descriptive Text
All personal transaction descriptions and memo notes entered into Wysem are encrypted locally inside your client browser using AES-GCM with a key derived from your account credentials, before being synchronized to our remote storage back-end. Because this process is executed entirely on the client side, no administrator, server operator, or database owner can read, access, or decrypt your private descriptive text. Numerical and categorical fields are handled separately — see §2.
2. Cloud Synchronization & Infrastructure Isolation
Your encrypted transaction parameters, alongside low-entropy numerical values (amounts, category classifications, and account payment methods), are synchronized and stored on remote cloud database servers managed by our infrastructure partner, Supabase. All data access paths are heavily guarded by server-side Row-Level Security (RLS) protocols matching your unique authenticated user identifier (UID). Users are permanently isolated, making it physically impossible for any account to view, alter, or interact with another user's financial ledger lines.
3. Account Recovery & Email Mutation Limitations
Because your encryption key is derived directly from your unique account credentials, modifying your profile email address inside your system settings will instantly shift your local encryption key. While your numerical balance totals, spending categories, dates, and payment tracks will recover perfectly upon an email modification, your historical transaction descriptions and memo notes will be rendered as blank text strings permanently. Modifying your login email constitutes an explicit agreement to this data isolation tradeoff.
4. Cookie & Memory Cache Configurations
We use localized browser storage (such as localStorage and JavaScript runtime RAM caches) to retain your user interface preferences, active language toggles, 12/24-hour time format settings, and secure Supabase login session tokens across device reloads. These files are strictly sandboxed by your web browser and are never shared with or tracking third-party advertising networks.
5. Third-Party Currency Network Integration
When you sign in, the application makes an automated background request to our whitelisted exchange rate provider (ExchangeRate-API at open.er-api.com) to load current global exchange rates. This request transmits only your browser's standard User-Agent and IP address; no private financial information, account balances, or transaction records are ever included.