Data and privacy

What Mirage Console reads, stores and sends, and what it never does.

Mirage Interactive collects no data through Mirage Console. The package has no analytics, no telemetry and no tracking, and never connects to Mirage Interactive or to any server of its own: Mirage Interactive receives, stores and processes nothing of what your game, your players or you do with it.

What can leave the device

  • Nothing, unless you set a webhook URL in the settings and a log is sent: with the Send button, send-log, or MirageConsole.Execute("send-log") from your code. It then goes straight from the device to that URL, and nowhere else.
  • What a send holds: the lines of the log chosen, or a Profiling recording; the message written before sending, if any; the name and version of the project, the version of Unity, the platform, the kind of build, the id and version of Mirage Console; when the log was taken, with the offset of the device's clock from UTC. See the fields.
  • sysinfo and the Profiling tab read information about the device (model, operating system, processor, memory, graphics, screen, language). They only display it; it only leaves the device in a log or a recording you send.
  • The logs may contain personal data: whatever your game logs (names, identifiers, addresses...) ends up in them, and so in what is sent.

What is stored

  • The settings asset holds the webhook URL, its authentication header and the hash of the password of the protected commands. It goes into the builds where the console is active, where anyone who extracts the assets can read it.
  • The Editor keeps the authorization of a machine for the protected commands in its preferences, on that machine only.

Your responsibility

You choose whether the webhook is used, where it sends, and what is sent. The server, service or workflow that receives the data (your own, or a third party's such as Slack, Discord or n8n) is chosen, configured and operated by you or under your control, not by Mirage Interactive. You are therefore solely responsible for:

  • its security: access to the URL and to its credentials, transport encryption (https://), protection, retention and deletion of the data it receives;
  • the terms of use of the third-party services you send to;
  • the compliance of what you send with the laws that apply to you and to your players, data protection laws included (such as the GDPR): the legal basis for sending personal data, and informing the people concerned, in particular when the console is active in a build you distribute.

To the extent permitted by applicable law, Mirage Interactive is not liable for the data you send with Mirage Console, nor for the security, availability or use of the servers and services that receive it. This page does not replace nor limit the terms of the Unity Asset Store End User License Agreement, under which the package is licensed.