Security and data handling at PRFactory
PRFactory orchestrates AI-assisted development from the EU and never runs your AI agents. The AI agents and your model subscriptions stay on your own machines, where your code is checked out and changed. The server keeps the workflow: tickets, plans, questions, answers, reviews, the diffs submitted for review, and the approvals.
What runs where
On your machines
the AgentTeamForge worker (atf)- Every AI agent. Claude Code, Codex and the other CLI agents run on the developer's machine.
- Your model subscription. Agents authenticate locally with the account you already have.
- Your source code. Agents work in a git worktree on the machine and push the branch to your Git platform.
- The connection direction. The worker calls the server to claim work. The server never connects to your machine.
On the PRFactory server
prfactory.dev · EU- Workflow state. Tickets, phases, the work queue and the recorded plan and test plan approvals.
- Workflow artefacts. Plans, questions and answers, test plans, reviews, the diffs submitted for review and agent output shown on the ticket.
- Integration credentials, encrypted at rest, used to read tickets and open pull requests.
- No agent execution. No AI agent runs in the server process.
- No model API calls and no model API keys. The server holds no LLM credential.
Where PRFactory runs
The application and its database run in the EU, on one private network.
| Service | Provider | Location | What it holds |
|---|---|---|---|
| Application | Zerops | EU Central, Prague (prg1) | The PRFactory web application and API |
| Database | Zerops PostgreSQL 16 | EU same project, private network | All workflow state and artefacts |
| DNS and edge proxy | Cloudflare | Global edge network | Traffic in transit to prfactory.dev and app.prfactory.dev |
| Sign-in | Logto Cloud (OIDC) | EU Netherlands | Your sign-in identity |
| Transactional e-mail | AhaSend | EU Netherlands | Outgoing notification e-mail |
| Payments | Stripe | Ireland; may transfer to the US | Card, billing and subscription data. PRFactory never sees the card number. |
Sub-processors
PRFactory's sub-processors are Zerops, Cloudflare, Logto, AhaSend and Stripe.
GitHub, Bitbucket, Azure DevOps and Jira are integrations you authorise, not sub-processors.
How your data is protected
- Encrypted credentials. Integration tokens and other secrets are encrypted at rest with AES-256-GCM. The key lives only in the production service's environment, never in the repository.
- Encrypted in transit. Every connection to prfactory.dev and app.prfactory.dev is HTTPS, with TLS 1.2 or later.
- Browser protections. A content security policy is enforced on every page.
- Human approval before anything merges. The agents never merge on their own.
Retention and deletion
You can ask for your data to be deleted by writing to [email protected]. Daily backups, kept for up to 3 months.
GDPR and DORA
GDPR. PRFactory is hosted in the EU. Your repositories are checked out and changed on your own machines, and the AI agents run there too; the server holds the workflow around the code. PRFactory (org.nr 556939-4777) is the data controller for account and billing data, and the processor for the workspace content you put into the Service, under our Data Processing Agreement, which is part of the Terms of Service, so accepting the Terms accepts it.
DORA, for regulated financial customers. PRFactory does not run your code or your agents, so the ICT service it provides is workflow orchestration and its record. Plan and test plan approvals are recorded on the ticket, and an override of the plan completeness check is recorded with the person who made it.
Certifications
PRFactory holds no security certification today.
Report a security issue
To report a security issue, write to [email protected]. We acknowledge every report within 2 business days. The same contact is in our security.txt file.
See what runs where for yourself
Connect one machine and one repository, and watch the first ticket run.