Will NBU see all my financial data?
No. NBU never logs into your bank, never scrapes your credentials, and only ever sees the statements you choose to import. Here is exactly what that means.
We never ask for your banking password.
NBU has no bank connection, no credential vault, and no screen-scraping. We never ask for your online banking login, and there is nowhere to enter it — the feature does not exist.
This is not a toggle or a plan tier. It is how NBU is built, and it stays that way.
You import your own statements.
You export a CSV or PDF statement from your bank yourself and import it into NBU. You decide which accounts, which months, and how much to share.
Nothing lands in NBU that you did not hand it. Import is the bridge, and you are the one who builds it.
Your transactions live in an account only you can reach.
What you import is stored in your own isolated account. Every row is protected by row-level security, so one account can never read another's data, and everything is encrypted at rest and in transit.
Before our AI assistant, Valerie, ever sees a transaction, we strip the personal identifiers — names, account numbers, card numbers. We do not use your financial data to train AI models.
Export it or delete it, whenever you want.
Under Québec's Law 25 and Canada's PIPEDA, you can access, export, correct, or delete your data — whether or not you live in Québec. Export is a plain CSV; deletion removes your data from our systems, with backup copies gone within 30 days.
Nothing changes your money picture on its own. Imported transactions wait for your review before they count — a person, you, is always in the loop.
Shared knowledge that can't point back to you.
Your own transaction history and category labels stay in your private account. Community learning is off by default.
If you turn it on, the merchant-category corrections you make are counted toward a shared suggestion pool. A suggestion only joins the pool once at least five different people have independently taught NBU the same thing — and what's stored is a one-way code made with a secret key, never a readable merchant name. The pool holds no names, amounts, notes, or e-transfer details, and no record of who contributed.
You can turn it off anytime in Settings → Data. NBU learns from patterns, not people.
If open banking arrives, it stays opt-in.
Canada is still rolling out open banking. NBU does not connect to it today, and privacy mode is the default. If regulated sync ever ships, it will be opt-in per institution, with consent you can revoke, and synced data will go through the same review step as anything you import.
No credential scraping, ever. That line does not move.
The details, in full.
Want the legal specifics? They're in plain language too.