What stays local.
What is processed.
Local files, keys and receipts
This notice describes mfenx LLC’s Gate website and software-licensing service. Local receipt verification and model evaluation read your selected files on your device. These workflows do not upload your models or evaluation data to MFENX. A customer-operated deployment keeps its organization records, policies and receipt history in the customer’s environment.
Your private purchase key, private receipt-signing keys and recovery passphrase stay under your control. Browser storage holds the local purchase identity; a recovery file is encrypted locally for you to save. Clearing browser data can remove the usable local key. MFENX does not receive the recovery passphrase or retain a copy of your private purchase key.
A compact release receipt can disclose artifact hashes, issuer information, evaluation identifiers and recorded outcomes. Inspect it before sharing. A full model package may include the model or dataset itself and is not the same as a compact receipt. MFENX does not automatically publish either on your behalf.
The license service
A software-license request sends a public purchase key, a signed challenge response and the identifiers required for the requested operation. The service checks the request and current payment eligibility. It does not require a MFENX email account or receive model files, evaluation data, private keys or your local receipt history.
The license ledger retains the holder’s public-key hash, opaque purchase and subscription references, the accepted commercial-terms digest, plan, entitlement state, paid-period and processing timestamps. The digest identifies the terms accepted; the ledger does not store the terms document itself. Temporary challenges and processed notification identifiers support authentication and duplicate detection. These records are pseudonymous, not necessarily anonymous: payment references can be associated with a purchaser through Paddle.
We use these records to issue and refresh entitlements, recover an already bound purchase, prevent replay and fraud, resolve support or payment disputes, and meet applicable obligations. The service receives provider notifications and reads current payment state; it does not retain raw notification bodies, customer names, billing addresses or card details in the license ledger.
Payment information
Paddle collects purchaser and payment information during checkout and handles billing as reseller. Its processing is described in Paddle’s privacy notice. The separate payment interface is not the local model-verification workspace.
Payment records available through Paddle, and information you choose to send in a support request, may identify you. Saying that model files remain local does not mean that a purchase is anonymous or that no personal information is processed.
Website, hosting and support
The static website is served through GitHub Pages. The license service is hosted on DigitalOcean. Those services, network providers and payment infrastructure may process IP addresses, request times and other connection metadata when serving or protecting requests.
The purchase workflow uses browser storage for its local key and recovery state. Third-party payment interfaces may use their own cookies or storage under their policies. Offline receipt verification and offline software-license validation do not need to contact a billing service.
If you email support, we receive the message, attachments and sender information you provide, and use them to review and respond to the request. Do not send models, datasets, private keys, recovery files, passphrases or payment-card details. Send only a redacted description and the minimum identifiers needed to locate the issue.
Retention and privacy requests
Licensing and support records are retained for subscription operation, purchase recovery, fraud prevention, dispute handling and applicable obligations. There is no automatic deletion schedule promised by this notice. Requests are reviewed against the records held and any continuing operational or legal need.
To ask about access, correction, deletion or another applicable privacy right, contact lexluger.dev@proton.me. We may need to establish that you are authorized to act for the relevant purchase. Contacting support does not itself prove control of a purchase key or guarantee key recovery.
For information held by Paddle, use the request channels in its privacy notice. Local customer-operated records remain under the customer’s administration. This notice does not replace rights available under applicable law.