Skip to content

Security and privacy

TxnFlow never asks for your bank login: you upload the PDF statements your bank already gives you. This page lists every company that processes them, how long each piece is kept, and how to delete it.

Do you need my bank login?

No. TxnFlow works only from PDF statements you upload. It never connects to your bank, never asks for online-banking credentials, and holds none.

Where does my data go?

These companies process your data so that TxnFlow can run. No one else receives it.

CompanyWhat forWhat it handlesWhere
SupabaseDatabase, sign-in (sign-in emails are sent through our email provider when one is configured) and file storageYour account email and sign-in records, uploaded PDFs, the statements and transactions read from them, and model usage recordsUnited States (AWS us-east-2, Ohio)
VercelHosting the site and app, and running the background workerEvery request, including each PDF held in memory while the worker sends it to Google for readingUnited States (iad1, Washington, D.C.)
Vercel (Web Analytics)Counting visits to our pages (only on the public site and the sign-in and sign-up pages)Which page was opened (its address without anything after a "?"), the site that linked to it, approximate location (country, region and city), and the browser, operating system and device type. No cookiesVercel's infrastructure; Vercel doesn't say where it stores visit counts
Google (Gemini API)Reading each statement PDF to extract its transactions and balances, and answering questions you ask the assistantThe PDF, sent with the request, and the rows the model returns; for the assistant, your question, the conversation so far and the figures and transactions it looks up to answerGoogle's infrastructure; the Gemini API offers no choice of region
Google Cloud Run (our decryption service)Unlocking a password-protected PDF that the app's built-in decryptor cannot open (only for password-protected pdfs the built-in decryptor fails on)That PDF and its password, held in memory for the request; the password is never loggedUnited States (us-east1, South Carolina)
PaddleSelling plans and page packs as merchant of record: checkout, payment, tax, receipts and refunds (only when you buy a plan or a page pack)What you enter at checkout, such as your email address and payment details. TxnFlow keeps only Paddle's customer and subscription identifiers and what you boughtPaddle's companies in the United Kingdom, the United States, Ireland and Canada; its privacy notice names no storage region
Cloudflare (Email Routing)Forwarding email sent to our support address to our inbox (only for email you send us)Your message, your email address and anything you attachCloudflare's global network
Google (Gmail)Our support inbox (only for email you send us)Your message, your email address and anything you attachGoogle's infrastructure
Cloudflare (Turnstile)Checking that a sign-in or sign-up comes from a person, not a bot (only on the sign-in and sign-up pages)Your IP address and details of your browser and connection, such as their user agent and TLS fingerprint; Cloudflare also uses them to improve its bot detectionCloudflare's global network
ResendSending email: alerts to us; product emails to you (a welcome, your first reconciled statement, a review request, low pages, and reminders after one and two months without uploads), unless you unsubscribe; the confirmation when you delete your account; sign-in emails once our Supabase project sends through it (alerts in every build that sends them; product emails unless you unsubscribe; the account-deleted confirmation when you delete your account; sign-in emails once configured)For alerts to us: internal account and upload identifiers, a redacted error message, or a note that new feedback arrived; never your email address, file names, statement content or what you wrote. For product emails, the account-deleted confirmation and sign-in emails: your email address and the message, which never includes amounts, file names or statement contentUnited States

How are password-protected PDFs handled?

Your browser checks the password against the file first, so a mistyped password is normally caught before anything is uploaded. The password is then sent with the upload, used on our server to unlock the file in memory, and discarded: it is never stored or logged. The unlocked PDF replaces the encrypted copy.

If the built-in decryptor can't open a file for a reason other than the password, the file and password go to our own decryption service on Google Cloud Run, which holds both in memory for that one request and never logs the password.

How long is it kept?

