Quick reviews and your data

What is uploaded, who can open review links, and how access expiry differs from data retention.

Quick reviews and your data

No account required does not mean no data is processed. After upload approval, Doomer receives source snapshots, task context, and the agent’s finding responses. Treat review links as private. Read about uploads, link access, and retention.

What leaves your machine

After you approve uploads, the skill uses the Doomer CLI to send source snapshots, task context, and the agent’s finding responses to Doomer’s hosted service. A snapshot can include repository files beyond the changed lines; quick review is not local-only processing.

The CLI also sends its running version and protocol metadata for compatibility notices. The service processes technical information such as IP addresses and diagnostic metadata as described in the privacy policy.

Each developer approves uploads for their own agent. Committing the skill shares instructions; it does not grant teammates’ upload permission.

A no-account quick-review link carries an access key. Anyone with the complete link can view its hypotheses and recorded responses, which may describe your code. Treat the link as private and share it only with people who should see that information.

Browsing the uploaded source requires signing in and owning or claiming the review; possessing the review link alone does not grant source-browser access.

Expiry and retention

An unclaimed no-account review has a seven-day access window, refreshed when the same review is submitted again. Claiming a review or linking its installation to your account removes that no-account expiry.

Link expiry is an access rule, not a promise that source snapshots and all related data are deleted after seven days. The privacy policy describes retention by purpose; it does not specify a fixed deletion period for every data type. For a deletion request or a retention question about your repository, contact [email protected].

Model training

Doomer’s privacy policy states that private source code and private artifacts are not used to train general-purpose models unless you expressly agree to that use.

Your choices

You can decline setup or upload approval. To stop using Doomer in a chat without changing your team’s committed skill, use the opt-out prompt.