Checked on every change. On the record.

• Every pull request passes the project’s CI and security scans, then an AI security review that fails closed: no verdict, no merge, and the merge is pinned to the exact version reviewed. A guard on the main branch refuses to deploy anything that went around the gates.
• Bring your own model subscription or API keys, or run local models. They live with your PP Orchestrator, never in the instance (only the optional voice key does).
• Coding agents run on your laptop, a VPS or on-prem: then the cloud instance never needs your source on our machines. If you choose the PP Orchestrator we run for you, the agents work on our machines instead.
• Self-host: wherever you run it. Cloud: one private instance in Germany (EU), with the database in Frankfurt. AI calls go only to the models you route to (voice, if on, goes to ElevenLabs); self-hosted with local models, no AI call leaves your premises. What we read from a cloud instance to run it: see below.
• From a cloud instance, only what we need to run it, and we pull it: the instance never sends us anything on its own. Every 5 minutes, a health check. Once a night, a usage summary: number of members; AI spend this month, in total and per model provider (calls, tokens, cost, and whether the key is yours or ours); last activity; release; e-mail mode; whether a PP Orchestrator is connected, its version and its health (queue, response times, memory, disk); when the first sign-in, completed training lesson, project, build, accepted requirement, merged pull request, deploy and feedback to Product Printer happened, with counts; trial events (AI credit used, plan chosen); and the answers to the day-7 in-app question (a 0–10 score and "what's missing", without the author). Every hour, keyed hashes of member e-mail addresses (never the addresses), so "find your instance" can e-mail a sign-in link. While we include AI credit (in a trial), we also read its spend and set its cap. Never project content, requirements, code, client data or the user list. On our cloud these reads are part of the service and cannot be switched off. A self-hosted instance answers them only if you set its read key (INSTANCE_OPS_READ_SECRET); without it, it answers no one.
• Export your whole instance at any time — it is yours either way.

Found a security issue? Write to [email protected].