Privacy Policy
Last updated: November 3, 2026
Introduction
Welcome to BudgetLabs ("we," "our," or "us"). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our budgeting application and related services.
Important Notice: BudgetLabs is not designed to store highly sensitive personal information such as financial account numbers, credit card details, or login credentials for banks or other institutions. Please do not enter such information into the application.
Information We Collect
Account Information
When you create an account, we may collect:
- Email address
- Name (optional)
- Account credentials (securely hashed)
- Email communication preferences — whether you have opted out of marketing email, and when that choice was last changed. We also keep an internal record of each change (the new setting, the time, and whether it came from your Settings page, an unsubscribe link, or a support request), so we can show that an opt-out was honored. Used solely to suppress marketing messages and to evidence that choice; it does not affect transactional email (password reset, signup confirmation, family invites).
- Legal acceptances — which version of these Terms and this Privacy Policy you accepted or declined, and when. We keep every response rather than only the most recent one, so there is an accurate history of what you agreed to. It is used to know whether to ask you again, and to evidence which version you agreed to if that is ever in question. It is deleted with your account.
- How you found us — if you arrive at signup from one of our own campaign links (e.g. a blog post or a comparison page on our site), we record the short campaign tag from that link with your account so we know which page or campaign brought you to signup. This is an internal page/campaign identifier only — it contains no browsing history and is never shared with third parties.
- How you heard about us — during setup we ask, optionally, where you heard about BudgetLabs (for example a friend, a search engine, or an AI assistant), with a short free-text answer if you pick “Other”. If you pick an AI assistant, we also ask, optionally, which one and what you asked it. The source and the assistant name are stored as plain text; what you asked is encrypted at rest with AES-256. We use these answers only in aggregate to understand which channels bring people to BudgetLabs and what they were looking for — they are never shown to other users, never shared with third parties, and never passed to Hank or any other AI feature. They are deleted with your account.
Financial Data
To provide budgeting and tracking features, we collect user-entered data such as:
- Budget categories and amounts
- Your budget's currency and number/date format — a currency code and a language tag (e.g. SEK and sv-SE) chosen in Settings. Stored in plain text because they describe how figures are displayed, never an amount; used only for formatting. We do not convert between currencies and hold no exchange-rate data.
- Transaction descriptions, dates, and amounts
- Income and expense information
- Savings goals and targets
- Asset and debt account balances, including optional loan terms, recurring contribution amounts, and employer-match amounts you choose to record
- Investment holdings you choose to record inside brokerage, retirement, HSA, 529, and crypto accounts — ticker symbols and market values, plus optional fund names, share counts, and cost basis. Encrypted at rest with AES-256; never shared with third parties.
- Target allocation percentages you optionally set per asset class (US equity, international, bonds, real estate, crypto, cash) to compare against your actual holdings mix on the Allocation page. Encrypted at rest with AES-256; never shared with third parties.
- Collectibles you choose to track in a Collection asset account — card details such as player or character, set name, year, manufacturer, variant, card number, grading company, grade, and certificate number, plus condition, values and prices (paid, listed, and sold), where you acquired the card, and any notes you add. Most of these fields are encrypted at rest with AES-256; card number is stored as plain text because sorting and matching each card to its set's checklist require it, and on its own it says nothing about you. If you build out a set's checklist — which cards you have or still need — the checklist itself (the set's name and manufacturer, and each entry's player/character and subset) is stored the same way. When a card or set is matched to the CardSight catalog we also store links to its catalog entry (the card, set and variant identifiers), encrypted the same way; a CardSight set's own checklist is fetched when you open the set and is not stored with your account. Picking a set from BudgetLabs' own card catalog in “Find a set” copies its checklist into your account, stored the same way as a checklist you build yourself, and keeps a link to the catalog set it came from, encrypted the same way; the catalog itself is a shared list of published card sets and holds no personal data. Not shared with third parties, except as described below: when a card photo is sent to CardSight AI, or a catalog search or lookup is made (see “AI Features and Third-Party Processing”), and, when eBay comps are on, the search terms built from a card's details are sent to eBay (see “eBay price summaries” in this list). We keep a dated history of the values recorded for each card (encrypted, including estimates and values filled in automatically from eBay asking prices), so you can see how a card's value changed; it is deleted when the card is deleted. We also keep the purchases you record for a collection — date, description, cost and an optional set — encrypted at rest with AES-256 (the date and set tag are stored as plain text); never shared. Members of your budget who have access to Cards can see them, and they are deleted when you delete the purchase, the collection or budget that holds them, or your account (purchases you recorded in a budget you don't own stay with that budget); deleting a set leaves its purchases in the collection, untagged.
- Photos of your cards — the photos you take or choose when you scan a card (its front, and its back if you add one), the photo of a card you saved from an older scan, or a photo you add to a card yourself, plus a small thumbnail made from the front, and a photo of the card's back that you add to a saved card yourself. Stored in a private card-photos bucket on Supabase Storage, never public: only members of the budget the collection belongs to who have access to Cards can view them, and only through links that expire after an hour. A back is stored the same way as the card's photo, and you can remove it at any time. Never shared with third parties, except that if you turn on Fill in details overnight for a collection, its cards' photos are sent to xAI as described under “AI Features and Third-Party Processing”. They are deleted (from our storage) when you remove the photo, delete the card, or delete your account — including photos you added to other budgets you can still edit (a photo another member later replaced is theirs, not yours; photos you added to a budget you have since left, or can now only view, stay with that budget). When a budget's owner deletes their account, every card photo in that budget is deleted with it. Photos left behind when a whole collection or budget is deleted are removed by a daily clean-up, typically within a day. Scans started in an earlier version of the app are different: while such a scan waits to be read and reviewed, its photos (one per card; a scan started before October 11, 2026 may also hold a card's back until the scan is deleted, and a back is kept with the card you save) are held in the same private storage, and what CardSight read from each card is stored with the scan, encrypted at rest with AES-256, for you to review. Both are private to your budget, not to you: other members of that budget who use Cards can see them until they are deleted, and reviewing a scan does not delete what was read from it. The photos are deleted when you save or discard the cards (except the photo of a card whose own photo could not be saved, which stays with the scan), or delete your account while you can still edit that budget, and a daily clean-up deletes the scan — any photos still waiting and what was read from them — once it is 7 days old.
- eBay price summaries for the cards you track — only when eBay comps are on for your account. For each card, once a day we store a summary of the asking prices we saw on eBay: the median, low and high price and the number of listings (and how many are new), encrypted at rest with AES-256, plus when it was last refreshed and whether the search found matches. If you change a card's eBay search, the search words you add and the words you exclude are stored with the card, also encrypted. We do not store eBay listings — no listing titles, photos, links or seller details are kept; the listings shown in the Market sheet are fetched from eBay when you open it and held in server memory for up to 15 minutes and never written to our database. When a card has no value you set yourself, its latest median asking price is recorded as the card's value (encrypted like any card value, and marked as coming from eBay asking prices) and counts toward the collection's value and your net worth; a later refresh updates it, a value you enter or confirm replaces it and is never changed automatically, and a value you clear is filled again by the next price. Members of your budget who have access to Cards can see these summaries. They are deleted when the card is deleted (and with the collection or budget that holds it). Card details sent to eBay to run the search, and listing thumbnails loaded from eBay's image servers, are described under “Data Sharing and Disclosure” below.
- Optional gross annual salary you choose to enter in Profile, used only to auto-convert between contribution percent and dollar amount in the savings modal — encrypted at rest, never shared with third parties
- Health Savings Account (HSA) limit-tracking details, if you record an HSA as an asset: the coverage tier you select (family or self-only), whether you mark an account holder as age 55 or older (which changes the IRS catch-up allowance), and an optional amount you enter for contributions already made this calendar year that aren't logged as transactions, together with the year that amount applies to. The contribution amount is encrypted at rest with AES-256; the coverage tier, the age-55 flag, and the year are stored as plaintext. We collect no diagnoses, claims, providers, or any other medical information — these values are used solely to show your progress against the published IRS annual limit inside the app, and are never shared with third parties, used for advertising, or supplied to any insurer.
- Money leaks records — the decisions you make on the Money leaks page about recurring charges BudgetLabs finds in transactions you have already imported (keep tracking, note which of your budget categories already covers it, mark cancelled with the date you cancelled, mark as a habit, or dismiss), each stored with the merchant name derived from the bank description, its billing frequency, and the latest amount; and any free trials you add, with the service name, the date the trial ends, and the price it renews at. Merchant names, labels and amounts are encrypted at rest with AES-256; never shared with third parties. Detection itself runs on transactions you have already imported — Money leaks never connects to your bank or your email inbox.
- Reimbursable expense notes — free-text memos you add when marking part of a transaction as expected to be paid back by a third party (e.g. a friend, employer, or insurance). Encrypted at rest with AES-256; never shared with third parties.
- Amount adjustment reasons — optional free-text notes you supply when you manually override the amount on an imported transaction (e.g. “added $10 cash tip”). Encrypted at rest with AES-256; never shared with third parties. The original bank-reported amount is also retained internally so duplicate detection keeps working after an override.
- Dedup feedback — your confirmations of fuzzy-duplicate matches in the import preview, along with the incoming row's date, description, and amount at the time of confirmation. Encrypted at rest with AES-256; used solely to improve our duplicate-detection logic and never shared with third parties.
- Subscription cancellation reason and optional comment — if you cancel your subscription in-app, we record which reason you selected from the cancellation survey (e.g. “Too expensive”, “Not using it enough”) and, if you choose to provide one, a free-text comment. The reason is stored as plaintext; the free-text comment is encrypted at rest with AES-256. This information is used solely to understand churn and improve the product — it is never shared with third parties.
- In-app satisfaction feedback — an optional 1–5 star rating and an optional free-text comment you submit through the in-app feedback prompt. The comment may contain whatever you choose to write. Encrypted at rest with AES-256; used solely to improve BudgetLabs and never shared with third parties or published as a public review.
- Receipts and source artifacts you choose to attach to a transaction — receipt photos, dropped emails (raw
.eml, HTML body, or plain text), or uploaded statement PDFs / images. Stored in your private receipts bucket on Supabase Storage, scoped to your account by row-level security, served only via short-lived signed URLs you request, never shared with third parties. You can remove a receipt at any time by clearing it from the transaction. - Peer-debt loan records — if you lend to or borrow from another BudgetLabs member on a different budget (for example, a family loan), we store the loan's principal amount, a description, and its payment history, encrypted at rest with AES-256. If you propose a loan, we also collect the invitee's email address (encrypted at rest, plus a one-way hash used only to match their sign-in to the invitation) to send a one-time invitation link. See “Sharing Your Data with a Peer-Debt Counterparty” below for who can see this information.
Note: We do not collect, store, or process actual bank account numbers, credit card numbers, or login credentials for financial institutions.
Newsletter Subscription (no account required)
You can subscribe to our email newsletter from our blog or the site footer without creating an account. If you do, we collect:
- Your email address, encrypted at rest with AES-256.
- Which page you subscribed from — an internal tag such as
blog-<article>orsite-footer, so we know which article brought you in. It contains no browsing history. - The dates you subscribed, confirmed, and (if applicable) unsubscribed, and your current subscription status.
Subscribing is double opt-in: after you submit the form we email you a single-use confirmation link, and you are not added to the list until you click it. If you never click it, we send you nothing further — the only way another confirmation email is sent is if the form is submitted with your address again, and even then we will not send one within 15 minutes of the last. We use your address for one purpose only — sending the newsletter — and every newsletter email carries a one-click unsubscribe link. We do not sell or share this list, and subscribing does not create a BudgetLabs account.
If you also hold a BudgetLabs account, your newsletter subscription is tracked separately from your account's email preferences: unsubscribing from one does not unsubscribe you from the other, and each email tells you which list it came from.
Usage and Device Data
We may collect limited usage data (e.g., device type, browser, IP address) and use cookies or similar technologies for analytics and performance. You can manage cookie preferences through your browser settings.
We also record in-app interaction events tied to your account — specifically, which feature-discovery tips and What's New announcements we show you (e.g. a suggestion to try Smart Import or ask Hank a question) and whether you dismissed or acted on them — solely to improve how we surface features you haven't tried yet.
Separately, we record which features you open and which actions you take while signed in — for example, that you visited the Debt page, or that you added a transaction — so we can see which parts of BudgetLabs are actually used and which aren't, and improve the product accordingly. This is product analytics: it is tied to your account internally, and it is never shown to other users or used for advertising. The content of it — what you spent, on what, in which category — is never shared with anyone. We do send Google Analytics an opaque account identifier (a random ID, not your email or name) so we can tell whether the same person came back the next day rather than counting them twice; that identifier carries no financial data and is meaningless without our database. As set out below, Google Analytics is disabled entirely for visitors in the EEA, UK, and Switzerland, so nothing — including that identifier — is sent to Google for those visitors.
Before you are signed in, the first screen of our app (the one with “Continue with Apple” and “Sign up with email”) records counts on our own servers: that the screen was shown, which of its buttons was tapped, and, if a sign-in or sign-up you started from that screen fails, a short error code (for example, that the Apple sign-in sheet was cancelled). Each record carries the platform (iPhone, Android or web) and a random identifier that lasts only until you close the app (on the web, the browser tab), so a view and a tap from the same visit can be counted together. The records we store contain no name, email address, account identifier, IP address or message text; we do not link them to any account, including one you create afterwards; they are not sent to Google or anyone else; and they are deleted once they are more than 90 days old (our cleanup runs monthly).
Cookies and Browser Storage
We keep the browser-storage footprint small and first-party. What we store falls into two groups:
- Essential (required for the service to work): your sign-in session (so you stay logged in), an optional trusted-device token if you choose to skip two-factor prompts on a device for 30 days, a cached copy of your subscription status so the app can render without re-checking on every page, how you found us (the referral tag from a link you clicked), and your interface preferences (e.g. which dashboard view you last used, and your budget's currency and number format so amounts render correctly on first paint).
- Analytics: Google Analytics cookies, used to understand which pages and articles people find useful. These are not required for the app to function. Separately, while you are signed in, opening a feature writes a
sessionStoragekey holding a timestamp — one per feature — so we don't record the same feature-view event (see “Usage and Device Data” above) more than once every 30 minutes in that browser tab. It holds no content beyond the timestamp and clears when the tab session ends. Before you sign in, the app's first screen keeps the random identifier described in “Usage and Device Data” in onesessionStoragekey; it is not linked to you and clears when the session ends.
We do not use advertising or cross-site tracking cookies, and we do not sell or share this data. We do not set Google Analytics, or any other third-party or advertising analytics storage, for visitors in the EEA, UK, or Switzerland. The first-party feature-view timestamp described above is written the same for those visitors as for everyone else — it is not a cookie and carries no advertising or cross-site purpose. See Service Providers below for who processes analytics on our behalf.
How We Use Your Information
We use the information we collect to:
- Provide, maintain, and improve our budgeting services
- Track budgets, process transactions you enter, and show your progress
- Send service-related notifications and account updates — including, on Pro, an email two days before a free trial you are tracking turns into a charge and an email if a subscription you marked cancelled charges you again. These go to every member of a budget covered by Pro, are on by default, never name the merchant or the amount, and can be switched off on the Money leaks page.
- Occasionally email you product updates, a short note from the founder asking for feedback, or an automated message based on your in-app activity (for example, a reminder to finish setting up, or a check-in if you've gone quiet). These are marketing messages — every one includes a one-click unsubscribe link, and you can opt out at any time from Settings → Communication or from any of those emails without affecting your account or any transactional email.
- Send our blog newsletter, if you subscribed to it and confirmed that subscription. We use a newsletter subscriber's address for that and nothing else — it is not used for advertising, not combined with account data to profile you, and not shared with anyone.
- Respond to your requests and provide customer support
- Collect and review optional in-app ratings and feedback you submit, to understand satisfaction and improve the product
- Detect, prevent, and investigate fraud or abuse
- Analyze usage to enhance features and performance
Data Storage and Security
We implement commercially reasonable technical, administrative, and physical safeguards to protect your information, including:
- Encryption in transit: All connections to BudgetLabs use HTTPS/TLS.
- Encryption at rest: Sensitive financial fields are encrypted with AES-256 at the column level inside our database, so the stored values are unreadable without the encryption key. The key is held in a managed secrets vault — never in application code or source control.
- Row-level security: Every record is access-scoped to its owning user at the database layer; users cannot read or modify other users’ data even by direct database query.
- Optional two-factor authentication (TOTP): You can enable 2FA in Settings → Security to require a 6-digit code on each sign-in.
- Trusted-device tokens: If you opt to trust a device for 30 days, we store a one-way hash of a per-device token (not the token itself), the device’s user-agent string, and the IP address used at the time of opt-in, so you can review and revoke trust later.
Important: No method of electronic transmission or storage is 100% secure. While we strive to protect your data, we cannot guarantee absolute security.
You are responsible for keeping your account credentials confidential and for all activities that occur under your account.
AI Features and Third-Party Processing
BudgetLabs includes optional AI-assisted features (collectively, "Hank" — the in-app chat assistant, AI-powered transaction import, AI-powered receipt scanning, AI-powered bill scanning (for upcoming-bill scheduling), AI-powered free-trial scanning (for the Money leaks trial tracker), and an MCP server for connecting external AI agents). When you use these features, certain inputs and the relevant context required to answer your question are sent to third-party AI providers for processing.
Specifically:
- The in-app chat assistant routes your messages, plus a limited slice of your budget data needed to answer them (for example: requested category names, transaction details, or spending summaries), to xAI (Grok) via the Vercel AI SDK.
- AI-powered import (pasted text, CSV / spreadsheet, uploaded bank-statement PDFs, and uploaded statement images), receipt scanning, and bill scanning (photos of upcoming-bill invoices, PDF bills, or emails / pasted text dropped into the “Add bill” modal, for extracting vendor / amount / due-date / supporting notes) send the file contents, email body, or image you submit to xAI for parsing into structured transaction or bill fields. Uploaded files are processed in memory and are not retained by BudgetLabs after parsing.
- AI-powered free-trial scanning (a trial confirmation email, PDF, screenshot or pasted text you drop into “Add a free trial” on the Money leaks page, a Pro feature) sends that content to xAI for extracting the service name, the date the trial ends, the price it renews at, and how often. Nothing is saved until you review the fields and add the trial, and the content you dropped is not retained by BudgetLabs after parsing.
- AI-powered investment statement scanning (brokerage, retirement, or crypto account statements you drop onto an asset account's Holdings section, as a PDF or an image) sends the file contents to xAI for parsing into structured holdings fields — ticker symbol, security name, asset class, market value, share count, cost basis — plus the account's stated total value and statement date. Nothing is saved to your account until you review the extracted holdings and press Save. The uploaded file is processed in memory and is not retained by BudgetLabs after parsing.
- Card scanning. Scanning a card saves the photos you take or choose of its front and, if you choose, its back straight to your collection as a new card: they are cropped, straightened and downscaled on your device and kept in private storage (see “Photos of your cards” under Information We Collect), and scanning itself sends nothing to CardSight AI, xAI or any other AI provider (the optional overnight reading described below is separate and off unless you turn it on). On iPhone, the app's card camera also reads the text printed on the card, on your phone. The text it read stays on your phone and is discarded; only the few details it fills in from it (card number, season, serial number, brand and, when it is clear, the name) are saved on the new card, the same as details you type, and you can edit them on the card at any time. When the front and the back read the name differently, both readings are kept with the card (encrypted, like its other details) so it can ask you to check the name; saving the card clears them. Like typed details, they are used in the card's eBay search when eBay comps are on (see “eBay price summaries”). Otherwise you fill in the card's details yourself. A card scan started in an earlier version of the app (photographs of trading cards and collectibles you captured in an asset account's collection) sends its images to CardSight AI (an independent third party; see “Data Sharing and Disclosure” below), not to xAI, so the card can be identified — player or character, set, year, card number, and, for a graded card, the grading company, grade and certificate number printed on the slab label. Each card is one photo of either side, taken with your phone's camera or chosen from your photo library, and it is cropped, straightened and downscaled on your device before being sent. CardSight's terms allow it to use images uploaded to it to improve and train its models. For the cards it identifies, we also look up sold prices from the last 3 months, or the last 12 when that's too few (one lookup per batch of scanned cards), sending CardSight only those cards' catalog identifiers; a “market estimate” is the median of at least three completed auction sales from that window. Cards CardSight is not confident about are shown as unreadable for you to fill in yourself. When you save a scanned card, BudgetLabs keeps its photo and a small thumbnail in private storage so the card can show its picture (see “Photos of your cards” under Information We Collect for who can see them and when they are deleted); you can also add a photo of a saved card's back from the card form, stored the same way (private, and deleted with the card), and remove it yourself. Cards are read in the background while BudgetLabs is open, and reading picks up where it left off when you open it again. Until the cards are read and you have reviewed them, the photos you took (one per card) and what CardSight read from each card wait in your budget's private storage, where other members of that budget who use Cards can see them. The photos are deleted when you save or discard the cards; what CardSight read stays with the scan, visible to those members, until a daily clean-up removes the scan and anything still in it once they are 7 days old. Of a scan's photos, only the photo of each card you save is kept (a scan started before October 11, 2026 may also hold a card's back until the scan is deleted, and that back is kept with the card you save too). Any market estimate is saved as the card's value, marked as an estimate, and counts toward the collection's value and your net worth; it is replaced if an eBay asking price for the card arrives later, and once you confirm it or enter your own value, that value is yours and is not changed automatically. For such a scan, nothing is saved to your account until you review the results and press Save.
- Fill in details overnight (optional, off by default). Only the owner of a budget that has no other members can turn this on for a collection in it (from the collection's More menu, which asks you to confirm), so it never sends photos another person added. When it is on, once a night BudgetLabs sends each card in that collection that is missing details, once, to xAI (through xAI's batch service): the card's saved front photo and, if it has one, its back photo, together with the details it already has (name, set, year, card number, variant and maker). xAI returns what it can read from the photos, usually within a day, and BudgetLabs fills in only the fields that are still empty; it never changes a detail you entered. The card is then marked “AI processed”, naming the fields that were filled in, until you next save it, and you can edit them at any time. A record that the card was sent (which batch, when, and whether anything was filled) is kept with the card and deleted with it, so the same card is not sent again. Turning the setting off stops any further cards from being sent; answers for cards already sent may still be filled in. Nothing is sent from a budget once anyone else joins it. Like every xAI feature described here, the photos and details are processed by xAI under its terms; xAI keeps each batch it receives, photos included, until the batch expires about 30 days after it was sent, and BudgetLabs cannot delete it sooner, so deleting a card or your account removes its photos from our storage but not from a batch already sent.
- When you paste a trading-card set checklist to build out a collection, BudgetLabs reads it itself, on your device, at no cost and with nothing sent anywhere — not to xAI and not to CardSight. As with card scanning, nothing is saved to your account until you review the results and press Save checklist, and the pasted text is not retained by BudgetLabs after parsing.
- Catalog lookups. “Find a set” in a collection reads BudgetLabs' own card catalog and sends CardSight AI nothing. When you use “Find this card”, the text you type (sent when you submit it) is sent to CardSight AI from our servers. The CardSight identifiers of the cards and sets you look up are sent too. When you open a set that was added from the CardSight catalog before BudgetLabs had its own, its checklist is fetched from CardSight and held on our servers for up to 24 hours, shared by everyone who opens that set — it records only the catalog's own card list (numbers, names and catalog identifiers), never who looked it up, and it is not stored with your account; instead of the checklist, your account keeps the set's catalog identifier (encrypted) and its card count. No name, email, or budget data is sent to CardSight.
- If you connect an external AI agent (Claude, ChatGPT, etc.) to BudgetLabs via our MCP server, the queries you make through that agent and the responses we return travel through that third-party agent’s provider; their privacy policy governs their handling of those exchanges.
- When you submit the support form, the contents of your message and the subject you chose are sent to xAI so it can draft suggested replies for our support team. The drafts are only ever read by a human, who writes and sends the actual reply — no automated response is sent to you.
We do not use your data to train third-party AI models. We do not share AI inputs or outputs with advertisers.
Separately from these in-app features, we use Anthropic (Claude) to generate our public blog content. That pipeline contains no user data — nothing you enter in BudgetLabs is ever sent to Anthropic.
These AI features are optional. You can avoid sending data to xAI by not using the chat assistant, AI import, receipt scanning, bill scanning, free-trial scanning, investment statement scanning, the support form, or Fill in details overnight for a card collection. “Find this card” (and card scans started in an earlier version of the app) use CardSight AI instead, and you can avoid sending data to it by not using “Find this card” or opening a set added from the CardSight catalog in a collection. You can revoke external MCP integrations at any time from Settings → API & Integrations.
External AI agents are read-only unless you grant write access. When you connect an outside agent through our MCP server, the permission screen asks separately whether it may change data on your behalf. If you decline, the agent can only read. If you accept, it may correct your existing investment holdings — ticker symbol, security name, market value, share count and cost basis — and, for administrators, create and edit blog content. If bank statement import is available on your account, it may also hold transactions it reads from a statement you share with it, add them to your budget, and create or change category rules. BudgetLabs receives what the agent sends: each row’s date, description and amount, plus the statement’s type, opening and closing balances, and the name of the account it belongs to, but not the statement itself. A batch waiting for your answers is encrypted at rest as an unfinished import, and is deleted when you finish or discard it, or by our monthly cleanup once it has sat untouched for 30 days. Saving a batch can also change the stored balance of a linked cash account, show a category in a month it was not listed in, link a payment to an annual event, and record your duplicate decisions. Asking you before it saves is the agent’s job, and BudgetLabs cannot confirm that you approved a save, so keep an eye on what your agent does. The agent cannot create or delete a holding, move one between accounts, or change or delete a transaction already in your budget. The permission screen summarizes these before you agree, and you can revoke the grant at any time from Settings → API & Integrations.
Data Sharing and Disclosure
We do not sell your personal information. We may share information in these limited circumstances:
- Service Providers (subprocessors): With trusted third parties who help us run the Service, including:
- Microsoft Azure — application hosting (Azure Web App).
- Resend — email delivery, covering both transactional email (e.g. password reset, sign-up confirmation, family invites) and product / marketing email. Resend receives your email address and the content of the message we send you.
- Supabase — managed Postgres database, authentication, and file storage.
- xAI (via the Vercel AI SDK) — large-language-model processing for the in-app chat assistant, AI-powered import (pasted text, CSV / spreadsheet, PDF, and image uploads), receipt scanning, bill scanning, free-trial scanning, investment statement scanning, drafting suggested replies to support requests, and drafting our monthly newsletter; and, only for a card collection whose owner turns on Fill in details overnight, reading that collection's card photos and details to fill in empty card fields (sent directly to xAI's batch API). The newsletter drafting sends only our own already-published material — release notes and blog posts — and no user data of any kind. See "AI Features and Third-Party Processing" above.
- Anthropic (Claude) — generates our public blog content; no user data is ever sent to it.
- Stripe — payment processing for web subscriptions. We do not store full payment-card numbers.
- RevenueCat, in conjunction with the Apple App Store and Google Play — in-app purchase processing on mobile. Payment-card and billing details are handled by Apple or Google directly under their privacy policies.
- Google Analytics and Google Search Console (Google) — aggregate usage, performance, and search-traffic analytics for our marketing site and app, read server-side via Google's Data APIs to power internal dashboards. Where analytics runs (i.e. outside the EEA, UK, and Switzerland) we also send an opaque account identifier so repeat visits by the same person are counted once rather than as separate strangers. No email, name, or financial data is sent.
- YouTube (Google) — embedded product-demo video on the marketing site, served from the privacy-enhanced
youtube-nocookie.comdomain. No cookies are set until you play a video; once you play one, YouTube receives your IP address and may set cookies under Google's privacy policy. - SaaSHub — we display an “Approved on SaaSHub” badge in the footer of our public marketing and content pages, loaded from SaaSHub's image CDN. Because your browser fetches that image, SaaSHub receives your IP address, browser user-agent, and the page you were viewing. No account or budget data is sent, and the badge is not shown on signed-in app pages.
- CardSight AI (an independent third party): trading-card identification and catalog lookups, only for users with access to Cards. Card photos from scans started in an earlier version of the app are sent to CardSight (api.cardsight.ai) from our servers to identify the card and read any slab label, and CardSight's terms allow it to use uploaded images to improve and train its models. We also send it the text you type into “Find this card” (“Find a set” reads BudgetLabs' own catalog and sends CardSight nothing), the CardSight identifiers of cards and sets you look up, and, to price a card, only its catalog identifier. No name, email, or budget data is sent. CardSight is a separate company with its own terms and privacy practices, which govern what it does with what it receives. We keep a count of how many CardSight requests are made each day, per account, only to cap usage.
- eBay (an independent third party, not a service provider acting for us): asking-price comparisons for the trading cards you track, only when eBay comps are on. When you add a card to a collection, open a card's Market sheet, press Refresh comps, or (once a day) when our scheduled refresh runs, the card's details (those you entered, or those the iPhone card camera filled in from the card's printed text) — year, set, manufacturer, player or character, card number, variant, print run (serial numbering, such as /99), grading company and grade — and any search words you add are sent to eBay's search interface as search terms, from our servers rather than your browser. No account, contact, or financial information is sent, and eBay does not receive your name, email, or budget data. When you open the Market sheet, your browser also loads listing thumbnails from eBay's image servers (
i.ebayimg.com), so eBay receives your IP address, browser user-agent, and the images requested; we ask your browser to send no referrer with these requests, so eBay is not told which BudgetLabs page you were on. eBay is a separate company with its own privacy policy (eBay's User Privacy Notice), which governs what it does with what it receives. We store only a daily summary of asking prices per card (see “eBay price summaries” under Information We Collect); we do not store eBay listings. The prices are eBay asking prices, not sold prices. - Legal Requirements: When required by law, subpoena, or government request
- Protection of Rights: To protect our rights, safety, or property, or that of our users
- Business Transfers: In connection with a merger, acquisition, or sale of assets
Sharing Your Data with Family Members
If you turn on Family Sharing and invite another person to join your budget, that person — once they accept — can see and modify the transactions, categories, monthly plans, debts, savings goals, and other budget data in the budget you share with them. Members of a shared budget can also see each other's name and email address, along with all financial data within the shared budget. Family Sharing is opt-in per invite; nothing is shared until you send an invite and the recipient accepts it.
You can revoke a pending invite at any time before it's accepted, and you can remove a member after they've joined. A member can also leave on their own. When someone leaves or is removed, any transactions they entered into the shared budget remain part of the budget's history so your accounting record stays intact; their personal authentication link to those records is removed.
We do not share your data with the family member's employer, advertisers, or any third party as a consequence of Family Sharing. The other party is a fellow BudgetLabs user who you have authorized to see this budget.
Sharing Your Data with a Peer-Debt Counterparty
Peer debt lets one BudgetLabs member lend money to another member on a separate, unconnected budget — for example, a parent lending an adult child. If you propose a loan, we use the invitee's email address to send a one-time invitation, to confirm the person who accepts is the one you invited, and — for as long as the loan stays open — to identify them to you on your Assets page (you will not learn their name through this feature). If you receive a proposal, both the invitation email and the in-app acceptance page tell you who is proposing it — by first name only, never their email address — and state the amount and description before you decide whether to accept. Accepting requires signing in with the exact email address the invitation was sent to; previewing those terms on the acceptance page does not — anyone signed in who has the one-time invitation link can see them, which grants no more than that same link already lets someone do by using it to accept.
Once a loan is accepted, both of you can see its principal amount, description, and payment history. Because access is granted to anyone who belongs to either linked budget rather than to one individual, so can anyone else on a shared Family Sharing budget either of you belongs to. This is inherent to the feature: a shared, honest record between two households is the whole point, and the person receiving a proposal can always decline — before accepting, the loan is not independently discoverable by anyone in the app; only the lender's household can see it as an ordinary record, and the only other way to see its terms is with the one-time link that was emailed to the invitee. BudgetLabs does not move money. The loan record only reflects that a payment happened outside the app — by cash, bank transfer, or a third-party payment service you and the other party choose.
If the lender forgives the loan, it is marked forgiven and the record is kept, not erased. If the lender's account is deleted, the loan record and its payment history are likewise kept for the borrower rather than erased, and only the connection to the lender's identity is cleared; from her Debt page, the borrower can then either keep the outstanding balance as her own personal debt record or close the loan outright, so it does not sit unresolved. If the borrower's account is deleted, no new payments can be recorded against the loan, though a payment she already submitted can still be confirmed or rejected afterward.
We do not share peer-debt data with anyone outside the accounts involved (and, where applicable, their shared-budget co-members) — never with employers, advertisers, or other third parties.
Your Rights and Choices
Depending on where you live, you may have the right to:
- Right to know / access: request a copy of the personal information we hold about you and how we use it.
- Right to correct: update or correct your personal information.
- Right to delete: delete your account and associated personal information.
- Right to portability: receive an export of your data in a machine-readable format. You can download your budget and account data anytime from Settings → Profile ("Download my data") or via
/api/exportwhile signed in — no support request needed. That export does not include the feature-usage event data described under “Usage and Device Data” above; if you'd like a copy of it, contact us using the details below and we will provide it. - Right to opt out of sale or sharing: we do not sell your personal information and do not share it for cross-context behavioral advertising. You may still exercise this right at any time.
- Right to non-discrimination: we will not discriminate against you for exercising any of these rights.
- Right to opt out of promotional communications: turn off Product news & updates in Settings → Communication, use the unsubscribe link in any marketing email, or contact us directly.
California residents (CCPA / CPRA): you may also designate an authorized agent to make a request on your behalf, and you may appeal a denied request by contacting us at the address below.
EEA / UK / Swiss residents (GDPR / UK GDPR): our legal basis for processing your personal data is (a) the performance of our contract with you, and (b) our legitimate interests in operating and improving the Service. We do not run analytics cookies for visitors in the EEA, UK, or Switzerland — Google Analytics is disabled entirely for those visitors, so we do not rely on consent as a legal basis and you will not be asked for it. When we make a material change to this policy we will tell you in the app and ask you to confirm you have seen it — that is a notice, not a request for consent, and there is nothing for you to decline. (Our Terms of Service are a contract and are handled differently: those we do ask you to accept.) You have the right to lodge a complaint with your local data protection authority.
To exercise any of these rights, contact us at contact@budgetlabs.io. We will respond within the timeframes required by applicable law (45 days under CCPA; 30 days under GDPR, extendable by an additional 60 days for complex requests).
Data Retention
Your record of accepted or acknowledged legal documents is kept for as long as your account exists, and is deleted with it. We keep every response rather than only the most recent, because the point of the record is the history of what you agreed to.
We retain your account information (e.g., email, name) for as long as your account remains active. Financial data you enter is retained for the life of your account plus up to 90 days after deletion for backup and recovery purposes.
If you close the transaction import tool before finishing, we save your in-progress work (parsed transactions, categorizations, and similar edits) so you can resume it later. That draft is stored encrypted and is automatically deleted after 30 days, or immediately once you complete or discard the import.
A card scan started in an earlier version of the app and waiting for review — its photos and what CardSight read from each card — is deleted by a daily clean-up once it is 7 days old; the photos go sooner if you save or discard the cards first.
The daily eBay price summaries for a card (median, low, high and listing counts), and any eBay search words you set for it, are kept for as long as the card exists and are deleted when the card is deleted, along with the collection or budget that holds it. eBay listings themselves are never stored. The dated history of the values recorded for a card is kept for as long as the card exists and is deleted with it. The purchases you record for a collection are kept until you delete them, the collection or budget that holds them, or your account; purchases you recorded in a budget you don't own stay with that budget.
When you submit the support form, your message and the email address it was sent from are also retained as business correspondence in the mailbox we use to manage support, separately from your account record, and are not subject to the periods described above.
Individual feature-view and feature-action events (see “Usage and Device Data” above) are retained for 90 days, after which they are deleted. Before deletion, each day's events are folded into a daily per-feature count with no individual timestamps — those aggregate counts are kept for as long as your account is active, the same as other usage statistics.
Newsletter subscriptions are retained until you unsubscribe. When you unsubscribe we keep your address, marked as unsubscribed, so we can honor that choice and avoid mailing you again — the record of your opt-out is the mechanism that enforces it. If you would rather we erase it entirely, email us and we will. An address that never confirms its subscription is retained as an unconfirmed request; we send it nothing further unless the form is submitted with that address again. Deleting a BudgetLabs account also removes any newsletter subscription held under the same address.
If you do not sign in or otherwise use BudgetLabs for 12 consecutive months, we treat your account as inactive and will delete it along with its data, as described above. We will email you a warning approximately 30 days before deletion and again approximately 7 days before — signing in at any point cancels the deletion and keeps your account active. Accounts with an active paid subscription are never deleted for inactivity, and we do not delete an inactive account whose shared budget is still being used by another member.
After account deletion, we will delete or irreversibly anonymize your personal data within a reasonable period, unless we are required to retain it for legal, compliance, or security reasons. When your account is deleted, we also delete your Stripe customer record and request deletion of your RevenueCat subscriber record (for mobile subscriptions).
Children’s Privacy
BudgetLabs is not directed to or intended for use by children under the age of 13. We do not knowingly collect, use, or disclose personal information from children under 13 without verifiable parental consent, in accordance with the U.S. Children’s Online Privacy Protection Act (COPPA).
If you are a parent or guardian and believe your child under 13 has provided us with personal information without your consent, please contact us immediately at contact@budgetlabs.io. We will promptly delete such information from our records.
Changes to This Privacy Policy
We may update this Privacy Policy from time to time. We will post the revised policy here and update the "Last updated" date.
For material changes, we will give at least 30 days’ notice and ask you to accept them. We will tell you in the app before the change takes effect, and once it does we will ask you to accept the updated policy. We record which version you accepted and when, so there is a clear record of what you agreed to. Minor corrections that do not change what we collect or how we use it are posted without a prompt.
If you decline, we record that as well, and you may accept later at any time. Declining never removes your access to your own information: you can view, export, and delete your data at any point, regardless of your answer. If you continue using BudgetLabs without responding to a material change after its effective date, that continued use constitutes acceptance.
Contact Us
If you have any questions about this Privacy Policy, please contact us:
Hollow Holdings, LLC
Email: contact@budgetlabs.io
Website: www.budgetlabs.io