---
title: "Local-first data model"
description: "Understand where data is processed and how to handle sensitive input safely."
---

> Documentation Index
> Fetch the complete documentation index at: https://help.serialize.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Local-first data model

Serialize's interactive workspace and page-local WebMCP recipe execution run inside the browser page. This is the preferred path for sensitive local data because the recipe input is not sent to Serialize's public MCP endpoint.

## What stays local

- Text or files placed in the workspace
- Intermediate and final recipe output
- Page-local `serialize_run_recipe` execution
- Workflows saved to browser storage

## Important exceptions

Some operations are network-capable by their nature. Inspect an operation before using it with confidential data, especially fetch, DNS, URL, or external lookup operations. Deep links can include both workflow and input data in the URL, so review a link before sharing it.

## Standard MCP boundary

The public endpoint at `https://serialize.dev/mcp` accepts catalogue search and exact operation-name description requests. It does **not** accept recipe input and cannot execute recipes.

> **Treat links as data containers**
>
> If you include input in a deep link, anyone who receives the link can read that input. Use recipe-only links for sensitive workflows.

Source: https://help.serialize.dev/getting-started/local-first/index.mdx