Back to Blog

Product guides

Local-firstPrivacyData scope

Local-first boundaries: records, sync, and AI requests

What happens on your device, what reaches cloud services, and why turning off sync does not disable all network processing.

ISEA Team

When you open a record already saved on your phone, you can read it without waiting for the server. ISEA uses the copy on your device for everyday viewing and editing.

AI, sync, and cloud backups still use online services. Here is what each one handles.

What works offline

You can view and edit saved records in screens that support offline use. If sync is enabled, those changes upload when your connection returns.

Cloud inference, attachments not yet downloaded, and cloud-only operations still need a connection. A local save also does not protect against device damage, app-data removal, or uninstalling the app.

Record sync is a separate path

When enabled, sync sends account-scoped business data to a cloud copy and other connected devices. Turning it off disconnects that path; it does not automatically delete data previously stored in the cloud.

The record-sync switch currently applies to records as a whole. There is no separate device-only setting for each record category. Check the app's settings for the available controls.

AI uses cloud services too

Local Agent executes tools on the phone, while inference still uses server and model services. Your messages and relevant tool results needed for a task may pass through that processing path.

Cloud Agent and Personal Agent run on the server using accessible account data. Turning off record sync does not remove cloud data already available to them. New phone-only edits remain unavailable until synchronized.

The record-sync switch is therefore not a master switch for all network capabilities.

Local-first and encryption answer different questions

Where data is stored first and who possesses the information needed to decrypt it are separate questions. Local-first does not establish end-to-end encryption or prove that a service provider can never access any content.

See the privacy policy for details about transmission, storage, access, and retention. Local-first describes how records are saved and used; some features still process data online.

Understanding an operation's scope

Ask what it reads, whether it uploads content, and where its result will be saved.

Records, chats, memories, attachments, and backups are stored separately. Before deleting something, check what the action covers. Deleting one kind of data does not automatically remove the others.

Continue with how ISEA manages data.