Legal
Privacy Policy
Last updated: 2026-09-07 16:12 UTC
Axial Solutions LLC ("Axial Solutions," "we," "us") operates the account portal at axialsolutions.io and kyriosforge.io (the "Portal") through which customers purchase, license, and manage KyriosForge and related products. This policy covers the Portal, associated support, and community forum data. It does not cover data processed by KyriosForge itself once deployed — see “KyriosForge is self-hosted” below.
KyriosForge is self-hosted
KyriosForge runs entirely on your own infrastructure. Workloads, containers, media pipelines, logs, metrics, and configuration stay on your hardware. None of your operational data is transmitted to Axial Solutions during standard execution.
Information we collect
Account information. When authenticating via Google or Microsoft, we receive your email address, name (if supplied), and a stable subject identifier. We do not capture or store passwords — authentication is handled entirely by your chosen provider. (Enterprise customers: see “Enterprise: unified organizational access” below for a coming-soon addition to this.)
Hardware footprint. We collect a non-reversible cryptographic hash of your hardware profile strictly for license enforcement, trial/registration integrity, and abuse prevention.
Transaction records. Polar.sh acts as our Merchant of Record and handles payment processing, card data, and tax compliance directly — we never receive or store your card number. We retain transactional metadata (order/subscription IDs, tier, product, term, amount, currency, status) tied to your account, along with the license records and entitlements that purchase grants. Order records also retain a one-way cryptographic hash of the email address used at time of purchase — not the email itself — independent of your account record; see “Data Retention & Purge Policies” below for why.
Support & forum. If you contact support, your ticket is created in our support system on your behalf; content is expected to contain only what’s needed to resolve the issue — a name or account identifier and your email at most. If you sign in to the community forum, your forum account is linked to the email from your chosen SSO provider so we can grant or remove posting access based on your license status.
Session cookies. We use a local session cookie holding an opaque, revocable token to manage authentication state — not a tracking identifier, and not shared with or readable by any third party. We do not use third-party analytics or behavioral tracking scripts of any kind on the Portal.
Enterprise: unified organizational access (coming soon)
Enterprise customers will be able to enroll their own SASL-capable identity server so that one organizational profile can centrally manage Portal login and license activation across multiple offices or deployments. If and when you use this, we would receive the same categories of information described above (email, name, stable identifier) via your organization’s own identity server rather than Google or Microsoft directly. This capability is not yet available — it does not apply to any account today.
How we use this information
- To create and maintain your account and authenticate you.
- To process orders, issue and track licenses, and handle renewals.
- To provide support and respond to tickets.
- To grant or revoke forum posting access based on active license status.
- To send transactional email (order confirmations, license/renewal notices, support replies). We do not send marketing email you haven’t asked for.
We do not sell your personal information. We disclose it only to the service providers required for core platform functionality: Google or Microsoft (or, once available, your enrolled Enterprise identity server) for sign-in; Polar.sh, our Merchant of Record, for payment processing, subscription management, and tax remittance; and our support and forum systems, strictly to provide the service.
Data Retention & Purge Policies
Active accounts. Your name and email address are retained for the duration of an active account.
Hashed hardware footprints. Retained for a maximum of five (5) years before being permanently purged.
Transaction records. Order and subscription metadata (IDs, tier, product, term, amount, currency, status) is retained indefinitely to satisfy accounting and tax-compliance obligations, and survives account deletion. An order record also keeps a one-way cryptographic hash of the email used at purchase — not the email itself, and not reversible back to it — retained permanently and not cleared on deletion, specifically so that if the same email is used to open a new account later, we can recognize it as a repeat and prevent re-claiming a one-time discount (e.g. the first-purchase referral discount) already used once. Because it’s a hash, not the address, this doesn’t reveal your email to anyone who might see the order record — it only ever answers “does this hash match,” never “what was the email.”
Account Deletion & Data Rights
You may request account deletion at any time by contacting [email protected]. Upon deletion:
- Your account’s direct identifiers (name, email, provider identity) are replaced with an anonymized placeholder; you can no longer sign in to the deleted account.
- All active session tokens for the account are invalidated immediately.
- Order and license records remain, still associated with the deleted account’s internal ID, for accounting/support/audit purposes — see “Transaction records” above for the one field (the order-level email hash) that is deliberately not scrubbed and why.
You may also contact us to ask what data we hold about you.
Children
The Portal is not directed to children, and we do not knowingly sell to or collect information from anyone under 18. We recommend parental guidance and supervision for any use of our products by anyone under the age of 18.
Changes to this policy
We’ll update the date at the top of this page when this policy changes, and post material changes here before they take effect.
Contact
Axial Solutions LLC
Kenmore, Washington, USA
admin@axialsolutions.io