Conduit · Miraland Labs

Privacy Policy

Version 1 · effective 14 September 2026 · applies to the Conduit service operated by Miraland Labs

What we collect

Account data: email address, display name, password hash, organization name and slug. Work data: objectives, plans, delivery packets, verification evidence, pull-request references, audit events, and the computers and agent lanes an organization connects. Payment data: the facilitator-verified payer wallet address and the settlement reference of each term. We never store a payment proof, a signed transaction, a wallet signature or a private key.

What we do not collect

Conduit does not read repository contents into its own storage, does not hold model provider credentials beyond what an organization deposits for its own use (encrypted at rest), and does not train models on customer content.

Why we process it

To run the service an organization asked for: plan and dispatch work, verify deliveries, record decisions, enforce seat and subscription limits, and send the transactional messages the service requires — email verification, a subscription receipt, and one renewal reminder seven days before a term ends. We send no marketing.

Where it lives and for how long

Data is held on infrastructure operated by Miraland Labs and its providers. Conversations with the Conductor assistant and screenshots attached to them are deleted after 30 days. Account and work records are kept while the organization exists and for a reasonable period after, then deleted on request.

Who can see it

Members of your organization, according to the roles the Owner assigns. Miraland Labs staff, for operating the service and resolving problems. Model providers, to the extent an organization routes work through them. No one else, unless the law requires it.

Your rights

You may ask what we hold about you, ask for correction, or ask for deletion. Write to the address on the Enterprise & contact page. Where data-protection law grants you further rights, they apply.

Cookies

Conduit's console uses a session cookie and a CSRF cookie to keep you signed in and to protect your account. It sets no advertising or analytics cookies.