Axiomyx Third-Party Models and Connectors Notice

Document version: 1.1 Effective date: 2026-08-26 Last updated: 2026-08-26

1. Purpose

Axiomyx can operate alongside third-party models, identity providers, databases, infrastructure, and connectors. This notice explains who selects them, where data can flow, and which responsibilities remain with the Customer and Axiomyx.

2. Core customer-hosted flow

Customer user -> Customer-hosted Axiomyx runtime -> Customer-controlled PostgreSQL/storage

The core runtime does not modify source systems by default. It writes derived canonical objects, signatures, indexes, and provenance into the customer-controlled Axiomyx data layer and can store, retrieve, export, and delete those derived records. Axiomyx does not require operational Customer Data to be uploaded to Axiomyx for those normal local functions.

3. Customer-selected model or connector flow

Customer-hosted Axiomyx runtime -> Customer-selected model or connector -> Provider systems

If the Customer enables an external model or connector, the selected data is transmitted according to that configuration. The provider may process prompts, content, metadata, identifiers, outputs, logs, and usage information in regions and under terms selected by the Customer.

External AI or connector write access to source or destination systems exists only where the Customer expressly configures and authorises it. Private Edition does not grant that write access by default.

The Customer must assess:

• legal authority and notices for the data disclosed;
• the provider's terms, privacy, security, training-use, retention, deletion, and subprocessor position;
• data location and overseas-disclosure requirements;
• model suitability, output risk, and required human review;
• credentials, permissions, rate limits, and charges; and
• whether the connector preserves required provenance and evidence controls.

Axiomyx should not represent a customer-selected model as endorsed, deterministic, accurate, or suitable for a regulated decision merely because a connector is technically available.

4. Activation flow

Customer runtime -> Axiomyx activation service -> Commerce status check and Cloud KMS signing -> Signed Entitlement

Activation uses limited commercial and installation facts. Google Cloud is an activation-hosting and key-management provider category. Operational Customer Data is not required for signing and is not intended to be sent to Google Cloud by the standard activation flow. The service uses authenticated Google Cloud infrastructure and Cloud KMS so the private signing key is not present in the runtime or application container.

5. Commerce flows

Personal customer -> Apple App Store or Microsoft Store -> Free distribution or Premium subscription -> Limited Axiomyx commercial records
Business customer -> Lemon Squeezy checkout/customer portal -> Payment and subscription providers -> Axiomyx commercial records

Apple or Microsoft distributes Personal Free and manages Premium checkout, payment, tax, receipts, subscription controls, entitlements, refunds, and payment disputes under its store terms. Lemon Squeezy manages those commerce functions for Business and acts as merchant of record for supported Business orders. These roles do not mean Customer operational data is sent to those commerce providers. Axiomyx does not receive complete card details through these checkout flows.

6. Identity, database, and infrastructure providers

Personal is delivered as a native store application and uses embedded SQLite. It does not require a PostgreSQL process, PostgreSQL socket, Docker, Compose, or OCI runtime.

Business requires customer-managed PostgreSQL, OIDC, and HTTPS issuer validation. The Customer chooses and controls the location of PostgreSQL and operational storage and selects and administers its database, identity, certificate, infrastructure, network, observability, and backup providers. Those providers can receive operational or identity data under the Customer's configuration.

7. Open-source software

Private Edition can include open-source software. Applicable licence notices and source-offer obligations must accompany the release where required. Open-source components remain governed by their respective licences. The Axiomyx commercial licence does not remove rights granted directly under an open-source licence.

Axiomyx maintains an accurate software bill of materials, licence inventory, attribution set, vulnerability review, and process for source-code obligations for released products.

8. Third-party changes and availability

Third parties can change APIs, models, terms, regions, prices, limits, or availability. Axiomyx may update or discontinue a connector when required for security, legality, compatibility, or provider changes. Material effects on an active paid service should be communicated fairly.

Axiomyx is responsible for accurately documenting its Software and for defects within its control. It does not operate or guarantee a customer-selected provider. This allocation does not exclude a responsibility or remedy that applicable law does not permit Axiomyx to exclude.

9. Support disclosures

Customers should send only customer-reviewed sanitised diagnostics to av@axiomyx.tech. Support should normally rely on synthetic or minimised reproductions and configuration information. Axiomyx must obtain informed agreement before requesting remote access or operational Customer Data. Provider-related support may require the Customer to work directly with that provider.

10. No absolute locality claim

The accurate proposition is customer-controlled deployment and local custody during normal core operation. It is not an absolute promise that data never leaves the Customer's infrastructure. External connectors, identity, databases, backups, telemetry selected by the Customer, activation metadata, commerce, and voluntary support disclosures create distinct flows that must be assessed.