privacy
spendsense is built to hold as little as possible, and to keep what it does hold private to your account.
what i collect
the transaction CSVs you upload — dates, descriptions, merchant names, amounts, and categories — along with the account/institution name you label them with.
summaries and insights computed from that data (monthly/weekly totals, detected recurring charges, generated spending insights), plus any feedback you give an insight.
what i use it for
showing you where your money went, spotting recurring charges, and generating plain-language insights about your own spending — nothing is shared or sold, and no bank connection is ever made on your behalf.
what i'll never do
sell your data, run ads against it, connect to your bank without an explicit CSV upload from you, or share your financial data with anyone.
where your data lives
in a private, access-controlled postgres database, reachable only through your own account.
if you use spendsense connected to homebase, api requests (uploading a CSV, recomputing insights) carry a homebase access token used only to verify you're entitled to use the app — spendsense doesn't store your homebase identity beyond that check.
your data, your call
re-categorize or remove a transaction any time from your dashboard. email me if you want your account's data gone for good.
questions
email hello@theafoundry.com.