Axari Data Security Practices

1–2. Purpose and Scope

This policy defines how Axari Technologies, Inc. protects data across its products, APIs, agentic workflows, hosted services, and internal operations, and applies to Axari-controlled production, staging, and development environments and to Axari personnel and approved partners.

3. Data Classification

• Public: marketing pages, public documentation, blog content.
• Internal: internal communications and documentation, non-public roadmaps.
• Confidential: customer configuration data, user accounts, non-public business data, contracts, billing information.
• Highly Confidential: customer secrets (API keys, tokens, customer-provided model keys), sensitive prompts and context, vulnerability data, credentials, encryption keys.

4. Core Data Handling Principles

• Least privilege and need-to-know; default deny.
• Environment segregation; production data is not copied to non-production unless anonymized or pseudonymized, with restricted, logged access.
• Multi-tenancy isolation at the application and data layers; any cross-tenant access for support requires explicit authorization and is logged.
• Data minimization; telemetry is periodically reviewed to remove unnecessary fields.

5–7. Encryption, Identity, and Infrastructure

• Encryption at rest (AES-256 class) for Confidential and Highly Confidential data; TLS 1.2+ in transit; managed key services with restricted, logged, rotated access.
• SSO/OAuth authentication; MFA for administrative access; RBAC across infrastructure and internal tools; access provisioned on hire, adjusted on role change, revoked on departure, and periodically reviewed.
• Peer-reviewed code changes; automated security checks in CI/CD; secrets in secret managers, never in source; risk-based vulnerability and patch management; network controls on production; security-relevant logging and monitoring that avoids storing full secrets.

8. Data Retention and Deletion

Retention periods vary by data type and are informed by operational, legal, and contractual requirements. Following contract termination or uninstall of the Axari app from a customer workspace, Customer Data is retained for 30 days for export, then deleted, and stored third-party authorizations (OAuth grants, including customer-provided model keys) are revoked, except where law requires retention. Backups expire per backup retention schedules.

9–11. Backup, Third Parties, Endpoints

• Regular encrypted backups of critical systems; restoration procedures periodically tested.
• Sub-processors handling sensitive data undergo security review; processing locations documented; DPAs executed where required; vendors contractually required to notify Axari of relevant incidents.
• Company-managed devices use disk encryption and secure authentication; local storage of Highly Confidential data is discouraged; remote access to sensitive systems is controlled.

12. AI and Agentic Platform Security

12.1 Per-user agents and context isolation

Each user's Twin operates with that user's own authorizations only. Prompts, context, memory, and outputs are logically isolated per tenant and per user. A Twin's content is available to its owner; it is not exposed to workspace admins or other users through the product. Cross-tenant data mixing is not permitted without explicit customer authorization.

12.2 Tool and credential controls

Access to external systems is scoped per user and per tenant. Credentials and tokens are stored securely and are never logged. Users can view and revoke their integration grants at any time.

12.3 Human approval and audit

Consequential actions execute only after the owning user's approval. Sessions, actions, and approvals are recorded in an activity log available to the owner.

12.4 Model training and telemetry

Axari does not use customer data to train foundation models by default; any such use requires explicit, documented customer opt-in. Session telemetry is summarized and redacted at ingestion, is classified Confidential or Highly Confidential according to content, and is governed by the same safeguards as customer data.

12.5 Customer-provided model keys (BYOK)

Where a customer elects BYOK, customer-provided model keys are classified Highly Confidential: stored encrypted, never logged, used solely for that customer's inference, health-checked before use, and deleted on termination or customer instruction. Under BYOK, agent inference traffic flows to the customer's own provider account; Axari's platform calls (for example classification) use Axari's own keys.

13–15. Incident Response, Roles, Review

• Axari maintains an incident response process; incidents involving customer data are notified to affected customers without undue delay, consistent with legal and contractual requirements, with root cause and corrective actions tracked.
• Founders/security owner maintain this policy; engineering implements controls; all personnel complete security awareness training.
• This document is reviewed periodically; material changes are reflected on this page.