Privacy Policy

Scope

Minifield Labs is an independently operated project. This policy describes data processing across its website, documentation, hosted platform, and runtime reporting service.

Website and documentation

Cloudflare delivers our static pages and routes application requests. Delivery services receive connection information, such as an IP address and the requested URL, to serve requests and protect the service.

The website and documentation don't use advertising cookies or a visitor-tracking SDK. Documentation search runs in your browser against a downloaded search index.

Accounts and workspace content

When you sign in, WorkOS handles authentication. The platform stores your account identifier, email address, display name, workspace membership, and session information to provide access and enforce permissions.

The platform stores the product definitions, trajectories, saved wording, training inputs, job records, and artifacts you choose to create or submit. It uses them to run the requested workflow, preserve version history, and recover interrupted jobs.

If you request AI-generated wording, the configured model provider receives the trajectory's trigger text and the requested number of variations. The request asks the provider not to store the completion. Returned wording and its provenance are retained for review and recovery.

Training workers receive the inputs selected for the job. Hosted workflows can therefore process submitted data on our servers and configured execution services.

Local inference and Observer

Local inference processes model inputs on the device running the model. The application embedding a Minifield package controls its own storage, synchronization, and host callbacks.

Observer scans local trace files on your Mac. It keeps masked findings and keyed fingerprints locally. Revealing a finding reads its value from the original log and holds it temporarily while the finding is open.

Runtime metrics

The browser runtime and native command-line runtime enable operational reporting by default. Reports describe inference duration, token counts, model identity, execution backend, and coarse device information. Browser reports can include browser and operating-system families, browser major version, website origin, and configured application labels.

Runtime reports exclude prompt text, generated text, tool arguments, and error messages. Browser reporting omits credentials and the referrer. The receiving service still handles connection information needed to accept the request.

Integrators can disable reporting or use their own receiver. See telemetry configuration for the available controls. Native library hosts choose whether to install a reporter.

Use and service providers

We use information to deliver requested features, authenticate users, enforce permissions, recover jobs, secure the service, and measure runtime operation. We don't sell personal information or use it for advertising profiles.

Cloudflare provides delivery and routing. WorkOS provides authentication. Configured model providers and execution services process the inputs needed for the workflows you request. Their processing locations and policies depend on the service in use.

Retention

Account and workspace records, version history, submitted job inputs, and artifacts remain in persistent storage to support the platform's workflows and recovery. The current service doesn't apply one fixed expiry period to these records.

Raw runtime records have a 30-day retention period. Aggregated operational metrics have a 12-month retention period. Locally cached model files remain until you clear them through your browser settings.

Cookies and browser storage

See the Cookie Policy for sign-in cookies, the sidebar preference, cached model files, and browser controls.

Contact and privacy requests

Contact the operator at [email protected] with privacy questions or requests to access, correct, or remove personal information. We review requests under applicable law and confirm your authority before disclosing or changing records.

Some records can need to remain for security, legal obligations, or another person's rights. We explain any applicable restriction when responding to your request.

Policy changes

We update this page when our data processing changes. The date above identifies the current version.