Do people actually want a privacy-first alternative to bank-connected subscription trackers?
I've been looking at subscription management apps recently, and most of them ask users to connect their bank account through Plaid or a similar provider. I started wondering whether people actually prefer that approach, or if they'd be happy with something…
I've been looking at subscription management apps recently, and most of them ask users to connect their bank account through Plaid or a similar provider. I started wondering whether people actually prefer that approach, or if they'd be happy with something simpler even if it meant manually uploading a bank statement CSV once in a while. The trade-off seems to be: Connect your bank → automatic updates, but you have to trust a third party with financial data. Upload a CSV → less convenient, but your data stays on your own device. I ended up building a small prototype that takes the second approach because I wanted everything to run locally in the browser. Before I spend more time building it, I'm curious: Would you ever use a CSV upload approach? Is bank integration basically a requirement for this type of product? What would convince you to use a subscription tracker? If anyone's interested in seeing what I built, I'm happy to share it in the comments.
已收录讨论
I built something like this for myself some time ago. Yes with AI but it's running locally and never sees any external access. github
Appreciate that! My goal is exactly that upload, analyze, and get an answer in a couple of minutes without creating an account or connecting a bank.
Thanks! That's reassuring because I intentionally avoided bank integrations for the MVP. Merchant normalization is definitely the area I'm spending the most time on. I also like the idea of highlighting price increases over time that's something I hadn't considered.
That's interesting! Did you build it mainly to find forgotten subscriptions, or did it evolve into something more? I'd love to know what features you found most useful over time.
Bank integration is not a hard requirement for everyone. Plenty of people will not connect Plaid for a tracker, especially if the value is just spotting renewals and forgotten charges. CSV works if the flow is low friction: detect the bank format, map merchants cleanly, and surface renewals without much cleanup. What usually sells it is clearer answers than the bank app already gives. Upcoming renewals, price changes, free-trial end dates, and a simple cancel checklist matter more than perfect automation. If sharing the prototype, show import time and how it handles messy merchant names.
CSV is viable if the import is boringly good. The killer is merchant normalization + renewal detection, not the bank connection. If it takes three minutes and doesn't ask me to marry Plaid, I'd try it.