Most money apps ask you to choose: connect a bank and get balances, or read your email and get context. Yuki does not think that is a choice worth making, because the two sources know genuinely different things.
What each source actually knows
| Bank feed | Your inbox | |
|---|---|---|
| Current balance | Yes | No |
| Card payments nobody emails you about | Yes | No |
| What is about to be charged, and when | No | Yes |
| A price increase, before it lands | No | Yes |
| Instalment plans and buy-now-pay-later | Partly | Yes |
| The merchant’s real name, not the card descriptor | Rarely | Yes |
This is why Yuki keeps both and reconciles them on read: whichever sources you have switched on, the answer stays correct, and switching one off changes the picture immediately rather than leaving stale rows behind.
Read-only, and revocable
- Read-only by design — Yuki can see balances and transactions. It cannot move money, make a payment or change anything about the account.
- You hold the switch — disconnect from the same screen you connected on, and access ends there and then.
- Bank credentials never reach Yuki — you authenticate with your bank directly; Yuki receives a token, never your login.
- EU data residency — the same commitment as the rest of your data, and no model is trained on any of it.
