Turning off conversation history should remove the chats stored on your device immediately. In Nkomo, switching history off purges that on-device history at once, while cloud consent remains a separate control over what may be sent for processing.
Imagine Ama, an invented composite, standing in her kitchen in Kumasi at 10:40 p.m. Her mug has gone cold beside the sink. Earlier, she used Twi and English in the same conversation to work through a tense family money matter, including names, amounts and words she would hate to explain out of context.
Now her cousin needs to borrow the phone.
Ama turns off conversation history, then hesitates. If those chats remain visible until some unclear future date, handing over the phone could expose a private disagreement before the family has settled it. She checks again. The old conversations are gone from the device. Only then does she unlock the door.
“Off” should describe what happens now
A history switch makes a promise. Most people read “off” as a change in the present, not a request that might take effect after an unspecified retention period.
That expectation becomes sharper when the conversation is personal. A Twi voice note about debt, a Ghanaian English draft about work, or a mixed-language exchange about someone’s health can carry meaning far beyond the words on screen. Who can see it matters. So does when it disappears.
Nkomo keeps conversation history on the device under your control. When you turn history off, that local history is purged immediately. You should not need to guess whether yesterday’s chats are still sitting behind another menu or waiting for a later cleanup.
This does mean giving up the convenience of reopening those conversations on the device. That is a real tradeoff, and the setting should make it clear. Privacy controls work best when the consequence is understandable before you tap.
Local history and cloud consent solve different problems
Deleting visible history answers one question: what remains stored on this device?
Cloud consent answers another: what may reach the cloud for processing?
Nkomo presents three cloud-consent choices: never, ask each time, or this session. Those choices let you decide before sharing something sensitive. Turning off local history does not rewrite an earlier cloud decision, so the safest moment to think about cloud consent is before you speak or type the private detail.
Ama’s late-night check covers the phone she is about to lend. If she plans another sensitive conversation tomorrow, she still needs to choose the cloud setting that fits that new exchange. The two controls belong side by side in her mental checklist:
- Decide whether this conversation may reach the cloud.
- Decide whether its history should remain on the device.
- Export anything you need before removing it.
- Delete the account if you want the broader account-level action.
For a fuller comparison of those last choices, see Should You Export, Delete Your Nkomo Account, or Purge Local History?. If the cloud options feel easy to mix up, The Three Cloud Choices That Decide Where Your Mother’s Voice Note Goes walks through them in a family setting.
Privacy controls need visible consequences
A reassuring label carries little weight if the result stays hidden. After a privacy action, you need to know what changed.
That is why immediate local purging matters. The empty history becomes confirmation you can see. Nkomo also avoids silent failure: when an error occurs, it is shown rather than swallowed. A failed action should not leave you assuming private material disappeared when it did not.
This principle reaches beyond one app. Ghana’s rejection of a health-data agreement over privacy and sovereignty concerns reflects the same underlying demand at a larger scale: people need meaningful control over sensitive information, with clear boundaries around where it goes and who governs it.
For an individual holding a phone, that principle becomes wonderfully practical. Tap the setting. Observe the result. Know what the action covered.
Make the privacy decision before the next conversation
The next morning, Ama keeps history off while she drafts a short message in the mix of Twi and English she naturally uses. She holds to speak, hears the reply and interrupts when she wants to change the wording. When she finishes, there is no old local transcript waiting for her cousin to stumble across.
Before your own next sensitive chat, pause for a few seconds. Choose whether cloud processing is allowed, decide whether local history should stay on, and export anything you cannot afford to lose. Then verify the result on the device.
That small check is the difference between hoping a privacy setting worked and knowing what changed when you touched it.
Comments
No comments yet.