Skip to main content
PraisonAI runs on your machine and sends your prompts and data only to the LLM provider and tools you configure — the project itself never receives them.

Quick Start

1

Keep data on your machine

Point the agent at a local model — nothing leaves your network.
2

Guarantee telemetry is off

Telemetry is already off by default. Set this to make the opt-out explicit and override any programmatic enable:

Where Your Data Goes

PraisonAI is a pass-through library: it does not proxy, store, or inspect your content on any PraisonAI-operated server. The data policy that applies to your prompts is the policy of the LLM provider you choose.

Telemetry

Telemetry is disabled by default. It only runs if you set PRAISONAI_TELEMETRY_ENABLED=true (or PRAISONAI_PERFORMANCE_ENABLED=true) or call enable_telemetry().
  • Event counts: agent runs, task completions, tool calls, errors, feature usage
  • Tool names and execution times (no arguments), error types (no messages), success flags
  • SDK version, Python version, OS type
  • A random session ID regenerated each run
GeoIP lookup is disabled.
  • Prompts, instructions, or LLM responses
  • Source code, files, or tool arguments and results
  • API keys or credentials
  • Personal data
Any of these wins over every enable setting:
See Telemetry for details.

Best Practices

Your prompts go straight to the provider. Check its retention and training-use terms, or use an enterprise/zero-retention plan.
Set llm= to an Ollama or other self-hosted model so content never leaves your infrastructure.
Web search, MCP servers, and API tools send their arguments to third parties. Leave them off for confidential work.
It guarantees no telemetry even if a library or script calls enable_telemetry().

Telemetry

What anonymous metrics are collected and how

Context Redaction

Strip secrets from context before it reaches the LLM