Privacy notice

Pilot intake can include your work email, company, optional product URL, target type, priority-scenario description, consent time, a keyed network identifier, and a limited user-agent string. Do not submit passwords, access tokens, customer personal data, or confidential build material through the public form.

If a pilot proceeds, Mirage can receive the authorized build or target details, task specification, synthetic-user inputs, screenshots, rendered text, action traces, checks, findings, usage records, and operator correspondence described in the written scope.

We use intake information to review fit, prevent abuse, respond to you, agree scope and commercial terms, operate the pilot, prepare the report and PDF, and hold the review call. The current landing site does not use the request as consent for a general newsletter.

The intake database, hosting platform, email or notification service, sandbox provider, and model provider can process information needed for their role. During a pilot, screenshots, rendered text, and approved task context may reach the model provider named in the written scope. Provider or sandbox regions and commercial terms are confirmed during scoping when relevant.

Mirage does not sell pilot-request data or use it for third-party behavioral advertising. We may disclose information when required by law or to protect the service and its users.

Each pilot is delivered in a dedicated private workspace, not a shared customer tenant. Access is limited to the engagement and the providers needed to operate it. A dedicated workspace does not keep model inputs inside the sandbox, which is why the provider path is disclosed before a run.

The public intake service does not currently enforce automatic deletion. Intake records remain until an operator removes them or you request removal. A commissioned pilot can use a separate evidence-retention period stated in its written scope. Infrastructure providers may retain security logs or backups under their own documented schedules.

The current landing implementation does not set marketing or analytics cookies. Hosting and security providers may still create ordinary request logs needed to deliver and protect the site.

You can ask what intake information Mirage holds about you, correct it, or request removal. We may need to verify that the request comes from the same work email. Legal or security obligations can require limited retention after a request.