Step 01
Step 1
Approve push for the categories you want — safety, goal, partner update, app announcement.
AccountRetail + B2Bpartial· marketing-claim · fcm-push
FCM push + email + SMS inbox.
Get the right kind of nudge — push for safety, inbox for everything else.
The problem
Why this exists.
Notification spam is a tax on attention. We want to send fewer notifications and have each one matter.
Push needs to be opt-in per category; inbox is the durable record that survives a missed push.
How it works · 3 steps
From input to outcome.
- Step 02
Step 2
Everything also lands in an inbox you can review at your own pace.
- Step 03
Step 3
Quiet hours apply to push; the inbox is unaffected.
Under the hood
The models and routes behind it.
Models called
No models cite this feature directly — backing logic is deterministic Python.
API routes
Internal-only — no public route handler.
Compliance posture
- FCM token never seen by Mukodi outside the FCM transport.
- DPDP §6 — push categories are individually consented and revocable.
- Inbox is part of the user account and erased under DPDP §12.
What it's not
Push delivery depends on the device and the network — we surface a copy in the inbox so the message is not lost when push is offline.
Related · features & stories