Avaron privacy
Privacy policy
Effective 19 August 2026. This page explains Avaron's current product-level privacy boundaries. Contract-specific data terms may add to these terms where applicable.
What Avaron processes
Avaron may process account identity, workspace roles, company profile information, what Avaron understands about your business, evidence, targets, commercial opportunities, validation actions, approved deal movement, usage, billing references, telemetry, audit logs, and support communications.
Avaron is designed to keep customer workspaces isolated and to expose only the data needed for the customer-authorized workflow.
Why Avaron uses this data
Avaron uses this information to operate and secure the service, understand what a company can genuinely deliver, match those capabilities against current market movement, investigate named targets, preserve evidence and approval boundaries, provide support, and improve reliability and relevance.
Avaron does not treat model output as verified fact. Evidence, inference, assumptions, confidence, and validation next remain distinct where they materially affect a commercial decision.
Service providers
Data may be processed by configured hosting, authentication, database, payment, email, AI, retrieval, observability, and security providers when needed to provide the service.
Customers should not upload unlawful or unnecessary sensitive data. Provider access and processing are limited to the services Avaron has configured for the applicable workflow.
ChatGPT and MCP use
When a customer connects Avaron to ChatGPT or another supported MCP client, Avaron resolves the authorized workspace and returns only the information required for the selected Avaron capability. Authentication secrets, server credentials, debug payloads, and unrelated workspace data are not intended to be returned to the model.
Consequential actions such as Review submission, outreach, contact creation, publishing, Pipeline movement, or billing changes remain separately controlled and are not implied by a read-only research request.
Retention, access, correction, export, and deletion
Retention depends on the type of account, workspace, commercial agreement, security and audit requirements, billing obligations, and backup schedules. Requests for access, correction, export, or deletion may be subject to legal, fraud-prevention, billing, security, and backup-retention requirements.
For account-specific privacy help, use the public Avaron support page and the support channel associated with your account or commercial agreement.