Know where mission
data goes.

01: SCOPE

A policy for local installations.

This notice describes the current FieldWeaver source code when you run it yourself. The project maintainers do not operate a hosted FieldWeaver service or receive your mission data. If someone else hosts an instance for you, that operator's practices also apply.

The application is simulation software. It is not designed to receive personal, confidential, or safety-critical information.

02: LOCAL PROCESSING

What the application handles.

• The browser sends mission text, selected scenario, mode choices, and run seed to the configured FieldWeaver API.
• The API returns a validated mission specification, simulation frames, metrics, and event trace to the browser.
• The backend keeps the latest run in memory for /api/evaluations/latest. Restarting the API clears that in-process value.
• The evaluation script can write a report under the local ignored artifacts/ folder.
• Normal backend request logs include method, route path, status, duration, and request ID. Unexpected exceptions include a stack trace. Protect local logs and generated reports as you would other project data.

03: LIVE INFERENCE

Live mode sends data to the selected provider.

When the compiler or agent is set to live, or to automatic mode while a backend key is configured, the backend calls the selected provider's Chat Completions endpoint. Mission compilation sends the mission text and a public summary of the selected scenario. Event-driven agent calls send a bounded observation summary, such as the current estimate, team centroid, safety state, and allowed action list. A server-configured key is not sent to the browser. A key entered in the browser remains in page memory and is sent to the backend for each live request.

Baseten's published security practices currently describe Zero Data Retention for its Model APIs inputs and outputs. The applicable service, configuration, account agreement, and current provider terms govern a real request. FieldWeaver does not configure or guarantee provider retention on your behalf.

04: BROWSER STORAGE

No app analytics or saved user profile.

The frontend stores one preference in local storage: whether tactical audio is muted. It does not set application cookies or load an analytics tracker. Browser requests go to the configured API origin. The browser and hosting platform may still create technical logs outside this project.

05: YOUR CHOICES

Keep control of your instance.

• Use Offline mock mode to avoid sending prompt and observation content to a model provider.
• Do not enter credentials, personal data, or confidential material into mission text.
• Keep the API on loopback unless you have secured the deployment and its network path.
• Review and remove local logs and evaluation artifacts according to your own retention needs.

For a locally operated instance, direct access or deletion requests to that instance's operator. The project itself has no central user account or data store to search.