Privacy notice

This draft names, at a category level, the processors and data categories involved in operating this website and warden. It does not yet state retention periods, legal bases, or a complete subprocessor list — those are pending legal completion.

This website (wardenruns.com)

• Netlify — hosts this static site and stores the submissions from the early-access form.

The product (warden)

• Clerk — handles account authentication for the operator console.
• Stripe — processes payments for paid plans. [Whether warden stores payment details itself, or Stripe handles them entirely as the payment infrastructure behind Clerk, and the resulting role allocation, are to be completed by the operator and legal review.]
• AI / model providers — warden sends parts of your repository and issue text to third-party AI model providers to plan and generate code changes. [The full list of model providers in use is to be completed by the operator.]
• Repository and project-management providers — warden reads from and writes to the repository host and issue tracker you connect it to. [The full list of connected providers is to be completed by the operator.]
• Audit evidence — records of what a run did — its declared scope, the gates it passed, and its validation output — are kept as audit evidence. [Retention period is to be completed by the operator and legal review.]

What isn't finished yet

[Data-subject rights process, a retention schedule per category, the legal basis for each processing activity, and a complete subprocessor list are pending completion by the operator and legal review. For the Stripe payment processor named above, the payment-data categories collected, the purpose and legal basis for that processing, the role allocation between warden, Clerk and Stripe, any international-transfer mechanism, and a link to Stripe's own privacy information are also pending completion. This notice is not a final privacy policy.]

Questions

Send privacy questions through the contact page.