Data Use
Last updated: July 1, 2026
1. What data Aethaar DevOp collects and why
This page provides a plain-language summary of what data Aethaar DevOp (our Agentic IDE) collects, where it goes, and what controls you have over it. For the full legal treatment, see our Privacy Policy.
2. Data Collection Breakdown
| Data Type | Collected? | Purpose | Leaves your device? |
|---|---|---|---|
| Account info (email, name) | Yes | Authentication and billing | Yes — stored on Aethaar servers |
| AI prompts (cloud models) | Yes | Fulfilling completion requests via Agentic AI | Yes — sent securely to trusted model providers |
| AI prompts (local models) | No | Processed on-device only via Ollama or similar | No — remains strictly local |
| AI prompts (BYOK) | No | Sent directly to your chosen API provider | Yes — to your provider, not to Aethaar |
| Code files | Partial | Providing context for agent interactions | Only the specific portion sent as context |
| Usage telemetry | Yes | Product stability and IDE improvements | Yes — strictly anonymized aggregates |
| Crash reports | Yes (opt-in) | Debugging IDE stability issues | Yes — stripped of any source code content |
| Payment data | No | Processed by payment provider | Goes directly to payment provider, not Aethaar |
3. Subprocessors
To provide our cloud-based Agentic AI features, DevOp securely transmits code snippets and prompts to trusted third-party AI model providers. Our current subprocessors include: OpenAI, Anthropic, DeepSeek, Google, xAI, and OpenRouter. These providers only process data required to fulfill the completion request and are contractually bound not to train their models on Aethaar customer data.
4. Model training
Aethaar does not use your private prompts, code, or completions to train AI models. This applies both to Aethaar's own model research and to our third-party providers. We maintain strict data processing agreements with all cloud model providers that prohibit training on our customers' data by default.
If we ever introduce an opt-in program where users can contribute data to improve DevOp agents, participation will be explicit, entirely voluntary, and clearly disclosed.
5. Codebase indexing
When Aethaar DevOp indexes your codebase for semantic search and deep agent context retrieval, the index database is generated and stored locally on your machine. Index data is not uploaded to Aethaar servers unless you explicitly enable a cloud-sync feature (which is disabled by default).
6. Telemetry controls & Enterprise isolation
Telemetry
Usage telemetry is enabled by default to help us understand how features are used and to improve the Agentic IDE. We only collect anonymized, aggregate data. You can disable telemetry entirely from Settings > Privacy. Disabling telemetry will not affect the functionality or performance of DevOp.
Enterprise Data Isolation
For organizations requiring strict compliance, Enterprise plans include dedicated data isolation options aligned with SOC 2 Type II controls. This includes tailored data residency configurations, private VPC deployments, standard data transfer mechanisms (such as DPAs), AES-256 encryption at rest, and local-only agent sandboxes. Contact us for detailed architecture reviews.
7. Contact
Questions about how your data is used can be directed to our unified support inbox at:
Email: [email protected]