Privacy

Information we may process

• Account identifiers, email address, sign-in state, settings, tenant and principal bindings, and support details.
• GitHub account, installation, repository, pull request, changed source, review, commit, discussion, and status evidence for the source you select.
• Decision identity, source and snapshot identity, packet content, findings, uncertainty, required actions, your recorded disposition, runtime state, and recovery evidence.
• Commercial account binding, billing readiness, completed-Decision usage, payment-provider references, payment status, tax, dispute, and support records when commerce becomes available.
• Session, route, device, IP address, security, reliability, and audit information needed to operate and protect the service.

How we use it

• Establish your account and authority without treating an email address or GitHub identity as permission by itself.
• Read evidence from the repository and pull request you select, then produce and retain a Decision packet.
• Operate prepaid funding, reservations, completed-Decision accounting, spending limits, and eligible refund requests when enabled for your account.
• Prevent abuse, diagnose failures, recover uncertain operations, protect customer separation, and meet legal duties.

Providers and disclosures

• Codaegis policy is to use customer source and Decision content to provide, secure, support, and legally operate the customer’s service, not for unrelated product training or advertising.
• Codaegis uses service providers for identity, authorized source access, hosting, databases, model processing, logging, payment, email, security, and support. The provider list and retention details for customer access are not yet published.
• For model processing, Codaegis requests endpoints that do not retain source content or use it for training. These content limits are separate from providers’ service metadata and transient processing.
• A bounded analysis request may pass through configured model and hosting providers. Likely secrets are screened before analysis; the returned packet is designed to cite source rather than reproduce raw source unnecessarily.
• Codaegis does not store full payment-card details. Information may also be disclosed when law requires it, to protect rights or safety, or as part of a business transfer with appropriate safeguards.

Retention, export, and deletion

Account export and access closure are available signed-in controls. Access closure is not the same as deleting every retained record.

• Decision, usage, consent, security, tax, fraud, dispute, and audit records may remain where service integrity or law requires them.
• You should keep any records you need outside Codaegis.
• A prepared account export has its own displayed retention window. Applicable correction and deletion requests may still require identity, legal-hold, fraud, billing, and security checks.
• Revoking GitHub access stops future reads. It does not erase records that Codaegis is entitled or required to retain.

Your choices

• Codaegis does not sell personal information or use it for cross-context behavioral advertising.
• The service is intended for adults and is not directed to children.
• You can prepare an account export and close future account access from signed-in Account controls. Provider cleanup, backup ageing, and deletion obligations may continue separately.