DevGenie works in your own repository, on your machine. The DevGenie service receives only what a command sends it. It does not reach into your repository.
What a command sends
- Instructions requests. Most commands ask the service for their instructions. These requests can include the project name, a stack hint and the requested build scope.
- Your architecture document, for rating.
/devgenie:gatesends the architecture document so the service can rate it. The service does not store the document. The signed rating result includes a hash of the document, binding the result to the text that was rated. - AgentDev evaluation evidence, if you use the judge.
/devgenie:agent-sliceruns and records your evaluations in your project. If you use the service's evaluation judge, the evaluation evidence is sent to it for a verdict.
What the service keeps
- Your account and plan, managed through the DevGenie portal. Payment details are held by Stripe.
- Decisions you record. When a command records a decision to your project's audit trail, the record is kept so it can be verified later. The decision's description and who made it are encrypted by the service; deleting their encryption key makes those details unreadable.
- Token usage, if you send it. The project metrics hooks can send per-task token counts with your email address and machine name, for cost reporting.
- First use. For a paid account, the date of its first successful DevGenie tool call.
Request logging is off unless we switch it on to investigate a problem. When it is on, it records the tool used, an account or key fingerprint, the plan and scope, a digest and size of the arguments, the outcome and timing. It does not store what you sent.
Questions
Email support@smartgenie.co.uk.