DARKOZA / OERSI

Privacy information for the pilot form

Last updated: 27 October 2026.

What is collected

The form collects the name and email you provide, optional team/company and HTTPS repository URL, your project objective, consent, and a submission timestamp. The service does not request passwords, access tokens, private keys, repository content, or payment details. IP addresses are used in memory for rate limiting and are not written to the lead file or application logs.

Why and who can access it

Darkoza uses these details only to evaluate and respond to the requested engineering pilot. Submitted records are stored on Darkoza's production server in a directory restricted to the dedicated pilot service account and administrators. Submissions are not sold or published. A repository URL is stored as text only; the form handler does not fetch it or attempt to log in.

Retention

Records older than 90 days are purged by a daily server task. The same cleanup runs before a new request is stored. If a contract or legal obligation requires different retention, that requirement may apply to related records.

What happens after submission

Submitting is not a purchase, does not grant repository access, and does not trigger repository analysis. Scope and read-only access must be agreed separately. No payment details are collected on the pilot page.

Questions or deletion requests

For an access, correction, or deletion request, use the pilot form and start the objective with “PRIVACY REQUEST”; use the same contact email as the original request and identify its approximate submission date. The request will be handled manually. Do not include passwords, tokens, private keys, or confidential source code.

Return to the pilot · Darkoza homepage