隱私權政策Privacy Policy
「DuoPurse」(以下稱「本服務」)由 Spotx Studio(以下稱「我們」)提供,網址為 duopurse.spotx.studio。本政策說明我們蒐集哪些資料、如何使用、與誰分享,以及你可以如何管理自己的資料。
1. 我們蒐集的資料
- 帳號資料:Email、密碼(經雜湊處理,我們無法得知原文)。註冊時,我們會在你的裝置上計算密碼的雜湊值,只把前 5 個字元送到 Have I Been Pwned 比對是否曾在其他網站外洩;密碼本身不會傳出。若你選擇「使用 Google 繼續」登入,Google 會提供你的 Google 帳號 ID、Email、姓名與大頭貼網址(由 Supabase 保存);我們用帳號 ID 與 Email 建立並登入你的帳號,姓名作為你在帳本中的預設顯示名稱(可在設定中修改),大頭貼不會使用或顯示。使用 Google 登入不會讓我們存取你的 Gmail 或其他 Google 資料。若你選擇「使用 Apple 繼續」,Apple 會提供 Apple 帳號 ID、Email(你可選擇使用 Apple 的「隱藏我的 Email」轉寄地址)與(僅第一次登入時、經你同意)姓名;用途與 Google 登入相同。為了在你刪除帳號時依 Apple 規定撤銷授權,我們會在伺服器上保存 Apple 提供的更新權杖(refresh token),僅供撤銷之用,刪除帳號時一併刪除。
- 記帳資料:你或你的帳本成員輸入的帳本、帳戶、交易(金額、幣別、日期、分類、商家、備註)、預算、分類設定與匯率。你可以把自己新增的帳戶設為「私人」:帳本的其他成員就看不到這個帳戶、它的餘額、帳單和通知,只看得到上面算進共享預算的紀錄,以及與共享帳戶之間的轉帳(帳戶顯示為「{姓名} 的私人帳戶」,唯讀)。私人帳戶不會讓資料離開你的帳本,也不影響你與服務商之間的資料流向。
- 成員資料:你在帳本中設定的顯示名稱、角色,以及加入帳本的時間。
- 偏好設定:你選擇的語言與目前使用的帳本。
- Gmail 資料(僅在你主動授權時):若你選擇連結 Gmail 以自動匯入信用卡消費通知,我們會以唯讀方式搜尋符合條件的銀行刷卡通知信(依發卡銀行的寄件網域與主旨篩選),並儲存這些通知信的寄件者、主旨、內文與收信時間,用來擷取交易日期、金額、幣別、商家與卡號末四碼,顯示在「匯入紀錄」供你確認。我們不會讀取或儲存不符合條件的其他郵件。
- 轉寄的通知信(僅在你設定 Email 轉寄時):你在 Gmail 設定篩選器轉寄給我們的銀行通知信,我們會以同樣方式儲存與處理。你登記的 Gmail 地址會被保存,用來辨識信件屬於哪個帳本;設定過程中我們會寄一封測試信到這個地址。無法對應到帳本、或不是銀行通知的信會直接丟棄,不會儲存。
- 簡訊與 App 通知(僅在你設定 iOS 捷徑時):你在 iPhone 上用捷徑,把刷卡簡訊或 App 通知(Apple 錢包、支付 App、銀行 App、LINE 等)傳給我們。iOS 的通知觸發只能選整個 App,不能只選某個聊天室,所以選了 LINE,每則 LINE 訊息都會觸發捷徑。你選的 App 的通知會交給我們的伺服器(手機上不先篩選金額),由伺服器檢查,只有看起來像付款的才會儲存(通知標題、App 名稱或寄件者、內文與收到時間),其餘立即丟棄、不會被保存、不留紀錄。儲存的內容用來擷取日期、金額、商家與卡號末四碼,顯示在「匯入紀錄」供你確認。聊天內容若剛好含金額並帶有付款字眼,仍可能被誤判而儲存,你可以在「匯入紀錄」略過。你可以隨時在 iPhone 刪除捷徑,或在 App 內重新產生金鑰使舊的失效。
- 快速記一筆(iOS,僅在你使用控制中心、動作按鈕、Siri 或捷徑的「記一筆」時):你在系統跳出的視窗輸入的金額、分類、品項與選的帳戶,會從手機直接送到我們的伺服器,記成你帳本裡的一筆支出(和在 App 裡記的一樣),不經過 App 畫面。App 登入後會在手機的鑰匙圈存一把只供這支手機使用的金鑰(App 畫面看不到),用來確認是你;登出、離開帳本或刪除帳號時,金鑰會被撤銷。沒有網路時,這筆紀錄暫存在手機上(最多 100 筆),送出成功後即清除。
- Android App 的通知存取(僅在你於 Android 版 DuoPurse 開啟時):你同意並在系統設定開啟「通知存取」後,DuoPurse 會讀取手機上 App 所跳出的通知:預設是所有 App,你也可以改成只讀你在清單勾選的 App(銀行 App、錢包、「訊息」等)。我們不要求也不使用讀取簡訊的權限;銀行簡訊是「訊息」App 的通知,讀取所有 App 或勾選「訊息」時才會一併處理。讀到的通知先在你的手機上檢查,沒有金額的(聊天、驗證碼、活動)立即丟棄,不會離開手機;含金額的才送到我們的伺服器(讀取所有 App 時,這也包括購物或外送 App 的優惠通知),之後的處理、儲存與刪除和上面 iOS 捷徑的說明相同(伺服器再檢查一次,只儲存看起來像付款的,其他立即丟棄、不留紀錄)。手機上只留金鑰、讀取範圍(所有 App 或你勾選的 App 清單),以及 10 分鐘內重複通知的比對;等待網路時暫存的通知在送出成功後即清除。App 能看見手機上有桌面圖示的 App,只用來顯示勾選清單與標出通知來自哪個 App,不會把 App 清單送出手機。你可以隨時在系統設定關閉通知存取、在 App 內停用,或重新產生金鑰使舊的失效。
- 讓 AI 協助辨識通知(原「分享通知格式」;可在「設定 › 自動記帳」關閉):這個開關涵蓋兩件事。(1) 通知版型:你收到的簡訊、App 通知與轉寄的銀行通知,會先在伺服器上去除姓名、帳戶與帳本名稱、所有數字(金額、日期、卡號等)、商家、Email、網址與電話,只留下格式文字;同一種格式要在至少 3 本不同帳本都出現,才會留下它們逐字相同的部分作為版型樣本,不同的部分一律丟棄。樣本不含任何可對回你或你的帳本的資料,也不含經 Gmail 授權取得的內容。2026-11-02 起預設開啟(先前只有主動開啟的人才分享),App 內會通知一次;你可隨時關閉;關閉後不再收集新的版型,已留下的樣本因為不含個人內容,無法對回你而不會被刪除。(2) AI 讀取(需要你在 App 裡按「同意」才會開始;沒按「同意」之前,不會把任何通知內容送給 AI 服務):認不得或讀不出的付款通知(簡訊、App 通知,以及你轉寄的銀行與支付服務 email),伺服器會先遮掉卡號(只留末四碼)、帳號、電話、Email、網址、身分證字號,並把帳本成員的名字換成代號;email 另外遮掉稱呼與欄位裡的姓名(例如戶名、持卡人、收款人)、地址和客戶/會員編號,只送主旨、銀行或服務的名稱(不含寄件地址)和金額附近的段落,最多 1,500 字,再交給 AI 服務 Anthropic 讀出金額、日期與店名;讀出的結果記在該筆通知上。這些通知經遮蔽的文字(含金額、日期與商家)會送出;聊天訊息與經 Gmail 授權取得的信件永遠不送。同一種寫法讀過幾次後,會用這些遮蔽後的文字起草新的辨識規則,單一帳本的樣本也可以。AI 讀取的通知文字不經任何人工閱讀:開發者核准新規則時,這類通知只看比對結果(驗證了幾則、差異幾則、讀出哪些欄位),不看通知內容;但上述(1)中三本帳本合併的版型樣本,以及你自己送出的辨識問題回報,開發者在核准規則時仍可能看到。你可隨時關閉開關;關閉後不再送給 AI,這類通知改為存在匯入紀錄等你確認,再次開啟時會重新請你同意。
- 共享商家分類統計(功能開啟後預設加入,可在「設定 › 自動記帳」關閉「貢獻分類統計」):功能開啟後,你儲存一筆已看過的支出時,會記下「哪個品牌被你的帳本記在哪一類標準分類」,每個帳本對每個品牌只算一票,匯總成「多少個帳本這樣分類」的匿名計數,讓其他人也能得到常見分類的建議。公開的只有品牌、標準分類與帳本數量,不含使用者或帳本代碼、金額、日期、備註、通知原文;不含經 Gmail 授權取得的內容、轉帳、收入與「其他」分類。逐筆投票只存在伺服器端、不公開,並隨帳號刪除一併清除。你自己的分類習慣(哪個商家你記在哪個分類)只存在你自己的資料,只有你讀得到,不用於他人。
- 辨識問題回報(僅在你自己按下「回報」並確認送出時):你對一則讀錯的通知按「沒讀對」時,App 會顯示要送出的通知原文(不經遮蔽,可能含姓名、卡號末幾碼、金額與商家),你同意後才送出;你可以另外改正金額、日期、卡號末四碼與商家,這些改過的值只用來在我們的伺服器上驗證新的辨識規則,不會送給 AI。我們(開發者)會看這些回報,AI 服務 Anthropic 的模型會讀這段原文來起草辨識規則,修正後所有人的這類通知都能讀對;原文不會寫進程式碼,進入程式碼的測試只含去除姓名、數字與商家後的版本。回報的原文與截圖轉出的文字,保存到回報處理完 30 天後刪除。你也可以上傳最多 5 張通知的截圖:截圖不會在手機上遮蔽,圖上可能有姓名、卡號末幾碼和金額;圖片會重新產生(不含拍攝地點等資訊)再上傳,只私下保存,最長 30 天;我們用 Anthropic 的模型把截圖讀成文字(它只為了轉成文字而讀圖),這段文字依上述方式處理。經 Gmail 授權取得的通知不能回報。每人每天最多回報 5 則、截圖回報 3 次,30 天內最多 20 張截圖。
- 一般回報(設定 › 回報錯誤):你選擇類別(通知沒抓到、通知讀錯了、App 出錯、建議、其他)、寫下備註,並可附最多 5 張截圖(截圖在手機上重新產生、不含拍攝地點,圖上可能有個人內容,請避開姓名、卡號和密碼)。「App 出錯」「建議」「其他」的備註與截圖只有我們(開發者)會看,不會送給 Anthropic 或任何 AI 服務,也不會用來起草或修改辨識規則;只有類別為「通知沒抓到」「通知讀錯了」的回報,其截圖才依上一項處理。備註保存到回報處理完 30 天後(沒處理則 60 天)刪除,截圖最長 30 天;每人每天最多 5 則一般回報。
- 匯入帳單/其他記帳 App 的檔案(每次匯入你按「同意」才會送):帳單和匯出檔平常只在你的手機上用規則讀取。讀不出來,或你按「讀得不對,交給 AI 讀」時,App 會先說明並請你同意這一次匯入;同意後,帳單的文字(不是檔案本身)會先在手機上遮掉卡號(只留末四碼)、姓名、地址、身分證字號、帳號和電話,再送給 AI 服務 Anthropic 讀出每一筆明細;其他記帳 App 的檔案若沒有內建格式,只送欄位名稱和前 20 列(同樣先遮罩)來判斷欄位。我們的伺服器只轉送這段文字,不保存帳單或檔案的任何內容,紀錄只記次數與字數;每人每天最多 10 份。你按「不要」就不會送出任何內容。
- 使用紀錄:你在新手引導中走到哪一步(例如看過哪幾張功能介紹、打開或完成了哪個「開始使用」步驟)與時間,用來改善新使用者的設定流程。
- 技術資料:為維持服務運作,我們的託管服務商可能會記錄 IP 位址、瀏覽器類型與存取時間等基本日誌。
2. 資料的使用方式
- 提供登入、記帳、同步與帳本共享功能。
- 依你的授權,將信用卡通知自動轉換為交易紀錄,供你確認。
- 改善新手引導與設定流程。
- 維護服務安全、排除錯誤。
我們不會出售你的資料,也不會將資料用於廣告。
3. Google 使用者資料
本服務對於從 Google API 取得之資訊的使用與傳輸,將遵守 Google API 服務使用者資料政策,包括其中的「有限使用」(Limited Use)規定。具體而言:
- Google 使用者資料僅用於提供或改善使用者可見的記帳功能。
- 不會將 Google 使用者資料移轉給第三方,除非是為提供上述功能所必需、為遵守法律,或屬於合併、收購或資產出售的一部分並經你同意。
- 不會將 Google 使用者資料用於廣告投放,包括再行銷或個人化廣告。
- 不允許任何人閱讀你的 Google 使用者資料,除非經你明確同意、為安全目的(例如調查濫用)、為遵守法律,或資料已彙整並匿名化。
- 不會使用 Google 使用者資料訓練通用的人工智慧或機器學習模型。
4. 資料分享
你的記帳資料只會與你加入同一帳本的成員共享。為提供服務,我們使用以下服務商處理資料:
- Supabase:帳號驗證與資料庫儲存。
- Vercel:網站託管。
- Google:「使用 Google 繼續」登入,以及(若你授權)Gmail 唯讀存取。
- Apple:「使用 Apple 繼續」登入,以及刪除帳號時撤銷 Apple 授權。
- Make:接收你轉寄的銀行通知信並交給本服務處理,以及寄送 Email 轉寄設定用的測試信。信件在 Make 的執行紀錄中最長保留 30 天;處理失敗的信會暫存於 Make 等待重試,同樣最長 30 天,之後由 Make 自動刪除。
- Have I Been Pwned:註冊時比對密碼雜湊值的前 5 個字元,檢查密碼是否曾外洩。
- Anthropic:(僅在你於 App 裡按「同意」「讓 AI 協助辨識通知」之後,且開關未關閉時)為讀出認不得或讀不出的付款通知的金額、日期與店名,以及起草辨識規則,接收伺服器遮蔽後的通知文字(含轉寄的銀行與支付服務 email 的摘錄;卡號只留末四碼,去除帳號、電話、Email、網址、身分證字號與帳本成員名字;仍含金額、日期與商家)。聊天訊息與經 Gmail 授權取得的信件永遠不送。另外,開關開啟時,也接收已去除個人內容、且至少 3 本帳本都有的通知版型,不含通知原文(見第 1 節)。
- Anthropic:(僅在你自己於「設定 › 自動記帳」開啟「AI 分類建議」時,且只針對你的消費)為判斷一筆自動記帳的分類,接收商家名稱、金額、銀行分類、帳本的分類名稱,以及你過去確認過的「商家 → 分類」對照。(「分類說明」功能開啟後,另包含你自己的每個分類的一句說明,以及為寫這些說明而統計的你自己的常見商家名稱、店型與時段、金額區間的次數;每週最多一次,不含單筆金額、日期、通知原文、姓名、帳戶或帳號。)不含通知原文、姓名、帳戶或帳號,也不含經 Gmail 授權取得的內容。建議只供你一鍵套用,不會自動改動紀錄。
- Anthropic:(共享商家知識的「AI 辨識」功能開啟後,與任何人的設定無關)為辨識帳單上的新商家名稱是哪個品牌、什麼店型,接收「商家名稱」(只有名稱)與我們已認得的品牌名稱清單;不含金額、日期、通知原文、姓名、帳戶、帳號、使用者或帳本代碼,不含轉帳的收款人、經 Gmail 授權取得的內容,也不含只有一個帳本出現、看起來像個人姓名的名稱,且只送公開登記資料查不到的名稱。答案只當作「猜測」,不會自動合併紀錄,也不會讓分類變成確定。功能關閉時不會送出任何東西。
- Anthropic:(僅在你自己送出辨識問題回報時)讀取遮蔽後的回報文字來起草辨識規則;你上傳的截圖(可能含姓名、卡號末幾碼與金額)會交給它,只用來讀成文字。你填的正確值不會送出。
- Anthropic:(僅在你於匯入時按「同意」這一次匯入)為讀出帳單的每一筆明細,或判斷其他記帳 App 檔案的欄位,接收在你手機上遮蔽後的帳單文字(或欄位名稱與前 20 列):卡號只留末四碼,去除姓名、地址、身分證字號、帳號與電話;仍含日期、金額與商家。不送檔案本身,我們也不保存。
除上述情形或法律要求外,我們不會與任何第三方分享你的資料。
5. 資料安全
所有連線皆經 HTTPS 加密。資料庫採用列級安全(Row Level Security),每筆資料只有所屬帳本的成員能存取。存取憑證僅保存在伺服器端。
6. 資料保存與刪除
- 你可以隨時在 App 內刪除交易、帳戶與分類。
- 通知版型的候選在 60 天內若湊不滿 3 本帳本就刪除;版型樣本在用來撰寫測試後再保留 90 天,未使用的最長保留 1 年。
- 回報的截圖保存 30 天,或在回報處理完 7 天後刪除,以先到者為準;回報的遮蔽文字在處理完 90 天後刪除,最長保存 180 天。刪除帳號時你的回報一併刪除。
- 簡訊與 App 通知的原文在「匯入紀錄」等待處理時保留;你自己按「略過」時我們立即清除原文;若是系統自動略過、且通知上看得到金額,原文保留 7 天,只有你本人在「匯入紀錄 › 已略過」看得到,讓你能按「其實是交易」撈回來,之後清除;留給你決定的不確定通知最多保留 14 天;被合併或新增為紀錄後,原文再保留 14 天,讓你能從該筆紀錄按「這則沒讀對」回報,之後清除,只留下解析出的日期、金額、商家與卡號末四碼。這 14 天內只有你本人(回報時)和我們伺服器上的規則驗證(以你的回報值為準)讀取原文。
- 你可以隨時至 Google 帳戶權限頁面 撤銷本服務的 Google 存取權。撤銷後我們將停止讀取 Gmail。
- 你可以隨時在 App 的「設定 › 個人資料 › 刪除帳號」刪除帳號,刪除會立即生效:只有你一人的帳本會連同所有紀錄、帳戶與預算一起刪除;和其他人共用的帳本,你記的紀錄(仍顯示你當時的顯示名稱)、新增的共享帳戶與共用預算會留給其他成員,你的私人帳戶和上面的紀錄會刪除(算進共享預算的紀錄仍留在帳本裡,帳戶顯示為「{姓名}(已離開)」),你的個人預算、連結的 Gmail、Email 轉寄與捷徑金鑰、確認過的「商家 → 分類」對照、使用紀錄會刪除。詳細步驟與刪除範圍見刪除帳號與資料。
- 無法使用 App 時,也可以來信 gabriel@spotx.studio 要求刪除,我們會在 30 天內完成。
7. 兒童隱私
本服務不針對 13 歲以下兒童設計,我們不會在知情的情況下蒐集兒童的個人資料。
8. 政策更新
我們可能不定期更新本政策,更新後會修改本頁上方的生效日期。重大變更時,我們會在 App 內通知。
9. 聯絡我們
如有任何隱私相關問題,請來信 gabriel@spotx.studio。
DuoPurse (the "Service") is provided by Spotx Studio ("we", "us") at duopurse.spotx.studio. This policy explains what data we collect, how we use and share it, and how you can control it.
1. Information we collect
- Account information: your email address and password (stored hashed; we cannot see it). When you sign up, your device hashes the password and sends only the first 5 characters of the hash to Have I Been Pwned to check whether it has appeared in a data breach; the password itself never leaves your device. If you choose Continue with Google, Google provides your Google account ID, email address, name and profile picture URL (stored by Supabase); we use the account ID and email to create your account and sign you in, and your name as your default display name in the ledger (you can change it in Settings). The profile picture is not used or shown. Signing in with Google does not give us access to your Gmail or any other Google data. If you choose Continue with Apple, Apple provides your Apple account ID, email address (you may use Apple's Hide My Email relay address) and, on the first sign-in only and with your consent, your name; we use them the same way as for Google. So that we can revoke the authorization when you delete your account, as Apple requires, we keep the refresh token Apple issues on our server, used only for that revocation and deleted with your account.
- Ledger data: the ledgers, accounts, transactions (amount, currency, date, category, merchant, note), budgets, category settings and exchange rates that you or members of your shared ledger enter. You can mark an account you added as private: the other members of the ledger then cannot see that account, its balance, statements or notices, only its records that count toward a shared budget and transfers to or from a shared account (shown read-only, with the account as "{name}'s private account"). A private account changes nothing about which service providers receive data.
- Member data: the display name and role you have in each ledger, and when you joined it.
- Preferences: your chosen language and the ledger you are currently using.
- Gmail data (only if you choose to connect it): if you connect Gmail to import credit-card spending notifications, we search your mailbox read-only for matching bank notification emails (filtered by the card issuers' sending domains and subjects) and store their sender, subject, body and received time. We use them to extract the transaction date, amount, currency, merchant and the last four digits of the card, and show them in Imports for you to review. We do not read or store any other email.
- Forwarded notifications (only if you set up email forwarding): bank notification emails that your Gmail filter forwards to us are stored and processed the same way. We keep the Gmail address you register so we know which ledger a forwarded email belongs to, and send one test email to it during setup. Emails that match no ledger, or are not bank notifications, are discarded without being stored.
- Texts and app notifications (only if you set up an iOS Shortcut): a Shortcut on your iPhone sends us card texts or app notifications (Apple Wallet, payment apps, bank apps, LINE and so on). iOS can only trigger on a whole app, not on a single chat, so if you pick LINE, every LINE message runs the Shortcut. Notifications from the apps you pick are handed to our server (the phone does not filter by amount first); the server checks them and stores only what reads like a payment (notification title, app name or sender, text and time received) — everything else is discarded at once, never saved and not recorded. What is stored is used to extract the date, amount, merchant and last four card digits, shown in Imports for you to review. A chat message that happens to contain an amount and a payment-like word can still be stored by mistake; you can skip it in Imports. You can delete the Shortcut on your iPhone at any time, or generate a new key in the app to make the old one stop working.
- Quick add (iOS, only when you use the Add a record control, Action button, Siri or Shortcuts): the amount, category, item and account you enter in the system windows are sent from your phone straight to our server and recorded as an expense in your ledger, just like one entered in the app, without opening the app. After sign-in the app stores a key in the phone's Keychain for this phone only (the app's screens cannot read it) to confirm it is you; the key is revoked when you sign out, leave the ledger or delete your account. Without a connection the record waits on the phone (up to 100) and is removed once it has been sent.
- Notification access in the Android app (only if you turn it on in the Android version of DuoPurse): once you agree and switch on Notification access in the system settings, DuoPurse reads the notifications posted by the apps on your phone: all apps by default, or, if you choose, only the apps you tick in its list (bank apps, wallets, Messages and so on). We neither ask for nor use the permission to read text messages; a bank text is a notification of the Messages app and is handled only when all apps are read or you tick Messages. Each notification is checked on your phone first, and anything without an amount (chats, one-time codes, promotions) is discarded at once and never leaves the phone; only what has an amount is sent to our server (when all apps are read, this includes promotions with a price from shopping or delivery apps), where it is handled, stored and deleted as described above for the iOS Shortcut (the server checks again and stores only what reads like a payment; everything else is discarded at once and not recorded). The phone keeps only the key, the reading scope (all apps, or the list of apps you ticked) and a 10-minute comparison to skip repeated notifications; a notification waiting for a connection is removed once it has been sent. The app can see the apps on your phone that have a home-screen icon, only to show the list and to name the app a notification came from; the list of apps never leaves the phone. You can switch off Notification access in the system settings, turn the feature off in the app, or generate a new key to make the old one stop working at any time.
- Let AI help read notices (formerly "Share notice formats"; switch it off in Settings › Auto capture): This switch covers two things. (1) Notice formats: text messages, app notifications and forwarded bank emails you receive are first stripped on our server of names, account and ledger names, every number (amounts, dates, card digits…), the merchant, email addresses, links and phone numbers, leaving only the wording of the format. A format is kept as a sample only when it has shown up in at least 3 different ledgers, and then only the parts that are word-for-word the same; anything that differs is discarded. A sample contains nothing that can be traced back to you or your ledger, and nothing obtained through the Gmail connection. Since 2026-11-02 it is on by default (before, only people who turned it on shared), and the app tells you once; you can switch it off at any time; turning it off stops new formats from being collected, but samples already kept contain nothing that can be traced to you, so they are not removed. (2) AI reading (starts only after you tap Agree in the app; before you do, no notice content is sent to any AI service): for payment notices we cannot recognise or read (text messages, app notifications, and bank or payment-service emails you forward), our server first removes card numbers (keeping only the last four digits), account numbers, phone numbers, email addresses, links and national ID numbers, and replaces the names of ledger members with a placeholder; for an email it also removes names in the greeting and in fields such as account holder, cardholder or payee, addresses and customer or member numbers, and sends only the subject, the bank's or service's name (never the sender's address) and the passage around the amount, at most 1,500 characters, then hands the text to an AI service, Anthropic, to read the amount, date and shop; the result is stored on that notice. The masked text, which still contains the amount, date and merchant, is sent; chat messages and anything obtained through the Gmail connection are never sent. Once the same kind of wording has been read a few times, the masked text is used to draft new reading rules, and a sample from a single ledger is enough. No person reads the text of notices read by AI: when the developer approves a new rule they see only the match results (how many were checked, how many differed, which fields were read), never those notices; the 3-ledger format samples in (1) and reports you send yourself may still be seen by the developer when a rule is approved. You can switch it off at any time; once off, nothing more is sent to AI, such notices are kept in Import records for you to confirm, and turning it on again asks for your agreement again.
- Shared merchant category counts (once the feature is on, you take part by default; switch off "Contribute category counts" in Settings › Auto capture): once the feature is on, when you save an expense you have looked at, we note which canonical category your ledger filed a brand under. Each ledger counts once per brand, and the votes are totalled into anonymous counts of how many ledgers file a brand that way, so others can get a suggested category. Only the brand, the canonical category and a number of ledgers are public: no user or ledger ids, amounts, dates, notes or notice text, and nothing from Gmail-authorised content, transfers, income or the "Other" category. The individual votes stay on the server, are not public, and are deleted with your account. How you personally file merchants is kept in your own data, readable only by you, and is never used for anyone else.
- Reports of reading problems (only when you yourself tap Report and confirm): when you tap "Read wrong" on a notice, the app shows you the notice exactly as it will be sent — the original text, not masked, so it may show names, the last digits of a card, amounts and shops — and sends it only after you agree. You may correct the amount, date, card's last four digits and shop; only the values you changed are used, on our server, to check a new reading rule, and they are never sent to AI. We (the developers) look at these reports, and Anthropic's model reads the original text to draft a reading rule that fixes the format for everyone. The text is not written into our code; the tests that enter the code contain only a version with names, numbers and shops removed. A report's text, and text transcribed from a screenshot, is deleted 30 days after the report is handled. You may also upload up to 5 screenshots of a notice: screenshots are not masked on your phone, so they may show names, the last digits of a card and amounts; the images are re-created (without location or other photo data) before upload, kept privately for at most 30 days, and Anthropic's model reads them only to transcribe them into text, which is handled as described above. Notices obtained through a Gmail connection cannot be reported. At most 5 reports and 3 screenshot reports per person per day, and 20 screenshots in 30 days.
- General reports (Settings › Report a problem): you choose a category (notice not captured, notice misread, app error, suggestion, other), write a note and may attach up to 5 screenshots (re-created on your phone without location data; they may show personal content, so please leave out names, card numbers and passwords). The note and screenshots of an "App error", "Suggestion" or "Other" report are seen only by us (the developers); they are not sent to Anthropic or any AI service and are never used to draft or change reading rules. Only the screenshots of a "Notice not captured" or "Notice misread" report are handled as described in the previous item. A note is deleted 30 days after the report is handled (60 days if it is never handled), screenshots after 30 days at most; at most 5 general reports per person per day.
- Importing a statement or another bookkeeping app's file (sent only when you tap Agree, for that one import): statements and exports are normally read by rules on your phone only. When that fails, or when you tap "Read wrong? Let AI read it", the app explains and asks you to agree for that one import; after you agree, the text of the statement (not the file itself) first has card numbers (last four kept), names, addresses, ID numbers, account numbers and phone numbers hidden on your phone, then goes to the AI service Anthropic to read each line. For another app's file with no built-in format, only the column names and the first 20 rows (masked the same way) are sent to work out the columns. Our server only passes this text on and keeps none of the statement or file; its log records only counts and character totals; at most 10 documents per person per day. If you tap No, nothing is sent.
- Usage records: how far you get through onboarding (for example which introduction slides you saw and which Get Started steps you opened or finished) and when, used to improve setup for new users.
- Technical data: our hosting providers may log basic information such as IP address, browser type and access time to operate the Service.
2. How we use information
- To provide sign-in, bookkeeping, sync and ledger sharing.
- With your permission, to turn card notifications into draft transactions for you to review.
- To improve onboarding and setup.
- To keep the Service secure and fix problems.
We do not sell your data and do not use it for advertising.
3. Google user data
DuoPurse's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
- We use Google user data only to provide or improve user-facing bookkeeping features.
- We do not transfer Google user data to third parties except as necessary to provide those features, to comply with law, or as part of a merger, acquisition or sale of assets with your consent.
- We do not use Google user data for serving advertisements, including retargeting or personalized ads.
- We do not allow humans to read Google user data unless we have your affirmative consent, it is necessary for security purposes (such as investigating abuse), it is required by law, or the data is aggregated and anonymized.
- We do not use Google user data to develop, improve or train generalized AI or machine-learning models.
4. Sharing
Your ledger data is shared only with members of the same ledger. We use these service providers to run the Service:
- Supabase — authentication and database storage.
- Vercel — website hosting.
- Google — Continue with Google sign-in, and read-only Gmail access if you authorize it.
- Apple — Continue with Apple sign-in, and revoking the Apple authorization when you delete your account.
- Make — receives the bank notifications you forward and passes them to the Service, and sends the test email used during email-forwarding setup. Emails stay in Make's execution history for up to 30 days; emails that fail to process are held in Make for retry, also for up to 30 days, and are then deleted by Make automatically.
- Have I Been Pwned — receives the first 5 characters of your password's hash at sign-up, to check it against known breaches.
- Anthropic — only after you tap Agree for "Let AI help read notices" in the app, and while the switch stays on: to read the amount, date and shop of payment notices we cannot recognise or read, and to draft reading rules, it receives the notice text masked on our server (including an excerpt of bank and payment-service emails you forward; card numbers cut to the last four digits; account numbers, phone numbers, email addresses, links, national ID numbers and ledger members' names removed; amounts, dates and merchants remain). Chat messages and anything obtained through the Gmail connection are never sent. While the switch is on it also receives notice formats with everything personal removed that have appeared in at least 3 ledgers, never notice text (see section 1).
- Anthropic — only when you yourself turn on "AI category suggestions" in Settings › Auto capture, and only for your own purchases: to suggest a category for an automatically captured purchase it receives the merchant name, the amount, the bank's own category, the ledger's category names, and your earlier "merchant → category" choices. (Once "category notes" is on, it also receives your own one-line note for each category, and — to write those notes, at most once a week — counts of your own common merchant names, shop types and time-of-day and amount bands, never single amounts, dates, notice text, names, accounts or account numbers.) It does not receive notification text, names, accounts or user IDs, nor anything obtained through the Gmail connection. A suggestion is only offered to you to apply with one tap; it never changes a record by itself.
- Anthropic — only once the shared merchant knowledge's "AI recognition" is switched on (it does not depend on anyone's own setting): to work out which brand and kind of shop a new merchant name on a statement or notice is, it receives the merchant name (the name only) and the list of brand names we already know. It does not receive amounts, dates, notice text, names, accounts, account numbers or any user or ledger ID, nor a transfer's payee, anything obtained through the Gmail connection, or a name seen in only one ledger that looks like a person's name, and it only receives names the public registries could not identify. An answer is treated as a guess: it never merges records by itself and never makes a category certain. While the feature is off, nothing is sent.
- Anthropic — only when you yourself send a report of a reading problem: it reads the masked report text to draft reading rules, and reads screenshots you upload (which may show names, the last digits of a card and amounts) only to transcribe them into text. The right values you type are not sent.
- Anthropic — only when you tap Agree for one import: to read each line of a statement, or to work out the columns of another app's file, it receives the statement text masked on your phone (or the column names and first 20 rows): card numbers cut to the last four digits; names, addresses, ID numbers, account numbers and phone numbers removed; dates, amounts and merchants remain. The file itself is not sent and we do not store the text.
We do not share your data with anyone else except where required by law.
5. Security
All traffic is encrypted with HTTPS. The database uses row-level security so that each record is accessible only to members of its ledger. Access credentials are kept server-side only.
6. Retention and deletion
- You can delete transactions, accounts and categories in the app at any time.
- Notice-format candidates that do not reach 3 ledgers within 60 days are deleted; a format sample is kept 90 days after it has been used to write a test, and at most 1 year if never used.
- A reported screenshot is deleted after 30 days, or 7 days after the report is handled, whichever comes first; a report's masked text is deleted 90 days after it is handled and kept at most 180 days. Deleting your account deletes your reports.
- The text of a text message or app notification is kept while it waits in Imports. If you skip it yourself, we clear the text at once; if the service skips it automatically and it shows an amount, we keep the text for 7 days, visible only to you in Imports › Skipped so you can tap "It's a transaction" to bring it back, then clear it; notices held for you to decide are kept for up to 14 days; once it is merged into a record or added as one, we keep the text for another 14 days so you can tap "This notice was read wrong" on that record, then clear it and keep only the parsed date, amount, merchant and last four card digits. During those 14 days only you (when you report) and our server-side rule checks (against the values you reported) read it.
- You can revoke the Service's Google access at any time on your Google Account permissions page; we then stop accessing Gmail.
- You can delete your account at any time in the app under Settings › Profile › Delete account, which takes effect immediately. A ledger you were the only member of is deleted with all its records, accounts and budgets. In a ledger shared with others, the records you entered (still showing the display name you had), the shared accounts you added and shared budgets stay with the other members; your private accounts and their records are deleted (records counted toward a shared budget stay, under an account shown as "{name} (left)"); your personal budgets, connected Gmail accounts, email-forwarding settings, Shortcut keys, confirmed merchant → category choices and usage records are deleted. Steps and details: Delete your account and data.
- If you cannot use the app, email gabriel@spotx.studio to request deletion; we will complete it within 30 days.
7. Children
The Service is not directed at children under 13, and we do not knowingly collect their personal information.
8. Changes
We may update this policy from time to time and will change the effective date above. We will notify you in the app of material changes.
9. Contact
Questions about privacy: gabriel@spotx.studio.