Product and purchase support
Software support
Email lexluger.dev@proton.me with a concise description of what happened and what you expected. Include the product version, operating system, CPU architecture, Python version and a redacted error message. A small reproduction that does not contain your private files is useful.
The qualified customer-runtime target is CPython 3.13, Linux x86_64 and glibc 2.34 or newer. Model-evaluation SDK dependencies are installed separately. Review the installation and integration documentation first; include which installation and acceptance check failed when reporting a problem.
Standard support is handled in writing. There is no guaranteed response time or custom service-level agreement in the standard subscription.
License refresh and purchase-key recovery
Use the software-license page in the browser that holds your purchase key, or restore your encrypted recovery file locally with its passphrase. Save recovery material before clearing browser storage or changing devices. Never send the recovery file or passphrase to support.
Monthly plans require an online entitlement refresh; the optional customer-side renewal tool does not install a scheduler automatically. Private entitlements validate offline until their signed expiry. An active payment and a valid local entitlement file are separate checks.
If self-service recovery fails, send the license identifier or purchase reference and the redacted error. We can review the record and available options. A support email is not proof of key ownership, and MFENX cannot promise to recover a lost private key.
Billing, cancellation and refunds
For receipts, payment details or subscription cancellation, use the management link in your Paddle purchase email or Paddle buyer support. See the cancellation and refund policy for refund requests. Uninstalling the software does not stop subscription renewal.
Security reports and privacy requests
Send a redacted security report or privacy request to lexluger.dev@proton.me. For a security issue, include the affected version and reproduction steps without live credentials. For privacy requests, identify the relevant service or purchase so that authorization and the records held can be reviewed.
Do not email private keys, passphrases, recovery files, payment-card details, models or datasets. The privacy notice describes information processed by the license service, infrastructure and support correspondence.