Skip to content

Privacy policy

Shortand plain.

No accounts, no email, no tracking cookies, no analytics of our own.

In your browser

The manifest you write in the studio is kept in this browser's local storage until you clear it, so a reload does not lose it. The wallet you last connected is remembered the same way. Downloads (the manifest file) are created only when you press the button, on your device.

On our server

The server reads the rail's public events from Robinhood Chain and sends the same full list to every visitor, so it cannot tell which agent you look at. Chain reads pass through a relay that counts requests per network to keep the shared quota fair; those counters expire within minutes. The server never receives a key, a manifest or anything you type in the studio. The hosting provider keeps its own access logs, which include IP addresses.

On chain

Launching an agent, queueing tasks, approving, pausing and every run are public transactions. The manifest itself is not published by Launiq: only its hash, unless you put a link to it in the manifest URI.

The runner

The runner runs on your machine. It talks to the Robinhood Chain RPC you configure and to the HTTPS sources named in your manifest. It sends nothing to Launiq.

Third parties

Reads go to the Robinhood Chain RPC, which sees your IP address. Links to the explorer, the launchpad and X take you to their sites and their policies. No analytics, no tracking cookies, no accounts, no email.