# Claude connector privacy and security

> Exactly what the quelltest Claude connector and cloud sync send (test names, scores, flagged locations) and what always stays on your machine.

Canonical page: https://quelltest.com/docs/connector/privacy

The connector and cloud sync send a sanitized subset of your readiness report (test names, confidence scores, flagged reasons, file and line locations, and the score) and never your source code, test bodies or docstrings. Sync is opt-in and can be audited and deleted from the command line. This page lists exactly what is sent, how it is enforced, and how to remove it.

The design rule is that **your source code never leaves your machine.**

## Does Claude see my source code?

**No.** The connector only receives a privacy-safe subset of your Quell report. Here is exactly what it can see:

| What Claude sees | Example |
|------------------|---------|
| Test names | `test_payment_rejects_zero_amount` |
| Confidence scores | `94` (0–100) |
| Confidence tiers | `HIGH` / `MEDIUM` / `LOW` |
| Flagged item locations | `src/billing.py:42` |
| Flagged item reasons | `external API: stripe.Charge.create()` |
| PRS score | `71/100` |
| Edge case counts | `23 total, 8 written, 3 scaffolded, 2 flagged` |

## What never leaves your machine

| What stays local | Why |
|------------------|-----|
| All source code | Your implementation logic |
| All test bodies | The actual `assert` lines Quell wrote |
| All docstrings | Your documentation |
| Variable names inside functions | Runtime state |
| Full file contents | Only `file:line` references are synced |
| Git history and diffs | Not relevant to the connector |
| Environment variable values | Never collected |

## Enforcement

The sanitizer (`quell/sync/sanitizer.py`) is the only code path that can produce an outbound sync payload. It enforces an allowlist — any field outside the allowlist raises `SanitizationError` before the network call is made.

The full published schema: [quelltest.com/docs/sync-payload](https://quelltest.com/docs/sync-payload)

## Audit what was sent

```bash
quell sync status --privacy
```

```
Sync enabled: yes (Pro tier)
Project: payments-service
Last push: 2026-06-07 10:00:00
What gets sent: test names, confidence scores, flagged reasons, PRS, file:line
What stays local: all source code, all test bodies, all docstrings
View full schema: https://quelltest.com/docs/sync-payload
```

## Connector auth vs LLM auth

Connecting to Claude.ai is **independent** from enabling LLM fallback in the CLI.

- Connecting the Claude connector does **not** enable `quell find --use-llm`
- You can use the connector without ever enabling LLM fallback
- They are separate opt-ins requiring separate authentication

## Delete your data

```bash
quell sync unlink
```

This sends a `DELETE /v1/projects/:id` to `api.quelltest.com` and removes all synced reports. Claude will immediately lose access. The local sync history is also cleared.

## Sync is always opt-in

`sync = false` is the default in `[tool.quell]`. Quell never auto-syncs.

```toml
[tool.quell]
sync = false  # default — must explicitly opt in
```

You must either set `sync = true` in config or pass `--sync` explicitly on each run.
