Axiomyx Customer Data and Deployment Boundary

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

1. Core proposition

Axiomyx Personal is a native desktop application using embedded SQLite and customer-selected storage. Axiomyx Business and Enterprise are customer-hosted products for customer-controlled infrastructure. The Customer controls its operational records, indexes, prompts, outputs, provenance, deployment, database, storage, access, retention, and backups.

Axiomyx licenses software and operates limited commerce, activation, release, and support functions. In the standard Private Edition product, it does not host or take custody of operational Customer Data merely because it supplies a licence.

Private Edition does not modify source systems by default. It writes derived canonical objects, signatures, indexes, and provenance into the customer-controlled Axiomyx data layer.

2. Boundary diagram

CUSTOMER-CONTROLLED BOUNDARY
Users -> Private Edition runtime -> PostgreSQL/storage -> Customer backups
                         |
                         +-> Optional customer-selected models/connectors

LIMITED AXIOMYX/PROVIDER FLOWS
Personal customer -> Apple App Store or Microsoft Store Free distribution and Premium commerce
Business customer -> Lemon Squeezy commerce
Business runtime -> Axiomyx activation service -> Cloud KMS -> Signed Entitlement
Customer -> Axiomyx support, only when the Customer chooses to submit material

The diagram is a responsibility model, not a network guarantee. Customer-selected cloud hosting, identity, database, model, connector, backup, and observability providers can operate outside the Customer's physical premises and outside New Zealand.

3. Personal deployment

Personal is intended for one person. Personal Free can be installed and used without a paid subscription for up to 500 MB (500,000,000 bytes) of Active Evidence. Axiomyx Premium costs US$9.99/month per Personal product and removes that product's Axiomyx Active Evidence quota while Premium is active. Device storage, operating-system, hardware, model, provider, and context-window limits still apply. The released design uses:

• a native application delivered through the relevant Apple App Store or Microsoft Store;
• embedded SQLite with no PostgreSQL process or socket;
• the production store and helper-service identity for that product; and
• customer-controlled local storage and backups.

The Customer chooses and can remove the files and folders used as evidence. Active Evidence is the combined source-file size of supported files that Personal has accepted and retained as evidence. Installation, compatible devices, Premium subscriptions, cancellations, and updates are governed by the relevant store and product listing.

4. Business deployment

Business is intended for one legal entity, up to ten Authorised Users, one production Deployment, and one non-production Deployment. It requires:

• a compatible Docker/OCI environment;
• customer-managed PostgreSQL with appropriate transport security;
• customer-managed OIDC;
• HTTPS issuer validation;
• customer-controlled production and non-production configuration;
• customer-controlled secrets, networks, storage, backups, monitoring, and recovery; and
• separation appropriate to the Customer's security requirements.

Axiomyx support can guide documented configuration but does not operate those systems.

5. Customer responsibilities

The Customer is responsible for:

• lawful collection and use of Customer Data;
• access control and Authorised User administration;
• infrastructure, database, identity, endpoint, network, and credential security;
• capacity, availability, backup, restoration, continuity, and retention;
• selecting and governing external providers;
• applying supported security updates;
• validating model outputs and maintaining appropriate human review; and
• responding to incidents within customer-controlled systems.

These responsibilities do not excuse a defect in the Software or remove a non-excludable remedy.

6. Axiomyx responsibilities

Axiomyx is responsible for:

• supplying the described Software and Documentation;
• maintaining a reasonable secure-development and release process;
• operating the activation service and protecting signing authority;
• applying agreed entitlement rules accurately;
• providing support and updates within the applicable Free, purchased, or negotiated tier and period;
• handling commerce, activation, support, and contact information lawfully;
• giving accurate security and privacy disclosures; and
• responding to defects, vulnerabilities, privacy events, and legal remedies according to the final policies and law, including guidance, patches, updated packages, corrected releases, replacement, or refunds where required by applicable law.

7. Activation boundary

Activation may send a licence credential and limited order, subscription, installation, tier, deployment-kind, release, and status facts to the activation service. Google Cloud is an activation-hosting and key-management provider category. This flow does not require or intend transmission of operational records, prompts, outputs, indexes, or provenance.

The activation service validates commercial eligibility and uses Cloud KMS to sign an Entitlement. The runtime contains the public verification key, not the private signing key. The licence key should not be embedded in the signed Entitlement or retained by the customer runtime after activation.

Service-side logging, licence-key handling, regions, and retention are documented and maintained as part of the applicable release and privacy controls.

8. Commerce boundary

Apple or Microsoft distributes Personal Free and processes Premium payment credentials, billing details, tax, receipts, subscription status, entitlements, refunds, and payment disputes under the relevant store terms. Lemon Squeezy processes those commerce functions for Business and acts as merchant of record for supported Business checkout. These roles do not mean Customer operational data is sent to the commerce provider. Axiomyx receives only the commercial information made available and required to supply and administer the product. Axiomyx does not receive complete card details through these checkout flows.

9. Support boundary

Support normally remedies defects without access to Customer operational data. It may rely on release and environment information, configuration information, synthetic or minimised reproductions, and customer-reviewed sanitised diagnostics. The Customer should remove secrets and unnecessary personal or operational data. Remote access or submission of Customer Data requires separate informed agreement and appropriate security.

Support contact: av@axiomyx.tech.

10. Models and connectors

The Customer decides whether to enable an external model or connector and which data to send. External AI or connector write access exists only where expressly configured and authorised by the Customer. That decision can move data outside the customer-hosted runtime and can engage overseas-disclosure, confidentiality, sector, and provider obligations.

Axiomyx must document any transmission initiated by its Software. The Customer must govern providers it selects. Neither party should claim absolute locality when an external provider is configured.

11. Free, trial expiry, and non-renewal

Personal Free is not a trial and has no subscription expiry. A Premium trial applies only where the relevant store expressly offers one and is governed by the store listing and terms. Axiomyx does not promise a Premium trial.

If Premium ends or is cancelled, Personal returns to the Free plan. Original source files and retained local evidence are not deleted. If retained Active Evidence exceeds 500 MB, further additions or folder growth can be restricted until the Customer removes enough evidence or restores Premium.

If a Business trial expires without conversion, new ingestion, canonicalisation, signatures, indexing, provenance, AI-context operations, users, and Deployments may be denied. Retained local data remains available for inspect, export, delete, and backup. Valid activation and sanitised diagnostics remain available.

If a fully paid subscription is not renewed, the last release fully paid for and validly activated may continue within the purchased limits. Future versions, security updates, support, and additional installations or Deployments end. Fresh reactivation after expiry may require support.

Neither state transfers, deletes, encrypts, seizes, or gives Axiomyx custody of Customer Data.

12. Release status

Product availability, supported release status, and operational requirements are stated in the applicable store listing, release documentation, or accepted order.