Browser-local checking. Separate server-side API.

RunSAVE processes the graph you type or paste in browser memory. The six checks, diagram, report download, and Agent NEXUS preparation note are produced locally. This browser workflow does not upload the graph for analysis.

The Provider Lab link contains the fixed marker source=runsave. It does not contain the graph, report, system name, endpoint, labels, or digests, and the browser is instructed not to send a referrer. Ordinary hosting and security infrastructure may still process request metadata needed to serve either page.

Calling the key-protected endpoint at runsave.dev/api/v1/analyse sends your declared graph to RunSAVE for processing on its hosting infrastructure. Use public or synthetic graphs only. Do not send secrets, personal data or confidential architecture. The application does not save graphs or reports, use them for training, or log request bodies or beta keys.

A single aggregate database row stores the current minute/day and request counts to enforce shared quotas. It contains no graph, report, API key, account, IP address or user identifier. Counter windows are replaced as new requests arrive; hosting backups may retain prior counter states. Hosting and security providers may process operational metadata under their own security, legal and service settings.

Browser graphs and reports exist in browser memory for the current session. API graphs and reports exist in server memory for request processing; memory/OS erasure is not guaranteed. Files you download remain on your device and under your control. RunSAVE has no application-saved graph record to retrieve or delete.

Email xeolite.app@gmail.com about information under the operator’s control. Do not attach credentials or a confidential architecture graph. Any future analytics, uploaded storage, or research submission will require an updated notice and consent review before use.