Privacy policy

Last updated: 24 September 2026. Operated by Venkatesh M K.

Plain-language description of how the service actually operates. It is provided for clarity and is not legal advice.

What CIPatch reads

• Workflow files under .github/workflows/, and the dependency manifests needed to recognise a safe caching recipe.
• Actions metadata: runs, jobs, runner labels, step names, timestamps and conclusions.
• Repository and installation identifiers, and your GitHub account login.

What CIPatch does not read

• No repository secrets, ever.
• No Actions logs in this version. Log parsing is out of scope.
• No application source code. Only workflow YAML and dependency manifests are fetched.

What is stored

Repository identifiers, workflow paths, run and job timings, runner labels, proposals, pull requests, outcome windows, and audit records. Workflow snapshots are used to compute a patch and are not retained as a copy of your repository.

What is never stored

• Card details. Payments are handled by Stripe on their hosted pages; CIPatch never sees a card number.
• Your GitHub private key or installation tokens beyond their lifetime: installation tokens are short-lived and cached in memory only.

Retention

Run and job observations are retained to measure before-and-after results. Retention is capped by plan (30 days on Free, 90 days on Starter, one year on Team and Organization), after which observations are rolled up into aggregates and the raw rows removed.

Subprocessors

• GitHub — source of the repositories and Actions data.
• Render — application hosting.
• Neon — managed PostgreSQL.
• Stripe — payment processing, once billing is enabled.

Uninstalling

Uninstalling the GitHub App stops all access; installation tokens are discarded and the installation is marked deleted. Delete requests: support@releasedge.com.

Your rights

Export or deletion requests: support@releasedge.com. Every finding is exportable by design; CIPatch does not hold your data hostage to keep you as a customer.