Legal

Privacy

Last updated: 4 September 2026

Who runs this

LexaForte is operated by Dmitrii Golovin, based in Bangkok. Contact: dmitrii@lexaforte.com. Channel contracts and CAT/TMS connectors can go through Custom.MT (CMT Language Technology s.r.o., Prague). On those deals Custom.MT is typically the processor and LexaForte is a sub-processor.

What we collect

  • Evaluation form: company name, work email, optional message. Sent so we can reply about an engine.
  • Translation API: source text for the length of the request. We keep usage metadata (character counts, a hash of the request, timestamp, client key) for billing. We do not keep the source or target text after the response is returned.
  • Purifier demo (Fast-Pass): a small sample file you choose to upload, used only to show health / retention stats on screen. It is not a production TM drop and is not used to train other clients’ engines.
  • Training sets: files you send for a real engine. After the engine is validated they are deleted from the training host. The fine-tuned model is private to that client.
  • Billing: handled by Stripe when a paid key is active.

Where it runs

Public site, portals and API gateway: Hetzner, Helsinki. Translation engines: Hetzner, Falkenstein. Those datacenters are ISO/IEC 27001 certified. That is the facility, not a LexaForte company certificate.

Who else can see a request

To keep the published character rate the same for every client, the optional LLM layer runs through OpenRouter. The post-edit is constrained, then discarded with the rest of the payload. Custom.MT sees what you send through their console when you use their connectors.

If OpenRouter is not acceptable — you want a private LLM, no third-party model hop, or you have doubts about that route — we open a dedicated GPU instance with an LLM optimized for that client. That box stays on your isolation boundary. The NMT engine and the $50 / 1M rate stay as agreed; the private LLM instance is quoted separately.

How long we keep it

Payloads: for the request only. Usage ledger: as long as needed to invoice and defend a billing dispute. Evaluation emails: until the conversation ends or you ask us to delete them. Sample Fast-Pass files: not retained as a training corpus.

Your rights

If GDPR applies to your data, you can ask for access, correction, deletion, or a restriction. Email dmitrii@lexaforte.com. For channel deals, send the same request to Custom.MT as well so both sides can act.

This site

The marketing pages use no advertising cookies. The evaluation modal is submitted through Web3Forms so the message reaches the LexaForte inbox.