DebugAI/privacy
Legal

Privacy Policy

Last updated: April 12, 2026

What leaves your machine — and what doesn't

During indexing: When you index your workspace, file content is sent over HTTPS to DebugAI servers where it is chunked and sent to Voyage AI for embedding generation. Code chunks and their embeddings are stored in your project index on our servers. Only files you choose to index are sent — never your full filesystem, git history, or secrets.

During debugging: The error message, a relevant code snippet, and optionally the names of recently modified files in your git repository are sent for AI analysis. File contents beyond the retrieved snippet, commit history, and diff text are never sent.

When idle: Nothing is sent. No background scanning. No telemetry on your codebase. API keys are stored in VS Code's encrypted SecretStorage — never in plaintext.

1. Who we are

DebugAI ("we", "us", "our") operates the website at debugai.io, the DebugAI VS Code extension, and related APIs. This policy covers all of these services (collectively, the "Service").

For privacy questions, contact us at privacy@debugai.io.

2. Data we collect

CategoryWhatWhy
AccountEmail, name (via Clerk — Google, GitHub, or email sign-in)Authentication, daily usage tracking, support
Indexed code chunksCode chunks from files you index in VS Code, plus their embeddingsStored in your project index on our servers to retrieve relevant snippets when you debug. Scoped to your account — never shared with other users.
Debug requestsError message + relevant code snippet per requestSent to AI for analysis. Cached short-term, then deleted
Git contextNames of recently modified files in your git repository (file paths only — never file contents, diff text, or commit history)Helps the AI understand which files are relevant to the error. Sent only when a git repository is detected. Not stored beyond the debug session.
Usage analyticsProduct events: debug sessions, fix applied, limit hit — no code contentProduct improvement, feature prioritization
Error trackingStack traces from DebugAI itself — never from your codeBug fixing and reliability

3. What we do NOT collect

4. How your data is processed

Workspace indexing

  1. You run "Index Workspace" in VS Code.
  2. The extension reads each file and sends the content over HTTPS to DebugAI servers.
  3. The server chunks the content and sends chunks to Voyage AI for embedding generation.
  4. Embeddings and code chunks are stored in your project index in our database, scoped to your account.

Debug analysis

  1. You press Ctrl+Shift+P in VS Code.
  2. The extension extracts the error message and retrieves relevant code snippets from your project index. If a git repository is detected, it also collects the names of recently modified files (paths only).
  3. This data is sent over HTTPS to the DebugAI API.
  4. The API forwards it to Claude (Anthropic) for analysis.
  5. The response is cached short-term, then automatically deleted.
  6. The fix is returned to your VS Code extension as a diff preview.

5. Subprocessors

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

ServiceCategoryRegion
AnthropicAI inferenceUnited States
Voyage AICode embeddingsUnited States
ClerkAuthenticationUnited States
PostHogProduct analyticsUnited States / EU
SentryError monitoringUnited States
RailwayInfrastructure hostingUnited States
Stripe (planned)Payment processingUnited States

6. Data retention

7. Your rights

If you are in the European Economic Area (EEA), United Kingdom, or another jurisdiction with data protection laws, you have the following rights:

To exercise any of these rights, email privacy@debugai.io. We will respond within 30 days.

8. Legal basis for processing (GDPR)

9. Cookies

We use strictly necessary cookies for authentication. PostHog may set analytics cookies. We do not use advertising cookies or sell data to third parties.

10. Security

All data is transmitted over HTTPS/TLS. API keys are stored in VS Code's encrypted SecretStorage. Server infrastructure is hosted on Railway with managed PostgreSQL and Redis.

11. Children's privacy

DebugAI is not directed at children under 16. We do not knowingly collect data from children. If you believe a child has provided us with personal data, contact us and we will delete it.

12. Changes to this policy

We may update this policy from time to time. We will notify users of material changes via email or an in-app notice. The "Last updated" date at the top reflects the most recent revision.

13. Contact

For privacy-related questions or data requests: