Privacy Policy

Last updated: April 3, 2026

1. Information We Collect

Account data: Email address, username, and hashed password when you register. Optional two-factor authentication (TOTP) secret if you enable 2FA.

Git provider data: Personal access tokens (encrypted), git identity (name and email), repository metadata (names, paths, branches, descriptions) accessed through GitHub, GitLab, or Bitbucket APIs.

Session data: Chat conversation history (messages, tool calls, token usage), workspace state snapshots (git diffs, untracked file archives, agent session files), and container activity logs.

API credentials: Anthropic API keys, OpenAI API keys, OAuth tokens (Claude and ChatGPT subscriptions), and webhook endpoint secrets — all stored with Fernet symmetric encryption.

Usage data: Token usage per session (input, output, cache tokens), model selections, session duration, and cost estimates. Browser push notification subscriptions (VAPID endpoints).

Analytics: We use PostHog for product analytics (user actions, session creation, feature usage). We use Sentry and BetterStack for error tracking and log aggregation.

2. How We Use Your Information

• Service operation: Running containerized workspaces, executing AI agents, managing git operations, delivering webhook notifications, processing cron job schedules
• Authentication: Verifying your identity, managing sessions, enforcing email verification and two-factor authentication
• Communication: Sending verification emails, password reset links, and push notifications when sessions complete
• Analytics: Understanding feature usage to improve the Service

We do not sell your personal data to third parties. We do not use your code or conversation content to train AI models.

3. Code Processing

Your code is cloned into isolated Docker containers per session. Code content is sent to the AI provider you configure (Anthropic's Claude API or OpenAI's API) for analysis and modification as you direct. We do not access, review, or process your code outside of providing the Service.

Container workspaces are ephemeral and destroyed after idle timeout. Workspace state (diffs and untracked files) is captured before cleanup and stored in encrypted S3-compatible object storage (Hetzner Cloud) to allow session resumption. This state data is deleted when the session is permanently cleaned up.

4. Credential Storage and Security

All sensitive credentials are encrypted at rest using Fernet symmetric encryption (AES-128-CBC with HMAC-SHA256). This includes:

• Git provider tokens (GitHub, GitLab, Bitbucket PATs)
• AI API keys (Anthropic, OpenAI)
• OAuth credentials (Claude and ChatGPT subscription tokens and refresh tokens)
• Webhook endpoint secrets
• Repository environment variables

Credentials are decrypted only when injected into container environments at session start. Encryption keys are stored separately from the database.

5. Container Security

Each session container runs with:

• Dropped Linux capabilities (CAP_DROP ALL) with only minimal caps for process management
• no-new-privileges security option
• Dedicated Docker network with iptables rules blocking access to internal/private IP ranges
• Configurable memory and CPU limits per container
• Environment variable filtering against a security blocklist (prevents PATH injection, LD_PRELOAD, etc.)
• SSRF validation on custom git host URLs and webhook endpoints

6. Third-Party Services

We use the following third-party services to operate the platform:

• Anthropic (Claude API) — AI agent functionality. Subject to Anthropic's usage policies
• OpenAI — AI agent functionality. Subject to OpenAI's usage policies
• GitHub / GitLab / Bitbucket — Repository access via APIs with user-provided tokens
• Hetzner Cloud — S3-compatible object storage for workspace state and email content
• Resend — Transactional email delivery
• PostHog — Product analytics (EU data center, PostHog privacy policy)
• BetterStack — Log aggregation and error monitoring
• Sentry — Error tracking

7. Data Retention

• Account data: Retained while your account is active
• Conversation history: Retained to provide continuity of service; deleted when you delete your account
• Container workspaces: Destroyed after idle timeout (configurable, default ~30 minutes)
• Workspace state (S3): Retained for session resumption; deleted when sessions are permanently cleaned up
• Sent emails: HTML content stored in S3; retained for audit purposes
• Webhook delivery logs: Last 50 deliveries per endpoint retained
• Audit logs: Retained for security purposes

8. Data Location

The Service infrastructure runs on European servers. Object storage (Hetzner S3) is located in the EU. Analytics data (PostHog) is processed in the EU. Email delivery (Resend) may process data in the US.

9. Your Rights

You have the right to:

• Access, correct, or delete your personal data
• Export your conversation history and account data
• Withdraw consent for data processing
• Disconnect git provider integrations and delete associated tokens
• Clear all push notification subscriptions
• Delete your account and all associated data

To exercise these rights, contact us at [email protected].

10. Cookies

We use session cookies for authentication (Django session cookie). We use a CSRF token cookie for security. We do not use advertising or tracking cookies. PostHog uses a first-party cookie for anonymous analytics which can be opted out of.

11. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be communicated via the email address associated with your account.

12. Contact

For privacy-related inquiries, contact us at [email protected].