Privacy Policy
Effective Date: October 31, 2026
1. Introduction
Welcome to Sofuu. Sofuu is a general-purpose runtime for AI — built to run anywhere from servers to smart devices — distributed as a single binary. Its runtime core is open source under the MIT License, and the QTSQ memory engine is open source under the Apache License 2.0 (see the Terms of Service). Because Sofuu is designed as a private, local-first execution engine on your own hardware, the Sofuu project does not collect, process, track, or store your code, session context, vector memories, or personal credentials.
2. Zero Telemetry & Local Execution
The Sofuu binary executes 100% in-process on the host machine. Unlike many contemporary developer tools and CLI assistants, Sofuu contains zero built-in telemetry, zero user analytics, zero crash reporting phone-home pings, and zero background tracking daemons.When you run sofuu run without a network tool, your code and data remain inside your process boundary. When you call a cloud model provider or a remote memory adapter, the data you send is transmitted to the endpoint you configured — that is described in sections 3 and 4.
3. Continuous Memory (QTSQ) & Session Mesh
By default, semantic memories, conversational context, and project session history managed by sofuu.memoryand the session mesh are stored on your own disk in .qtsq containers encrypted with AES-256-GCM. The key is machine-local: Sofuu generates ~/.sofuu/brain.key (32 random bytes as hex, mode 0600) on first use, or reads the key from SOFUU_BRAIN_KEY if you set one for CI or a fleet. The session mesh syncs only sessions on the same project on the same machine; it is not a cloud service. A brain file that only the older fixed password can open is reported as legacy, backed up, and re-encrypted with the machine-local key on its first write.
Memory adapters are opt-in. If you explicitly open a remote adapter — Qdrant, Pinecone, pgvector, or a custom object of your own — the records you write through that handle are sent to the backend you configured, subject to the R7net.allow / net.denypolicy. The local-first statement above applies to the default QTSQ backend, not to data you choose to route to an external service; that service’s privacy policy then governs it.
4. Local Inference vs. Third-Party AI Services
Local inference (experimental): When running models on-device via sofuu infer orsofuu.ai.streamLocal, the engine reads the model file from disk and generates tokens in-process; it does not contact a model provider. Network access only happens if your own code makes it.
Cloud and network providers: When using sofuu.ai.stream() or sofuu.ai.complete()with a provider — OpenAI, Anthropic, a llama.cpp server, or any OpenAI-compatible endpoint you configure — prompts are dispatched directly to the endpoint with the API key in your configuration. Sofuu does not proxy, inspect, log, or intermediate those requests. Your data handling with those providers is governed by their respective privacy policies.
5. Plugins, Tools & Sandbox Safety
Plugins, MCP servers, and toolpacks executed by autonomous agents run in-process and are subject to the R7 policy surface. When a policy file is active, filesystem reads and writes are confined to fs.roots (or, when fs.roots is unset, to the project working directory). Network egress is open by default: it is restricted only once you set a non-empty net.allow (then only those hosts are reachable),net.deny always wins, and net.enabled: false blocks all egress. SSRF protection for private and loopback addresses is opt-in through net.ssrf: true. Sandboxed evaluations also carry a fuel budget and a wall-clock deadline, so a runaway script fails as an exception instead of hanging the process.
These controls are only as strict as the policy you load. With no policy file, the sandbox still meters fuel and deadlines, but filesystem and network limits are those of your operating system account. A plugin you allow broad roots or broad net.allow entries can reach those destinations — review the policy before running untrusted code.
6. Website Logs & Cookies
Visiting sofuu.xyz does not set third-party tracking cookies or deploy invasive marketing pixels. Basic, non-personally identifiable server logs (such as request timestamps and HTTP status codes) may be generated by Cloudflare edge infrastructure strictly for DDoS mitigation, service availability, and security purposes.
7. Contact Us & Social
If you have questions, feedback, or security inquiries regarding this Privacy Policy, please reach out via:
- Email: hello@sofuu.xyz
- Official Twitter / X: @sofuu_runtime (https://x.com/sofuu_runtime)
- GitHub: github.com/sofuu-runtime/sofuu