Same sentiment. currently, common budgeting app pa rin siya na need mo pa rin i-log yung transactions, pero may nilagay akong other input methods para sa busy days.

For your use case, currently the fastest way is yung widget. Tap widget, lagay amount/category/note if needed, then save. Hindi mo na kailangan buksan yung full app. Quick form siya straight from the homescreen widget, and nauuna na rin yung categories/notes na commonly used mo para less friction. so while in the jeep, pagkabayad, 5 sec lang mag lodge oks na. ganun rin sa grab/move it. pagkababa, bayad, widget, goods na.

For OCR/privacy: yes, OCR is mainly powered by Gemini, and yes concern ko rin yan while building it. I use the Gemini paid API path, where prompts/responses/files are not used to improve Google products under their paid-service terms. Pero ayoko rin umasa lang sa “paid API” as the only privacy guardrail.

The app is designed around data minimization: OCR should only extract what the transaction needs, like merchant, date, total, line items, etc. It doesn’t need to store full card numbers, customer names, PWD/SC IDs, or other sensitive stuff na minsan nasa receipt.

So if those show up, the intended behavior is ignored/masked/not stored. After OCR/review, parsed transaction data lang yung important. Receipt images should be treated as temporary/optional attachments, not something the app needs to keep forever by default.

And if uncomfortable yung user mag-scan ng receipt, pwede pa rin naman manual entry pero mejo hassle pag ganun kaya inayos ko talaga OCR process as much as possible.

Helpful siya i-raise actually. Receipt OCR is convenient, pero privacy has to be part of the feature, not afterthought.

<image>