Privacy notes for AgentOS

Open-source, self-hosted runtime

AgentOS is released under the Apache License 2.0, as are the extension packs in its registry, its guardrail packs and its skills; its storage dependency, @framers/sql-storage-adapter, is MIT. It ships as a TypeScript package you run on your own infrastructure. The runtime does not phone home, collect analytics, or send end-user data to Frame.dev. It sends prompts and documents only to the services you configure, such as LLM, embedding, speech and search providers, and keeps data in memory or in the storage you connect. Packs that run a local model, such as the PII pack's NER tier, download the model files from Hugging Face the first time they run.

You control data collection

Because the runtime is self-hosted, privacy obligations sit with the operator. When you build a product on top of AgentOS you must define how conversation history, workflow telemetry, or marketplace records are stored, how long they are retained, and which third parties (if any) have access.

Recommended practices

• Document what you log (e.g., agency launches, persona submissions) and why.
• Implement opt-in analytics and give end users a way to delete or export their data.
• Review marketplace submissions before publishing to avoid unlicensed content or personal data.
• The Marketplace class in AgentOS keeps listings, reviews and installs in memory. If you persist them, give them the same retention and deletion rules as your other user data.