Privacy Policy

When you sign in, we collect your GitHub identity — name, email, and avatar — via OAuth. When you connect a repository, we collect its metadata (name, default branch, visibility) and, in order to scan it, its source code content. When you connect a vendor integration (Vercel, Sentry, Resend, and others), we collect and store the credentials you provide, encrypted, in Supabase Vault. We also collect usage analytics through PostHog to understand how the product is used.

Connected repositories are cloned to ephemeral, isolated workers for the duration of a scan or fix job and are not retained after the job completes. Before any content leaves that worker, a secret filter strips out .env files, API keys, and other credential-shaped values. The remaining, filtered excerpts relevant to a given finding are sent to Anthropic's Claude API for analysis — this is how Prodward generates readiness findings, explanations, and fix suggestions. Per Anthropic's policy, data submitted through the API is not used to train their models.

Scan results, readiness reports, and related findings are retained for as long as your account and the associated connection remain active, so you can track progress over time. You may request deletion of your account and associated data at any time by contacting us — see Your rights below. An organization owner can self-service delete the entire organization at any time from Settings → Danger zone — this takes effect immediately and cannot be undone; deletion requests sent by email to support@prodward.com are processed within 30 days.

You have the right to access, correct, delete, and export the personal data we hold about you. To exercise any of these rights, email support@prodward.com. If you are located in the European Union or Turkey, we acknowledge and honor the rights afforded to you under the GDPR and KVKK respectively, including the right to lodge a complaint with your local supervisory authority.

Data is isolated per organization with row-level security (RLS) at the database layer. Vendor credentials are stored in an encrypted credential vault and are never exposed in plain text to the application layer. Inbound webhooks from vendors are verified with HMAC signatures before being trusted. Prodward never writes directly to a default branch — every change lands as a pull request for you to review.

Prodward uses only essential session cookies to keep you signed in (via Supabase Auth). Product analytics (PostHog) runs cookieless: it stores no cookies and no identifiers in your browser. We do not use advertising cookies or sell data to third parties for advertising purposes.

We may update this policy from time to time; material changes will be reflected by updating the "Last updated" date above. Questions about this policy can be sent to support@prodward.com.