WhatWhereKeptRemoved by
Uploaded PDFSupabase StorageUntil you delete its uploadDeleting the upload. Deleting a statement or an account does not remove the PDF; delete the upload too.
Temporary copy of a password-protected PDFSupabase StorageUntil the PDF is unlocked, moments after uploadRemoved automatically once the file is unlocked. If an upload is abandoned partway, the copy can remain; ask us to remove it.
Statements and transactions, including the rows of a statement held for reviewSupabase databaseUntil you delete the statement, its account or its uploadDeleting any of the three removes them
Accounts (bank name, currency, account type, the last four characters of the account number, latest balance)Supabase databaseUntil you delete the account; deleting an upload or a statement leaves itDeleting the account, or deleting your account in Settings
Categories (yours, and the standard ones an import adds)Supabase databaseUntil your account is closed; the app has no way to delete a categoryDeleting your account in Settings
Rules and budgets you set upSupabase databaseUntil you delete themDeleting them in the app, or deleting your account in Settings
Feedback and survey answers you send from the app (your message, which part of the app you sent it from, and your answer)Supabase databaseUntil you delete your account, or sooner if you askDeleting your account in Settings, or asking us
Your all-data download (a ZIP of your data and PDFs, built when you ask)Nowhere; we keep only the time of your last downloadThe ZIP is streamed to you and never stored. The time of your last download is kept until your account is closed, so downloads can be limited to one every 10 minutesDeleting your account in Settings
The model's raw output (every transaction, balance and account number it read)Supabase database30 days after the model read the statement, or until you delete the upload if that is soonerRemoved by a scheduled job once 30 days old; stripped at once when the upload is deleted
Captured messages and typed notes (what you send or type for the app to read as a transaction, including the bank alerts you forward by email or send from your phone with their sender and subject, and what it read from it)Supabase databaseThe text and what was read from it: 30 days after the capture is settled (confirmed, rejected, failed or not a transaction); one still waiting for your answer keeps it until you answer. The capture's record (when it arrived, from where, and what became of it): until you delete your accountThe text is removed by a scheduled job 30 days after the capture is settled; the record, by deleting your account in Settings
Channel links (each way you connect to send transactions in: the last four characters of your forwarding address or device token, never the address or token itself; and the alert senders you told us to remember)Supabase databaseUntil you delete your account. Revoking, rotating or replacing a link stops it working at once; its record (the hint, the dates and the remembered senders) staysDeleting your account in Settings; a remembered sender, by forgetting it in Settings
Chat with the assistant (your questions and its answers)Supabase databaseThe text of each question and answer, and a conversation's title: 90 days. The rest (when, the figures an answer gave and which of your transactions they came from): until you clear the conversation or delete your accountThe text is removed by a scheduled job after 90 days; the rest, by clearing the conversation in Chat or deleting your account in Settings
Changes the assistant proposed (an entry, a category, a merge) and what you decidedSupabase databaseUntil you clear the conversation or delete your accountClearing the conversation in Chat, or deleting your account in Settings
Learned category rules and category corrections (a merchant you filed under the same category twice, and each time you chose a different category than the one suggested)Supabase databaseA learned rule: until you remove it on the Categories page or delete your account. A correction: until you delete your accountRemoving the rule, or deleting your account in Settings
Account aliases (what a card or account hint like HBL 4821 means for you, from your answers)Supabase databaseUntil you delete the account it points to, or your accountDeleting that account, or deleting your account in Settings
AI clients you connect (what each may do and the dates it was created, last used and revoked; for one you signed in from, the name it registered with, its client id and the website it returns you to; for one with a token, the label you gave it and the token's last four characters, never the token itself)Supabase databaseUntil you delete your account. Revoking a client stops it working at once; its record (the name or label, the hint and the dates) staysDeleting your account in Settings
What your AI clients changed (which client, the action, when and how it ended, the transaction it changed and, so you can undo it, that transaction's values before and after; for a transaction it removed, its whole content)Supabase databaseUntil you delete your accountDeleting your account in Settings
Statements your AI client is importing (the file it sends and the figures and rows it read from it, while the import is open; and the import's record: the file name, its fingerprint, the page and row counts and how it ended)Supabase database and Supabase StorageThe staged file and rows: until the import finishes, or 24 hours after it began. A finished import's file is kept as any uploaded statement is. The import's record: until you delete your accountFinishing the import; otherwise a scheduled job within 25 hours of its start. The record, by deleting your account in Settings
Model usage records (tokens, cost, duration, model, error messages)Supabase databaseAfter the upload is deleted, with no expiry today; they no longer hold the extracted rowsDeleting your account in Settings
Which product emails we sent you and when (never their text)Supabase databaseUntil you delete your accountDeleting your account in Settings
Your product-email choice and its unsubscribe linkSupabase databaseUntil you delete your accountDeleting your account in Settings
PDF passwordsNowhereNever stored or loggedNot applicable
Account email and sign-in recordsSupabase AuthUntil you delete your account in Settings. Supabase's auth audit log keeps sign-in events, with the email address, for its own retention period after thatDeleting your account in Settings removes the account and its sign-in at once, with everything above. Supabase's auth audit log (auth.audit_log_entries) keeps entries for sign-ins and other auth events, with the address, until its retention period runs out; we do not purge it ourselves. A database copy taken earlier keeps your data until that copy is deleted (see Database copies), and support emails follow their own row
Account deletion recordSupabase databaseIndefinitely: internal ids and the timestamps of each deletion step. Your email address is removed from it when the deletion completes. It keeps the account's sign-in identifier, which can be joined to Supabase's auth audit log while that log keeps its entriesNot applicable: once the deletion completes it holds no personal data on its own
Page usage records (each parse's file name, a fingerprint of the file's contents, its page counts, and whether it was charged)Supabase databaseUntil your account is closed; deleting an upload leaves them, so used pages are not refundedDeleting your account in Settings
Page balance and billing account (pages granted and every reservation, charge and release against them; your plan, its status, and Paddle's customer and subscription identifiers)Supabase databaseUntil your account is closedDeleting your account in Settings
Billing event log (each Paddle notification's type, time and outcome, never its contents)Supabase databaseAfter your account is closed, without the link to youDeleting your account in Settings removes its link to you; the log itself is kept
Invite code and invitations (if you create an invite link: your code, and how many accounts signed up through it)Supabase databaseUntil your account is closedDeleting your account in Settings
Who invited you (if you sign up through an invite link: which account invited yours, and when your first statement reconciled)Supabase databaseThe invitation record is kept until either account is closed; if the inviting account is closed, it stays with yours, without the link to that account. If your first statement earned the inviter pages, the inviter's page record keeps an internal identifier of your account (a random id, not your email or name) and the date your first statement reconciled, for as long as the inviter's account exists, because page records are never alteredDeleting your account in Settings removes the invitation record; the inviter's page record, with the internal identifier and that date only, goes when the inviter deletes their account
A keyed hash of an invited address (if you sign up through an invite link)Supabase databaseAfter your account is closed, to stop one address earning invite pages twice (our legitimate interest in preventing abuse). It cannot be turned back into the address without our server's secret key, and it holds nothing else: no link to your account, no name, no dates beyond when it was recordedNot deleted with the account, by design
Support emailsOur support inbox (Gmail)12 months after the conversation endsDeleted after 12 months, or sooner if you ask, including when you delete your account
Failure alerts (an internal upload or account identifier, the kind of failure and a redacted error message; never your email address, file names or statement content)Our database, our inbox and Resend30 days in our database. The emailed copy stays in our inbox until deleted, and Resend keeps its sending log for 30 daysRemoved once 30 days old, the next time an alert is recorded; the inbox copy by hand
Request and error logsVercel, Supabase and Google CloudVercel: 1 hour. Supabase: 1 day. Our decryption service: Google Cloud's default of 30 days (method, path and status only)Expire automatically
Visit counts for the public and sign-in pagesVercel Web AnalyticsAt least a month, the reporting window on our current Vercel plan; Vercel may keep them longer. The code that tells one visit from another is discarded after 24 hoursVercel. It doesn't tie them to any person, so there is nothing to find or delete for one person
Database copiesThe operator's own computer, on an encrypted diskSupabase's current plan takes no automatic backups. Before each change to the database's structure, the operator takes one full copy of the database, which is deleted 30 days after the change is verifiedDeleted on that schedule; deleting your account does not remove you from a copy taken earlier

How do I delete it?

  • Delete an upload and its PDF, the statements and transactions read from it, and the model's raw output all go with it.
  • Delete a statement or an account and its statements and transactions go, but the uploaded PDF stays in storage. Delete the upload too if you want the file gone.
  • Delete your account from Settings, and everything we hold for it goes at once: your uploaded PDFs, bank accounts, statements, transactions, categories and rules, and the account itself. It asks you to type your email address and to have signed in recently. What stays: Supabase's auth audit log, which keeps sign-in events with your email address for its own retention period; a database copy taken before a change to the database's structure, until that copy is deleted 30 days after the change is verified; a deletion record with internal ids and timestamps, without your email address; and our emails with you, kept for 12 months unless you ask us to delete them too. Download all your data from Settings first if you want a copy.

How is it protected?

  • Every connection uses HTTPS, and browsers are told to insist on it (HSTS).
  • Supabase encrypts the stored data at rest (AES-256).
  • Every database query is scoped to your account.
  • TxnFlow holds no bank credentials, because it never asks for them.

What reconciliation can and can't prove

The check proves that the rows TxnFlow extracted add up to the balances the statement prints. It can't catch a statement that is itself wrong, or two mistakes that cancel each other out exactly. Statement content is treated as untrusted: text inside a PDF can try to steer the model, and that risk is reduced, not removed, so an answer that is wrong but adds up would still pass. Check anything important against the original.

Certifications

TxnFlow itself holds no security certifications. Supabase and Vercel each hold a SOC 2 Type 2 attestation, and Vercel is ISO 27001 certified.

If something goes wrong

If we find a security incident that affects your data, we'll email the address on your account without undue delay, and no later than 72 hours after we confirm it, saying what happened, what data was involved and what we're doing about it. Our server alerts us when uploads fail or errors occur, so we can look into them quickly.

Reporting a vulnerability

Email support@txnflow.app with the details and the steps to reproduce. Please don't access other people's data or disrupt the service while testing.

Our contact details are also published at /.well-known/security.txt.

Last reviewed