Step 01
Step 1
Pick your language from the eight supported; the app, voice and notifications update together.
AccountRetail
Settings, locale & device management.
Language, accessibility, notifications, security — all on one screen.
The problem
Why this exists.
Settings UX is where good apps go to die. We want one screen, three sections, no surprises.
Locale, security, and notification preferences should be reachable in one tap, with the most-changed item at the top.
How it works · 3 steps
From input to outcome.
- Step 02
Step 2
Configure biometric / PIN / TOTP from the security section.
- Step 03
Step 3
Tune notification categories and inbox digests independently.
Under the hood
The models and routes behind it.
Models called
No models cite this feature directly — backing logic is deterministic Python.
API routes
- GET /api/v1/settings
Compliance posture
- Settings changes land in audit-trail.
- Locale state is bound to the account, not the device — sign in elsewhere and your language follows.
- DPDP §12 — preferences are erasable with your account.
What it's not
Settings tune your experience; they do not change what Mukodi remembers about you. For that, see your-memory.
Related · features & stories