Privacy

Your data stays with you

• Projects are files on your disk. No hosted workspace, no automatic sync.
• Mock servers run on your machine, on localhost. No round trip through a third-party service.
• The response history is an archive placed next to your project.
• Secrets are never written into the project: they live in a local file or in the system’s environment variables. See Secrets.
• Code actions run in a WebAssembly sandbox, with no access to your file system.

The firewall

Restorm intercepts all of its outbound calls — yours as well as its dependencies’ — and blocks by default anything that does not come from a URL in your project, asking you for authorisation.

This is the most concrete guarantee on offer here: a third-party library cannot call a remote service without your seeing it. See Firewall.

What does go out

Traffic	When
Your requests	When you send them — that is the whole point of the tool
Update check	At start-up and every four hours, can be disabled in the settings
Entitlement check	Only if you are signed in to an account
Import by URL	Only when you trigger one

Update calls are exempt from the firewall; every other one is subject to it.

AI driving

The MCP server listens only on the loopback interface and requires a process-specific token. It never starts on a machine with no display.

An agent receives the resolved value of your secrets, just like the rest of the application — it drives Restorm on your behalf. Every call is recorded in the MCP logs.

One thing to know: run_request genuinely calls the target. It is your MCP client’s approval flow that acts as the safeguard — keep it on.

The full policy

The service’s privacy policy is published at restorm.app/privacy.