Subprocessors
The third parties that process personal data on our behalf when you use Lingivio. This list is compiled from the services the running system actually calls.
Last reviewed — 2026-09-12
These documents were drafted by the operator and checked against the running system. They do not constitute legal advice and remain subject to review by a qualified practitioner.
Who you are dealing with
Lingivio is operated by Velniq Ltd, a private limited company registered in England and Wales (company no. 17454810, incorporated 11 September 2026). Velniq Ltd is not VAT-registered; purchases are sold by our merchant of record, who charges and remits any VAT or sales tax due.
- Company
- Velniq Ltd
- Company status
- Active — private limited company (Companies House)
- Jurisdiction of incorporation
- England and Wales, United Kingdom
- Company registration number
- 17454810
- Registered office
- 2nd Floor College House, 17 King Edwards Road, Ruislip, London, United Kingdom, HA4 7AE
- Date of incorporation
- 11 September 2026
- Effective date of these documents
- 2026-09-12
- Company website
- https://velniq.ai
- Service
- https://lingivio.com
- Support
- support@velniq.ai
- Privacy
- privacy@velniq.ai
- Data protection contact
- dpo@velniq.ai
- Abuse reports
- abuse@velniq.ai
- Legal and contracts
- legal@velniq.ai
Last reviewed — 2026-09-12
| Processor | What it does for us | What it receives | Where it processes |
|---|---|---|---|
| Cloudflare, Inc. | Hosting, database, object storage, caching, job queue, platform logs, and — only if you allow analytics — cookieless page-view measurement | All request traffic, all account and billing records, uploaded documents and translated outputs, abuse counters keyed to IP address, account id or API key id, platform logs which for an unmapped error can contain a fragment of a document, and — with analytics allowed — the page address, referring site and general device type its measurement script reports, with no identifier of you | Global edge, with no region pinned to the EU today |
| Modal Labs, Inc. | Runs the translation engine, including document parsing, OCR and re-rendering | The complete bytes of every uploaded document, the storage key which contains the account id and filename, the job options and any glossary terms, and the translated output | United States |
| OpenRouter, Inc. | Model gateway that routes translation requests to the model provider | The translatable text of the document including OCR text, glossary terms, target and source languages, formality and structural labels. No account identifier, email, filename or job id | United States |
| OpenAI, L.L.C. | Provides the language model that produces the translation | The same request content the gateway forwards: document text, glossary terms and translation settings, with no identifier of you | United States |
| Kelviq, Inc. | Merchant of record: sells the plan or top-up, takes payment, issues invoices and handles tax | Your account id and chosen plan from us; your name, email, billing address, tax identifier and payment details collected directly by it from you | United States, with payment processing by its own processors in the United States, the United Kingdom and the European Union |
| Functional Software, Inc. (Sentry) | Error reporting: tells us when our website, our interface or the translation engine has crashed, so we can fix it | The technical detail of a failure and nothing else: the error type, the code that raised it, the page or operation it happened in, and an account reference that is a one-way hash rather than your identity. Your document text, your file names, your glossary terms and your email address are stripped out before anything is sent, so none of them reaches this processor. That is a statement about error reporting only: the rows above describe the processors that do receive your document text, because translating it is what they are for | European Union |
| Google Ireland Limited (Google Analytics) | Product analytics and advertising measurement (Google Analytics 4): tells us which pages are visited, where visitors came from, and whether an advertisement led to a sign-up | Page paths, referrers, campaign tags, and the same fixed list of short technical values our own analytics may carry — a file format, a language code, a plan name. For a signed-in visitor who allowed analytics, a dedicated random identifier that is minted for this purpose and maps to nothing outside the analytics tool. Your document text, file names, glossary terms and email address are structurally excluded. It runs only on a deployment where we have configured it, and nothing is stored in your browser without your consent | European Union data location; Google may process in the United States under the EU–US Data Privacy Framework |
| Amazon Web Services EMEA SARL | Image safety check (Amazon Rekognition): classifies the images an upload carries for sexual content before the file is translated | Copies of the images inside an uploaded file, each re-encoded and reduced in size, sent one at a time with nothing else: no document text, file name, account id or email address. The account is set to opt out of the provider using this content to improve its services. | European Union (Ireland) |
| Microsoft Corporation (PhotoDNA) | Known-material check (Microsoft PhotoDNA): compares a fingerprint of each image an upload carries against lists of known child sexual abuse material, so a match can be reported to the authorities without anyone at our company viewing the file | Copies of the images inside an uploaded file, each re-encoded and reduced in size, sent one at a time with nothing else: no document text, file name, account id or email address | Not yet in use. The processing location is set by the service endpoint Microsoft issues with access, and is stated here before the check is switched on |
A dependency to be aware of
Which model provider receives your document text depends on the model we have deployed. Changing the model changes the processor at the end of that chain, so this page is re-verified against the deployed model as part of every model change. If you have a contractual requirement about which model provider sees your content, tell us before you rely on this page.
Not currently in use
Sign-in with Google is only a processor when Google sign-in is enabled on the deployment you are using; when it is, Google receives the sign-in request and returns your Google account id, email, name and profile image. An alternative payment provider is implemented in the code but is not switched on, and is not a processor unless and until this page says it is. Error reporting is named in the table above before it is switched on, so that a processor is listed before it receives anything rather than after. Two limits apply whenever it is on: it receives nothing from your browser unless you have allowed diagnostics, and what it receives from our own servers is the technical detail of a crash with your content already removed.
Deliberately absent
There is no session recorder, no separate email service provider and no content moderation or antivirus vendor in this product. Analytics and error reporting exist and are listed above; they run nowhere without your consent in the browser and are structurally unable to carry your document content. If any vendor of the kinds named in this paragraph is introduced, it will be added to the table above before it processes anything.
Changes to this list
We will publish any addition to this list here, with a new review date, before or at the point the new processor begins handling customer data, and we will notify business customers who have asked to be told. If you object to a new subprocessor on reasonable data protection grounds, write to the privacy contact; if we cannot resolve it, you may terminate the affected subscription and receive a pro-rata refund of any prepaid period.