Privacy

Codela gives AI coding agents a memory of what went wrong in production. To do that it needs some of your data. This page explains, in plain words, what we collect, why, who helps us process it, and what you control.

What we collect

• Your GitHub identity when you sign in: your GitHub ID, username, name, profile picture and primary email address. We don't get your GitHub password.
• Repository data for the repos you choose: the code changes in your deploys and pull requests, and your deployment history. We read it and never change your code. The only thing Codela writes is its lesson files (.codela/, plus a line in CLAUDE.md and a section in AGENTS.md), through pull requests that merge automatically by default. You can switch them to review, or turn them off, in Settings.
• Monitoring data from the tool you connect (SigNoz, Datadog, New Relic, Grafana or Sentry): latency, error rates and traces around each deploy. Your read-only keys are stored encrypted.
• What Codela produces: lessons, deploy check results, pull request warnings, and usage counts such as how often Claude Code loaded your lessons.
• Billing details if you subscribe: Stripe handles payment. We store your Stripe customer and subscription IDs, never your card details.
• Product usage: which pages you visit and steps you take (for example signing up, connecting a tool, starting a trial), so we can see what works. On our public pages (home, pricing, integrations) we may record anonymous session replays with all typed input hidden; we never record the dashboard or Settings. We don't send your code, lessons, repo names or keys to our analytics.

How we use it

• To check your deploys, write lessons, deliver them to your Claude Code sessions and warn on pull requests that repeat one.
• To run your workspace: sign-in, your team, settings and billing.
• To email you about your account, such as a welcome email when you sign up. We don't send marketing email or share your address.
• To keep Codela working and secure, and to understand our own costs.

We don't sell your data. Your lessons belong to your workspace and are never shown to other customers.

Who helps us

We use a small number of trusted providers to run Codela:

• An AI provider analyses code changes and monitoring data to write lessons and check pull requests. We send only what each analysis needs.
• An analytics provider (in the US) counts product usage, as described above.
• Hosting providers run the Codela service, its database and this website.
• GitHub handles sign-in, repository access and pull request comments, through the Codela GitHub App.
• A payment processor handles payments.
• An email provider sends account emails.
• A monitoring provider watches Codela's own service so we can keep it running.

Each provider only gets what it needs for its job. For a current list of the companies we use, email hello@usecodela.com.

What you control

• Choose which repos Codela can see, and change them anytime on GitHub.
• Delete any lesson from your dashboard.
• Disconnect GitHub or your monitoring tool, or uninstall the Codela GitHub App, at any time.
• Delete your workspace and all its data yourself, from Settings → Delete this workspace, or ask us by emailing hello@usecodela.com.

Security

Keys and tokens are encrypted at rest, GitHub access uses short-lived tokens limited to the repos you pick, and connections to Codela are encrypted in transit. No system is perfectly secure; if something goes wrong that affects your data, we'll tell you.

Changes and contact

If we change this policy in a meaningful way, we'll update this page and tell active customers. Questions: hello@usecodela.com.