Back to Blog

Engineering

Data managementAccount isolationRecord lifecycle

How ISEA manages records, conversations, and attachments

Does deleting a chat remove its records? Why do photos load later on a new device? Follow a meal entry to see how ISEA stores your data.

ISEA Team

A meal card shows what you ate and a photo. ISEA stores the record and image separately. If you created it through AI, the conversation has its own storage too. Your phone also keeps local details such as download progress.

That is why deleting a chat does not automatically remove all its records, and why a record can finish syncing before its photo has downloaded.

Records have stable identities

Business records have stable identifiers, types, timestamps, and documents. Expenses, journals, and water logs share record conventions while retaining their own field requirements.

Each record's ID distinguishes an edit from a new entry. ISEA also keeps the event time separate from the save time. If you log yesterday's lunch today, it should still count toward yesterday.

Forms and agent tools follow the same field rules, so their records can be queried, summarized, and synced together.

Local copies and account isolation

The current client maintains a separate local database for each account. Screens read locally, while synchronized business data connects to the cloud through the sync path. Account switches close the previous connection and finish local work before opening the target account's space.

The server also checks ownership against verified identity. Knowing a record ID does not grant access to another account's record.

Local-first establishes availability and data-location boundaries. It is not automatically an end-to-end encryption guarantee. AI requests, record sync, and file uploads each have their own processing scope.

Different kinds of data

DataMain purposeImportant boundary
Business recordsQuerying, editing, summaries, and reviewActual writes determine what exists
Conversation historyExchanges and tool resultsSeparate server-history and client-cache paths
Personal memoryLasting facts and preferences with sourcesNot a search index of all conversation history
Device stateNotification registration, caches, local progressDoes not all need to move to another device

Deleting a memory does not automatically delete the conversation that mentioned it. Clearing a chat is not equivalent to deleting every business record. Each action has its own stated scope.

Images have a separate lifecycle

A record uses an attachment ID to find its file. The location of a photo on one phone cannot be used directly by another device.

References, uploads, and downloads are therefore handled separately. Retrieved files are checked for integrity. This explains why text may appear before a photo on a new device.

A synchronized record does not mean every attachment is already available offline on that device. A complete backup needs to collect the required attachments in its scope.

Deletion, recovery, and derived state

Business records use deletion markers so sync and recovery can recognize the change. Recovery operations remain subject to record state and version rules.

A deletion marker does not mean every historical cloud archive has been physically erased. Backups, conversation history, and account deletion have separate scope and retention rules. Disappearance from a list is not proof that all copies are gone.

Caches, search indexes, and notifications are built from your records. After a restore, they need to be cleared or rebuilt so reminders and search results do not keep pointing to old data.

Next: local records, sync, and AI requests.