What the app actually stores, and where to ask for deletion or clarification.
Last updated: August 2026.
Account details, receipts you upload, and the budgeting data you create - nothing more than what the app needs to work.
Account-scoped, never public, never sold. One-way in, never shared onward - that's what the banner animation represents.
This Privacy Policy was written by BudgetFlow AI's founder, not a lawyer. It's an honest, plain-language description of what the app actually does with your data - not a substitute for professional legal advice, and not a guarantee of compliance with every data-protection law in every country.
BudgetFlow AI is an early-access personal finance and receipt-scanning app, built and operated by a single independent founder based in Portugal. This policy explains what data the app collects when you use it, why, and what choices you have. It is written to be read, not just filed away.
Your name, email address, username, and a securely hashed password (we never store your password in plain text). If you are logged in, we also store your preferred language.
Receipts and invoices you upload, including the image or PDF file and the text our OCR engine extracts from it down to individual line items, plus anything you enter directly: money entries, budgets, installment plans, recurring payments, categories, payment methods, and accounts.
A session cookie that keeps you signed in, and a cookie that remembers your language. Our server also keeps ordinary application logs used to debug problems; we do not run IP-based analytics or ad tracking.
We collect this data to run the app for you: extracting totals and items from your receipts, building your reports, budgets, and Safe-to-Spend estimates, keeping you logged in, and showing pages in your preferred language. We do not use your financial data for advertising, and we do not build behavioral profiles from it.
Your data lives in a PostgreSQL database operated for the app, with secrets such as encryption keys and session keys held outside the source code. Uploaded receipt files and extracted OCR text are stored on the application server, scoped to your account so that only you can read them.
We do not sell your data, and we do not share it with advertisers or data brokers. We currently use no email-sending or analytics vendor. Pages on this site do load fonts, base styling, and chart rendering directly from third-party content delivery networks (Google Fonts, jsDelivr, and Plotly's CDN) - that means your browser makes a direct request to those providers when a page loads, and we don't control what those providers log on their end.
We use exactly two cookies, both required for the app to function: a session cookie (expires after about 8 hours of inactivity) that keeps you signed in, and a language cookie (expires after one year) that remembers whether you prefer English or Portuguese. Neither is used for advertising, tracking, or analytics, so we don't show a cookie banner with accept or reject choices - under data-protection rules like the GDPR, cookies that are strictly necessary for the service you asked for don't require that kind of consent.
You can export your financial data at any time from Settings. You can correct almost anything by editing it directly in the app. You can permanently delete your account and everything tied to it from Settings - see "Delete Account" below. For anything else, including questions about your data, contact us and we'll help.
We keep your data for as long as your account is active. If you delete your account, your data is permanently removed, not just hidden - see the Delete Account section in Settings for exactly what that does.
BudgetFlow AI is not directed at children, and we don't knowingly collect data from anyone under 16. If you believe a child has created an account, contact us and we'll remove it.
As the product changes during early access, this page may change with it. We'll update the date at the top when it does.
Reach out any time at bkhayatian@gmail.com or through the contact page - you'll be talking to the person who actually built this, not a support queue.