Settings
One global screen at /settings, grouped by who each setting serves.
Global, not a dashboard page
Settings used to live under the dashboard, which made the theme, your PIN, the backup password and the AI key read as dashboard features. They are not — someone in the vault or the legacy desk needs them just as much. The old path still redirects, so existing links and browser history keep working.
How it is grouped
Flat, the tabs gave no way to tell that one governs a single import pipeline while another governs the whole app. They are grouped by audience instead — app-wide first, per-feature last:
Account
Who you are and how the app looks to you.
ProfileAppearance
App
Behaviour that applies wherever you are — money defaults, alerts, AI.
FinancialNotificationsAI & Integrations
Privacy & data
The lock, the encryption, your backups and your data.
Privacy & SecurityData Management
Modules
Optional features. Each tab owns the switch that turns its module on.
Categories & BudgetsRules & TagsKakeiboPassword Manager
About
Version, licences and where the numbers come from.
About
Vertical settings stay with their vertical
Settings that belong to one feature — the vault's export and import, the NRI residency facts, the freelance GST profile — deliberately stay inside that desk, next to the data they govern. Only the things that apply across the app live here.
Every control here does something
A control that saves a value but changes nothing looks identical to a working one in a screenshot, so the settings screen was audited key by key against the code that reads it. Anything the app could not honour was removed rather than left on screen — if you see a toggle here, something consults it.