Training data disclosure

Yes, unless you opt out. Prompts and completions sent through our endpoints may be used to train our own models. Opting out takes effect on your next request and stops all future content retention for your account.

The switch is in your dashboard. It is disclosed on the plans page and in the signup terms before your first key is issued, and flipping it has no effect on service quality or price.

The end state is domain-specific small models that answer coding questions well enough, cheaply and privately enough, that customers with sensitive data never have to ship their prompts to a frontier lab. The scarce input for that is honest, well-routed, real-world coding traffic, which our users generate.

We would rather fund that with your voluntary consent than by selling the service short behind fabricated research claims.

• prompt and completion text of your API requests, including tool-call payloads;
• routing metadata — which tier answered — plus timing and cache statistics;
• you are not identified in any model output by name, account, or by code you have submitted, and we do not publish datasets containing your content.

• your request content stops being stored by us; billing metadata continues, because it is needed to run the service;
• content already used in a training run cannot be un-learned. Deleting the source material from our stores does not retroactively remove gradients from trained weights. This is the honest limit of an opt-out and we state it plainly;
• deleting your account erases retained content within 30 days.

Each cohort report discloses the consent rate within the cohort, the share of traffic used for training, and the upstream retention terms we rely on. No per-user rows are ever published.