VoxNexa turns your phone into a dictation microphone for your computer. Speech is transcribed on your phone and the resulting text is inserted into the field you have focused in your browser. We do not sell your data, we do not use advertising or behavioural tracking, and we do not use your dictation for anything other than delivering it to you.
VoxNexa is operated by LUMISOFT / E-Clinics International LLC ("we", "us"). This policy explains what the VoxNexa browser extension and mobile app access, what is transmitted, and what we do and do not retain.
LUMISOFT / E-Clinics International LLCThree components, so it is clear where data travels:
Your audio never reaches our servers. Speech recognition runs on your phone. Only the resulting text is relayed, and only between your own paired devices.
The extension detects when you focus an editable element and inserts transcribed text into it. To position the text correctly it reads the text immediately before your cursor — solely so that a corrected phrase replaces the extension's own previous insertion rather than duplicating it. That text is never transmitted anywhere and never leaves the page.
Dictation deliberately refuses to target password fields, and fields a site marks as holding a password, a one-time security code, or credit card details. The indicator does not appear on them and no text can be inserted into them.
The extension contains no analytics, no tracking pixels, no advertising code, and no remotely hosted scripts. All of its code ships inside the extension package.
Chrome shows a broad-access permission at install. This is required because the extension's purpose is to type into whatever field you choose — an email, an internal web application, a clinical system. The set of sites cannot be known in advance, so access cannot be limited to a fixed list. On every page, its only actions are: notice that an editable field has focus, show a small indicator beside it, and insert text when you dictate.
The VoxNexa Gateway runs on our own cloud infrastructure at
cloudpk.lumieclinic.com, operated by E-Clinics International
LLC. Dictation traffic (pairing, session control, and transcribed text)
goes only to that Gateway. The browser extension contacts
no other service. The mobile app also uses a small set of
operational service providers listed in §6 — never for advertising
or to process your audio or dictated text.
| Data | Where it goes | Why |
|---|---|---|
| Audio of your voice | Nowhere. Stays on your phone | Transcription happens on-device |
| Transcribed text | Phone → Gateway → your browser. Relayed in memory; never stored | To insert it where your cursor is |
| Device name, manufacturer, model, operating system, app version, network type | Gateway (retained) | So you can recognise your own paired devices |
| IP address used to connect | Gateway (retained) | Security, abuse prevention, and device recognition |
| Push subscription identifier | Gateway, and OneSignal (see §6) | So the browser can wake your phone when a session needs it |
| Pairing session identifiers | Gateway | To link your phone to your browser and no one else's |
| A random install identifier, browser name, extension version, operating system name | Gateway | To register this browser as a valid pairing endpoint and issue its credential |
| Crash and diagnostic reports (mobile app only) | Sentry (see §6) | To find and fix app failures — not for advertising |
| Speech-model weight files (not your audio) | Downloaded from Hugging Face to your phone | So on-device transcription can run without sending your voice anywhere |
The install identifier is a random value generated on your device. It is not derived from your name, email, hardware serial, or any advertising identifier. It is stored on the Gateway so we can recognise that install; it is not sold or used for advertising.
Transcribed text is never written to storage and never written to logs. The Gateway holds each message in memory only long enough to forward it from your phone to your browser, then discards it. There is no transcript history, no archive, and no copy retained on our servers.
Because nothing is stored, dictated text cannot be retrieved by us, and is not available for training speech or language models.
So that you can recognise your own paired devices, the Gateway keeps a record of the devices linked to your account: device name, manufacturer, model, platform and operating system version, app version, network type, last-known IP address, and (for phones) push subscription id.
No GPS or precise location. VoxNexa never requests location permission and never reads your device's GPS. We do retain the IP addresses used to connect to the Gateway, for security and device recognition — not to map where you are. The browser extension contacts no service other than the VoxNexa Gateway.
The extension keeps the following in your browser profile so it can reconnect after a restart. It is local to your browser and is not sent to us as a set:
Removing the extension deletes this data.
We use a small number of companies to run VoxNexa. They process data only for the purposes below, under their own terms, and not to sell your information or serve ads.
| Provider | Role | What they receive |
|---|---|---|
VoxNexa Gateway
(cloudpk.lumieclinic.com) |
Our own relay and pairing service | Transcribed text in memory only; device and pairing records as described in §4 |
| OneSignal | Push notifications that can wake the phone app | Push subscription id and the wake notification payload — never your audio or dictated text |
| Sentry | Crash and error reporting from the mobile app only | Diagnostic event data (device/OS, app version, stack traces). The extension does not use Sentry. Dictated text is not sent to Sentry by design |
| Hugging Face | Hosting of on-device speech model files | Download requests for model weight files. Your microphone audio is never uploaded there |
The browser extension talks only to the VoxNexa Gateway. OneSignal, Sentry, and Hugging Face are used by the mobile app (and, for wake pushes, by the Gateway calling OneSignal's API).
VoxNexa is speech-to-text software. Whatever you dictate is treated the same way, whatever it happens to be about:
You decide what to dictate and where it goes. If you use VoxNexa in a regulated setting, your organisation's own policies govern what may be dictated and into which systems. Questions about compliance requirements for a particular deployment can be sent to the address in §12.
Depending on where you live, you may have rights to access, correct, or delete personal data, or to object to its processing. Contact us using the details below and we will respond as required by applicable law.
Dictated text is never stored, so there is nothing to retain or delete. What we do keep, and for how long:
| Record | Kept for |
|---|---|
| Live pairing session (session id, credential) | Until the session ends or its expiry time is reached |
| Durable pairing link (phone to browser) | Until you unpair or ask us to delete it |
| Device / extension record — install identifier, device name and model, operating system, app version, IP address, push subscription id | Until you unpair or email us to erase it. We do not currently auto-delete inactive device records on a fixed schedule |
| Security and connection event logs (never containing dictated text) | Up to 90 days |
To have a device record and its associated identifiers erased, email us at the address below. We will confirm the deletion. Unpairing a device from the app ends its active session immediately; residual device records are removed when you request it.
VoxNexa is professional dictation software intended for adults in a work setting. It is not directed at children, and we do not knowingly collect information from anyone under 13 (or under 16 where local law sets that threshold). If you believe a child has used VoxNexa, contact us and we will delete the associated records.
Questions about this policy or about your data:
LUMISOFT / E-Clinics International LLCEvery revision is published here with a new date at the top of the page. For material changes — anything that alters what we collect, who receives it, or how long we keep it — we will notify you in the app before the change takes effect, and where the law requires your consent we will ask for it rather than infer it from continued use.