---
title: "Security checklist"
description: "Review data boundaries before loading, executing, saving, or sharing a recipe."
---

> 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.

# Security checklist

## Before execution

- Identify whether input contains secrets, customer data, tokens, or private logs.
- Inspect every operation for network behavior.
- Prefer the local workspace or page-local WebMCP for sensitive data.
- Start with a representative subset rather than a complete dataset.

## Before sharing

- Remove embedded input from deep links.
- Replace keys, identifiers, and hostnames with safe fixtures.
- Review recipe arguments for secrets.
- Open the final link in a clean browser profile.

## Cryptography

Serialize is useful for inspection, interoperability, and reproducible transformation. Legacy algorithms such as RC4 may be present for analysis but should not be selected for new security designs. Follow the relevant protocol and organizational requirements for production cryptography.

> **Do not paste secrets into remote prompts**
>
> The public standard MCP endpoint is read-only and needs no recipe input. If an external assistant asks you to send sensitive data elsewhere, stop and use the local workspace instead.

Source: https://help.serialize.dev/reference/security/index.mdx