Privacy

The software

Mojulo is a local substrate — a SQLite database and a process supervisor on your own hardware. It is keyless: your agent installs it from npm and runs it on localhost. Because of that:

• No external telemetry. Mojulo does not report usage, crashes or metrics to anyone, and makes no analytics or "phone-home" calls. There is no install to register and no account to create. The software does keep one local log of its own tool calls: each row holds the tool name, start time, duration, status, the argument names and their sizes (never the values), truncated error text, and the MCP client's name, version and session id. It lives in the database under ~/.mojulo/, rows older than 30 days or beyond 50,000 are deleted at startup, it never leaves your machine, and MOJULO_MCP_TELEMETRY=off turns it off. The log is described in the plugin README.
• Your data stays local. Recipes, images you attach, and every artifact you mint — objects, worlds, games, exports — live in a SQLite file and folders on your machine. The maintainer never receives them and has no ability to access them.
• Inference is yours. The reasoning runs on the agent you already run, through your own LLM-provider relationship and key. Mojulo does not proxy your prompts through any service of the maintainer's. The one opt-in exception to "the agent does the reasoning" is mint_solid with via:'prompt', which sends its prompt to the provider you name, with your own key, and to nobody else.
• The MCP surface is loopback-only. Mojulo's control plane binds to localhost and is not exposed to the network. It is reachable by agents running on the same machine, not by anyone reaching in.
• Nothing is fetched until you ask. Starting the server makes no network call. Network access happens only on a named action, and none of it carries your content: installing from registry.npmjs.org; an anonymous version lookup when your agent calls check_for_updates; the mojulo-ui dashboard from npm, once, when you open it; and the optional search runtime (npm) and its model (huggingface.co), only through mojulo install recall. Outside the Claude plugin build there are two more: an explicit render with no browser installed downloads Chrome for Testing from storage.googleapis.com, and the first MP4 encode with no ffmpeg installed downloads a SHA-256-pinned ffmpeg from GitHub releases. The plugin build never downloads a browser, ffmpeg or the model on its own. The full list is the table in the plugin README.

ChatGPT and Codex plugin

The official mojulo plugin for ChatGPT and Codex runs the mojulo package inside the execution environment OpenAI provides to you. Mojulo does not operate a remote service for the plugin, and the maintainer does not receive your prompts, conversation history, uploaded files, recipes, generated geometry, exports, or other plugin content.

• Personal data collected by mojulo: none through the plugin. Mojulo requires no account and does not collect names, email addresses, IP addresses, ChatGPT conversation history, or other personal information from plugin use.
• Purpose of use: because mojulo does not receive this data, the maintainer does not use it for analytics, advertising, profiling, training, or any other purpose. Data processed locally by mojulo is used only to perform the 3D task you requested.
• Recipients: mojulo does not transmit plugin content to the maintainer, and does not sell or share it with third parties. Your use of ChatGPT or Codex is governed separately by OpenAI's terms and privacy practices. Network requests needed to install the mojulo npm package go to the package registry, as described above.
• Retention: mojulo retains no plugin data on infrastructure operated by the maintainer. Mojulo's workspace files and local tool-call log remain in your execution environment. The log keeps rows for up to 30 days or 50,000 rows, whichever limit is reached first, as described above.
• User controls: you can delete mojulo workspace files and generated artifacts from your execution environment. The local tool-call log can be turned off with MOJULO_MCP_TELEMETRY=off. Uninstalling the plugin stops any further use of mojulo through it.

What this covers — the official package

Everything above is a statement about the mojulo the maintainer publishes: the official build, which is the mojulo package on npm the Claude plugin (plugins/mojulo) and the ChatGPT and Codex plugin (plugins/mojulo-chatgpt), each of which runs that same package pinned to one version, built from the source at github.com/zombico/mojulo, installed and run on your own hardware. That is the build whose behavior the maintainer can answer for, and the guarantees on this page are guarantees about it.

Mojulo is open source under Apache-2.0, and that license deliberately lets anyone fork it, modify it, redistribute it, or run it as a service for other people. Those are legitimate uses of an open license. They are also outside the maintainer's control, so they are outside this policy:

• A modified build is its author's software. A fork can add telemetry, add an account, or send your data somewhere — and can still be called mojulo. If you did not install it from npm or build it from the published source, the promises on this page are not the ones that apply to it; the party who gave it to you owes you their own answer.
• A hosted mojulo is somebody else's service. If a third party runs mojulo on their infrastructure and gives or sells you access, your prompts, your recipes and everything you mint are on their servers — that is what hosting means, whatever this page says. Their privacy policy is the one that governs. The maintainer is not a party to it, receives nothing from it, and can see nothing of it.
• The maintainer hosts nothing today. There is no official mojulo cloud, no managed instance, no paid tier, and anything sold as one now is not the maintainer's — not affiliated with, endorsed by, or vetted by the maintainer.
• The permanent commitment is the package. The open-source mojulo stays open source and has no external telemetry; that is not a policy that gets revised. It does not forbid an official hosted mojulo built on ordinary cloud services. If there is demand for one, it is something the maintainer may explore — as a separate service with its own privacy policy, announced as such, leaving this policy and the package it describes unchanged.

The check is the same one the rest of this page rests on: install it yourself and read it. The source is public and the release you installed is the one this policy describes.

What you host

When you export something you built — a self-contained HTML file, a Godot project, an app — and put it where people can reach it, it runs on infrastructure you choose: your machine, your cloud account, a static host. Mojulo is not in that path and receives nothing from it.

Any personal data that flows through a thing you built and hosted — visitor traffic, form submissions, messages — is processed on your infrastructure, under your control. The maintainer does not see it. Obligations to the people whose data passes through (notice, consent, retention, deletion) are yours; see the Terms.

This website

mojulo.ai is a static, informational site. It has no login, no account, and no user-generated content.

• No cookies, no cross-site tracking. The site sets no cookies and embeds no third-party trackers, ad pixels, or social widgets.
• No analytics, no off-site requests. Fonts, styles, and every other asset are served from this site itself. Opening a page makes no request to any third party — no analytics service, no CDNs, no ad networks, no social widgets. Check the network tab; it should show only mojulo.ai.
• Outbound links (GitHub, npm, and the like) go to services with their own privacy policies, which govern once you leave this site.

Contact

Mojulo is published by Franz Ombico ("the maintainer"). If you email through the contact link, we receive your email address and whatever you write, and use it only to reply. We do not sell, rent, or share it.

Questions about privacy: hello@mojulo.ai.

Found a security issue in the software? Use GitHub's private vulnerability reporting rather than a public issue — the process is in SECURITY.md.

Changes

Effective 2026-10-02. This policy may be updated as the site changes. The version in force is the one published here, with the date above.