Privacy Policy

1. Who we are

Axis is provided by Expressline LLC, a Wyoming limited liability company. Privacy questions may be sent to privacy@tryaxis.so. General questions may be sent to contact@tryaxis.so.

2. Local-first product content

Axis runs on an Axis node you control. Your source files, project files, prompts, transcripts, commands, artifacts, credentials, and agent work are stored primarily on that node rather than in the Axis commercial control plane.

Content leaves your node when you direct Axis to send it to an AI provider, integration, paired device, or notification service, or when a feature clearly requires that transfer. Those third parties process information under their own terms and privacy policies.

3. Information Axis processes

• Account and access information, such as email address, account identifiers, authentication state, plan, and billing state.
• Installation and device information, such as pseudonymous device and installation identifiers, platform, architecture, app/runtime versions, entitlement state, and last-seen timestamps.
• Security and reliability information, such as access IP history, coarse country, health heartbeats, update state, bounded error categories, and operational logs.
• On tryaxis.so, content-free website measurements: random pseudonymous visitor and session identifiers, desktop or mobile device class, and explicit interactions with allowlisted navigation and platform-download controls.
• When you separately opt in, content-free in-product analytics such as stable signup, setup, onboarding, activation, and feature identifiers; bounded status or provider categories; pseudonymous user/account and installation identifiers; app/runtime versions; platform; product interactions; and timestamps.
• Aggregated local usage information, such as provider/model names, request and token counts, and estimated provider cost.
• Billing evidence from payment providers, including customer, subscription, product, transaction, and webhook information.
• Feedback and support messages you deliberately submit.
• Legal acceptance evidence, including policy versions, acceptance time, account/authentication identifiers, and acceptance surface.
• Paired-device and notification information, including device identity, token digests, notification preferences, push tokens, approval keys, titles, identifiers, approval text, and deep links needed to deliver enabled notifications.

4. Website measurement, product analytics, and operational logs

On tryaxis.so, Axis uses narrow first-party website measurement to count pseudonymous browser sessions and explicit clicks on allowlisted page-navigation and download controls. The browser stores random visitor and session identifiers in local storage and sends only fixed event names, desktop or mobile device class, navigation destination, download platform, button placement and availability, and timestamps to PostHog’s European Union cloud. It does not send form values, email addresses, raw URLs or query strings, page text, advertising identifiers, or fingerprinting data. Axis does not use browser autocapture or session replay.

In-product analytics is optional and off by default. If you separately choose “Share anonymous product analytics,” Axis sends minimal content-free first-party events to PostHog’s European Union cloud to understand where setup succeeds or fails, improve reliability, and guide product improvements. In-product analytics is limited to the closed categories described above. It does not include prompts, files or file contents, commands, project or session names, paths, free-form error text, secrets, or credentials. Axis does not use product analytics to track you across apps or websites owned by other companies and does not request AppTrackingTransparency permission.

Your in-product choice does not affect signup or access. You can withdraw it at any time in Account & devices; withdrawal stops new in-product analytics events and removes undelivered analytics records. It does not disable website measurement or operational security and reliability logs needed to operate and improve the service.

Operational logs are separate from optional in-product analytics. They may include allowlisted request routes, pseudonymous runtime identifiers, timing and status information, bounded error categories, and sanitized performance measurements. Axis excludes prompts, files, commands, project or session names, paths, and free-form errors from hosted operational logs.

5. Why we use information

We use information to create and secure accounts, operate Axis, activate installations, provide access and updates, process billing, prevent fraud and abuse, diagnose failures, improve the product, provide support, enforce our Terms, and comply with law.

6. Providers and disclosures

We may use service providers for payments, email delivery, optional analytics, operational logging, hosting, push notifications, distribution, and other infrastructure. PostHog’s European Union cloud processes the website and optional in-product analytics categories described in sections 3 and 4: pseudonymous website visitor, session, user/account, and installation identifiers; allowlisted website and product interactions; platform and app/runtime versions; bounded event categories; and timestamps. PostHog also processes separately allowlisted operational logs.

Apple and Google may process App Store or Play Store account, storefront, purchase, subscription, transaction, crash, and diagnostic information under their own policies when they distribute Axis or provide store services. Axis may receive store transaction identifiers and status needed to provide purchases or subscriptions. Apple Push Notification service and browser push providers process device/push tokens and the notification fields needed to deliver notifications. AI providers and integrations you configure receive the content you choose to send them.

We may disclose information when required by law, to protect users or the service, to investigate abuse, or in connection with a business transaction subject to appropriate safeguards.

7. Retention, deletion, and security

We retain information only as long as reasonably necessary for account security, service delivery, billing, support, fraud prevention, product improvement, and legal obligations. Retention varies by system and provider. Exact commercial access-IP observations expire after 30 days and are removed during security-history cleanup. No shorter analytics-specific retention period is promised until the pending retention review is approved.

Verified deletion requests cover applicable Axis-held account and analytics records and, where applicable, a deletion request to PostHog. Some billing, security, fraud-prevention, dispute, legal, suppression, or backup records may remain for their required or rolling retention periods. Apple, Google, and other providers control deletion and retention for information they hold under their own policies.

We use reasonable technical and organizational safeguards, but no system is completely secure. You are responsible for securing your computer, Axis node, provider credentials, API keys, and connected accounts.

8. Your choices and rights

You may leave optional product analytics off during signup, enable it separately, or withdraw it at any time in Axis under Account & devices. You may also disable optional integrations or notifications through their available controls.

You may request access, correction, export, or deletion where applicable by emailing privacy@tryaxis.so. We may verify your identity and may retain information where required for security, billing, fraud prevention, backups, dispute resolution, or legal compliance.

9. International use and children

Expressline LLC is based in the United States. Information may be processed in the United States and other countries where providers operate. Axis is not directed to children under 13, and we do not knowingly collect their personal information.

10. Changes

We may update this Privacy Policy as Axis changes. Material updates may require renewed acceptance. The version shown on this page identifies the policy currently in effect.