AI and data use

It applies when you use completions, chat, edits, agent tasks, or similar AI features in Eyeban or on related services that send context to a model.

To generate Suggestions, Eyeban may send your prompt, relevant code snippets or files, project metadata needed for context, and technical parameters (such as model choice and limits) to one or more model providers.

You control what you select or allow the agent to read. Do not include secrets, credentials, or regulated data unless you accept that they may leave your machine for processing.

Eyeban does not use your Inputs or Suggestions to train models, and does not permit providers to train on that Content, except when you explicitly enable a training opt-in control in the product (if offered). Generating a response for your request is service processing, not training.

Providers may process Inputs transiently to return Suggestions. Eyeban may retain limited logs for abuse prevention, debugging, and billing of AI usage. Retention periods will be documented in-product as features mature. You can request account deletion as described in the Privacy Policy.

Model providers act as processors for generating Suggestions. The specific providers available in the product may change. When you use your own API keys (if supported), those requests are also subject to the provider’s terms, and Eyeban’s zero-training commitments may not extend to that provider relationship.

When a privacy mode or similar control ships, it will be described in the docs with what is blocked, what still must be sent to produce Suggestions, and whether org admins can enforce it. Until that control exists, treat AI features as sending necessary context to providers under this policy.

Review Suggestions before applying them. Ensure you have rights to submit Inputs. Follow your employer’s policies for proprietary code. You remain responsible for the software you ship.

Questions about AI and data use: hello@eyeban.ir