Privacy Policy
This policy explains how MapConductor (“we”, “us”) handles information when you use the MapConductor Studio website and its optional MCP connection.
Information processed during an MCP connection
- A one-time pairing code is generated in your browser and held temporarily by the relay service until it is used or expires.
- When you pair a preview, project source, console output, map state, and requested preview actions are relayed between your browser and the AI tool you selected.
- Relay data is held in memory for the active connection and is not stored as project content after the connection ends. The pairing code expires after 10 minutes and is single-use.
Usage metrics
We collect anonymous aggregate operational metrics such as browser sessions, pairings, tool-call counts, error counts, connection durations, and daily unique-client counts. Source code, console output, pairing codes, and IP addresses are not included in the stored daily metrics. IP addresses may be processed transiently for rate limiting and abuse prevention.
Information you choose to provide
If you contact support, we receive the information you include in that message. The Studio playground does not require an account for MCP preview pairing.
Third-party services
Your chosen AI client (for example, Codex) processes the information you ask it to use. A project may also load map tiles, fonts, or other resources from providers selected by the project author. Those providers have their own policies.
Security and retention
We use HTTPS, short-lived pairing codes, origin checks, request limits, and connection timeouts. Aggregate metrics are retained for operational reporting for as long as reasonably necessary. No security measure can guarantee absolute security.
Your choices
You can disconnect an active MCP session from Studio at any time. You can also stop using the service without creating an account.
Contact
For questions about this policy, visit MapConductor support.