Privacy & data.

This page describes the data handled by the PACT sandbox application.

Your browser

A temporary test-wallet key is generated in browser memory. The application does not send that private key to the server or store it in local storage. A reload discards it. Transaction signatures and the public wallet address are sent to the sandbox service.

The session

An HTTP-only cookie identifies a server-side session for up to two hours. The service keeps the associated public wallet address and session expiry in memory. IP addresses are used in short-lived rate-limit records to protect the faucet and planner. There are no third-party analytics or advertising scripts in this build.

Your instruction

The text you submit to the AI planner is processed by a model hosted on the PACT server. The app does not send it to an external AI API or intentionally retain the prompt in an application database. Infrastructure and model processes may produce operational logs. Avoid including secrets or personal information.

On-chain records

Test transactions, public addresses, recipients, budgets and permissions are recorded on the sandbox chain. They are readable through supported RPC calls. This is not a private transaction system. The chain resets when its service restarts.

Exported files

Receipt downloads are created in your browser. They contain public test-chain transaction information, not the temporary private key. You control those files after download.

Sandbox scope

The service uses valueless demo tokens and is provided for experimenting with agent permissions. It is not connected to real funds, mainnet execution or guaranteed financial outcomes. The contracts are experimental and have not received an independent audit.