Step 01
Step 1
Open Your Memory in the app; see every captured fact with source turn and timestamp.
AI InsightsRetail· marketing-claim · scribe-shadow-mode
Your memory, your rules.
See, edit, and erase everything Mukodi has remembered about you — per record.
The problem
Why this exists.
Every AI app says it remembers you; few show you what.
A user who cannot see and erase per-fact memory cannot give meaningful consent — DPDP §6 specificity is structural, not cosmetic.
How it works · 3 steps
From input to outcome.
- Step 02
Step 2
Edit a fact you disagree with; erase it with a tap.
- Step 03
Step 3
Pause capture entirely from /settings/security — Mukodi stops adding new memory until you resume.
Under the hood
The models and routes behind it.
Models called
API routes
- GET /api/v1/me/memory
Compliance posture
- DPDP §6 — capture is consent-flagged; minors are short-circuited entirely.
- Per-record erase under §12 — no blanket 'erase all my memory or none'.
- Capture audit log surfaces under audit-trail.
Interactive demo · mocked at the edge
See it work.
Ask Saraswati (mock)
Loading the demo…
What it's not
Memory is per-user retrieval, not per-user model weights. The underlying ML weights are shared across users; what we remember about you is yours alone.
Related · features & stories