Your statement stays on your device

How local PDF conversion, account data, optional saved work and payment records are handled.

Local financial data

PDF contents, passwords, account numbers, filenames and transactions are processed in your browser. During conversion they are not uploaded to our servers, Stripe or an AI service. Clear files, sign out or close the tab to discard current results. Optional saved work is separate.

Account and service records

Supabase stores account email and authentication details, display name, consent, plan, page credits and export receipts. Receipts contain a user-specific result hash, bank, page count and export date, not statement contents. Support forms store the contact details and message you submit.

Stripe receives account email and a user reference for billing. Payment details are entered directly on Stripe. Our database stores customer, subscription, invoice, purchase and payment-status references.

Statement samples are optional. If you attach a file to a bank request and press “Agree and send sample”, your browser reads the file locally and sends only the text and its positions from at most the first 6 pages, including account name, account number and transactions, to Supabase. It is used only to add support for that bank, is visible only to authorised operators, is never shared, and is deleted when the request is closed or within 30 days. The PDF file and its password are never sent.

Anonymous daily totals: we count, per day, visits, conversions started, successes or error codes, verification results, bank, page-count range, sample or full downloads, plan-limit blocks, picks of unsupported banks, bank requests (and whether a sample was attached), pricing views, sign-ups, checkout pages opened and payments, with the kind of source (for example Google, AI, social or the linking site’s name) and the first page group visited. Each browser is counted at most once a day per item. The totals contain no session ID, account, IP address, filename or statement contents, so they cannot identify or be deleted for one person, and they are kept for up to 400 days. Your browser keeps its latest source (30 days) and today’s counted items locally. Counting stops as soon as you press No thanks (use before that may already be counted) or untick anonymous daily totals in settings (this browser only). Nothing is counted if your browser sends Global Privacy Control.

If you press Allow or turn on per-event stats in settings, per-event analytics are also sent: service events, bank and parser version, a session identifier and, when you are signed in, your account ID, without statement contents or session replay. Hosting and authentication providers may retain their own technical request logs.

We measure traffic with Google Analytics, such as pages opened, traffic source, device type and approximate location, which uses Google cookies. It receives page addresses with other parameters removed, except utm and gclid, and never statement contents, filenames or passwords. Google processes this data under its own policies. Google Analytics stops loading when you press No thanks or untick daily totals in settings, and does not load if your browser sends Global Privacy Control.

Optional local saved work

Pro and Firm users can opt in to saving transaction results and client labels in this browser’s IndexedDB. Original PDFs and passwords are not saved. The app does not additionally encrypt saved results; other people with access to your browser profile may be able to read them. Delete individual saved jobs or clear local work from your account. Browser data clearing can permanently remove them.

Retention and requests

Account and export records remain until account deletion. Per-event analytics are retained for up to 90 days, anonymous daily totals for up to 400 days, statement samples for up to 30 days and closed requests for up to 180 days. You can disable analytics, clear local work and request account deletion from your account.

Subscriptions must have ended and no checkout may be pending before account deletion. Deleting the app account does not itself delete payment records held by Stripe under its own obligations. Provider backups may retain data until they expire. Contact support for other privacy requests; do not include sensitive financial documents.

Manage my dataPrivacy request

พร้อมจัด Statement ให้เป็นตาราง

ดูตัวอย่างก่อนสมัคร รองรับรูปแบบ SCB และ K PLUS ที่ระบุ

เลือกไฟล์ PDF