Security and Data

Vesence is designed so your chats, added materials, Workspace files, and generated outputs stay on your computer — not in Vesence-owned storage.

Here's where your data lives and how the Vesence working environment operates from a security perspective.

The user's materials stay on the user's computer. Vesence does not store them.

Core idea

Vesence does not store the user’s chats or added materials.

The files, chat context, and work product used in a Vesence workflow exist locally on the user's computer. Vesence works with those materials through the Workspace, which is the storage and file system inside the chat's virtual computer.

Storage and processing are separate. To carry out a task, Vesence sends the relevant content to the AI model that processes it, the same way any AI assistant does. The model performs the work, but the user's files and chats are not kept in Vesence-owned storage — they remain local to the user's computer.

Where files are stored

Files added to Vesence are stored on the user’s computer.

This includes:

The Workspace is the local file area that Vesence uses while working on a task.

See: Vesence Workspace for more information.

Where chats are stored

Vesence does not store the user’s chats.

The chat exists as part of the user's local Vesence working environment. When the user gives instructions, those instructions are used by the local Vesence workflow and the chat's virtual computer to perform the requested task.

This means the chat context is tied to the user's environment, not stored as a separate Vesence-hosted chat database.

The virtual computer

Each Vesence chat has a virtual computer.

The virtual computer is the controlled working environment that Vesence uses to process files, run scripts, create outputs, and work with the Workspace.

The Workspace is the storage inside that virtual computer.

This matters because Vesence can work with real files in a structured environment without needing broad access to the user's computer.

Local hosting

The Vesence virtual computer is hosted locally on the user’s computer.

That means the working environment used by Vesence runs on the user's machine rather than in a Vesence-owned server.

The result is that the user's files and working materials remain local to the user's computer while Vesence performs the requested work.

Manage local storage

Because Vesence keeps workspace files in the browser on the user's own device, the user can see and manage exactly what is stored there. The “Browser storage on this device” screen lists each chat's stored files, how much space each one uses, and when it was last used.

From here the user stays in control: individual chats can be cleared to free up space, and the local SharePoint cache can be reset. Nothing here touches the organization's cloud storage or files on other devices — it only manages what is held locally in this browser.

Isolation from computer files

The Vesence virtual computer does not have access to all fileson the user’s computer.

It only works with the files that are made available to the Vesence workflow, such as files added to the Workspace or files accessed through an approved integration or workflow.

This isolation is important for security. Vesence can work with the materials needed for the task without having general access to the user's full file system.

Vesence can work with the files provided to it, but it cannot freely browse the user's computer.

Connected systems

When Vesence works with connected systems such as SharePoint, OneDrive, Outlook, Teams, iManage, or NetDocuments, access depends on the user's permissions and the relevant workflow.

Vesence can only work with connected-system material that is available through the user's access and made available to the Vesence task.

iManage and NetDocuments are optional document management integrations that an organization enables, and access follows the user's existing permissions in those systems.

For cloud and document management files, Vesence can stage changes for review rather than automatically publishing them. This keeps the user in control of what is changed, sent, or published.

Generated outputs

When Vesence creates work product, the output is saved in the user's local Workspace.

Generated outputs can include documents, summaries, redlines, checklists, spreadsheets, presentations, markdown files, scripts, or small tools.

These outputs belong to the user’s working environment and should be reviewed by the user before being sent, published, or relied on externally.

Why this is safe

The Vesence data model is designed around local storage and controlled access because:

• Vesence does not store chats.
• Vesence does not store added materials.
• Files exist on the user's computer.
• The virtual computer is hosted locally.
• The Workspace is a controlled storage area inside the virtual computer.
• Vesence does not have general access to all computer files.
• Vesence works only with materials made available to the task.
• External actions such as sending, publishing, or staging changes remain under user control.

More about security

For more about how Vesence protects data, see our Security page.