Can you really delete what an AI knows about you?

Imagine an assistant bringing up an old detail at exactly the wrong moment.

It remembers that you were considering a move, but the plan changed months ago. It still describes a colleague as your manager after you changed teams. The sentence is not dangerous because it is dramatic. It is dangerous because it sounds settled, and you no longer know where the assistant learned it or how to make it stop using it.

“Your data stays on your device” does not answer that problem. A private black box is still a black box.

For a digital twin, the harder promise is not merely we store memory. It is you can see which memory exists and remove the part that is wrong.

Memory should have a visible shape

DT Life does not treat everything it has seen as one mysterious personality blob. Different records have different jobs: recent accepted replies provide working context, remembered facts describe people and the user, commitments track promises, chat sessions preserve conversations, diary entries hold days, library passages support document answers, and optional Presence records build the Rhythm view.

That separation makes the controls more specific.

When chat suggests a new long-term fact or an observed routine, it enters a review queue. You can choose Remember or dismiss it instead of allowing the suggestion to become unquestioned memory. Remembered details about a person are listed in Interactions, where one detail can be removed or replaced, or the whole interaction can be forgotten along with that person’s stored details. Older facts remain searchable in the memory archive and can be forgotten one by one.

Conversations, diary days, library documents, career applications and generated draft history have their own deletion controls. Deleting a diary day also removes its searchable library copy. Removing a library document deletes the text and vectors DT Life indexed, while leaving the original file on disk alone.

For optional screen observation, a single screen note can be deleted, all observation data can be purged, and Forget the last hour reaches the derived Rhythm material and deletes any diary day composed from that period together with its searchable copy—not only the first sample visible in the interface.

Deleting the source and deleting the conclusion are different

This is the part most “delete” buttons hide.

A conversation and a fact learned from that conversation are different stored records. Removing a remembered fact does not necessarily mean every chat line that once mentioned it has also disappeared. Deleting generated draft history does not delete twin chats, learned memories, preferences or calendars; the Data & privacy screen says so beside the control. Forgetting an interaction in DT Life also cannot erase the original message from an email or chat app.

If the goal is to correct what the twin should use, remove or replace the memory. If the goal is to erase the underlying record too, review the relevant conversation, diary, library or observation control as well.

That is less magical than a button labelled “forget me,” but it is more honest. The interface can name what will be removed and what will remain before the user confirms.

Local and encrypted are separate promises

The sensitive database fields—chat text, learned facts, diary entries, job notes and window titles among them—are protected with AES-256-GCM. The key is sealed to the user’s Windows account with DPAPI rather than stored in plaintext beside the database.

Encryption protects a copied database, a disk read from another account or a backup that leaves the machine. It does not replace deletion, and it does not protect against every program already running as the same Windows user. A record can be encrypted and still be unwanted. Ownership requires both protection from outsiders and controls for the person inside.

There is no single erase-everything button today

DT Life currently uses scoped controls rather than one dashboard action that wipes every category at once. That reduces the chance of deleting years of memory while trying to clear one history, but it also means a complete cleanup takes more than one step.

This matters when someone is handing a PC to another person, leaving a job or trying to remove every trace of a sensitive period. They should not assume that deleting draft history also cleared chats, the library and the job tracker.

The honest answer to “Can I delete what it knows?” is therefore: yes, the memories and source records are inspectable and forgettable, but deletion has a scope. Read that scope, remove related layers when necessary and keep the decision in the hands of the person the memory describes.

See DT Life’s privacy model and controls →