Launch offer: $39 $19code UVLAUNCH, applied at checkoutuntil November 30Buy now

Privacy

Short version: nothing you dictate or read is sent anywhere. The app has no account, no analytics and no crash reporting. (The website is covered separately, below.) This document is written to be checkable — every claim below can be verified by watching the network with Little Snitch or lsof, or by reading the source.

What leaves your machine

During normal use: nothing you said, dictated or read — ever. The app makes exactly two kinds of connection on its own: an occasional licence check (see below) and an update check against our own domain. Neither carries a word of yours. A third happens only when you press Send Report in the Report Issue form, and it carries only what that form shows you (see Reporting a problem, below).

Speech processing runs on your own Mac. Univocal reaches its local speech engine at 127.0.0.1:8787 and through a Unix socket in ~/Library/Application Support/Univocal/. Other apps can also send text to Univocal through the local Connect channel described below. These local channels keep voice and text on your Mac. If you watch the app with Little Snitch, its remote hosts are api.lemonsqueezy.com for licence checks and univocalapp.com for update checks and issue reports you choose to send, plus the download hosts listed below when something new is fetched. These requests do not contain anything you dictated or read.

During installation and first use: downloads, all to fetch the speech engine.

On first launch the app downloads the software it runs on — packages for the speech engine from pypi.org, the speech recognition and synthesis models from huggingface.co, and, only if your Mac has none, a standalone Python from github.com. Roughly 1.2 GB in total. Reading aloud in some languages, Korean and German among them, fetches one more model, about 400 MB, the first time you use them.

These are ordinary public downloads of published files. Nothing about you is sent with them beyond what any download involves — your IP address is visible to those servers, as it is to any website you visit. Each file is verified against a SHA-256 hash recorded in the installer before it is used.

After setup, those hosts are contacted again only to fetch something new: a Kokoro voice's small style file (about 0.5 MB, from huggingface.co) the first time that voice reads, the 400 MB model above when you add a language it serves, and a language extra (from pypi.org) when you press Improve… for Japanese or Chinese. Each is a plain download that carries nothing you said or read.

What stays on your machine

Univocal Connect

Connect lets other apps on this Mac send text to Univocal for reading and receive reading progress. Apps communicate with Univocal through a local Unix-domain socket. Connect adds no remote network destination. The text stays on your Mac.

Clicking Connect for an app in Settings → Connections approves its access. If the app’s code signature matches the one Univocal expects and it connects within two minutes, no approval card appears. Otherwise, Univocal shows a card naming the app and asks you to allow or deny access. Starting with Read aloud in Obsidian shows one approval card the first time. Apps you’ve already allowed can reconnect without another card. In Settings → Connections, you can revoke each app’s access or turn off Allow app connections. To reconnect after revoking access, click Connect for that app in Settings. App access, Univocal’s read shortcut in connected apps, and playback controls are on by default.

Univocal saves Connect settings and connection records in ~/Library/Application Support/Univocal/Connect/state.json. This includes:

Revoke removes the app’s access grant and ends its active sessions. It does not delete the saved instance name, such as an Obsidian vault name. That name has no expiry, and Univocal currently has no control that removes it. Turning off Allow app connections ends active sessions and connections but does not delete saved Connect state.

Connect state files have owner-only read and write permissions (0600). Connect folders have owner-only access permissions (0700).

Text read through Connect is not saved to Univocal’s reading history and is not logged. The connected app receives reading progress, including text ranges and playback status. In Obsidian, the plugin uses that progress to highlight words in your note.

From plugin version 0.1.3, the Obsidian plugin stores its connection credential in a file outside your vault. Only your macOS user can read it. The plugin no longer uses the macOS Keychain. Its README explains where the file is stored and how to remove the credential.

The licence key

Activating a licence sends exactly two things to Lemon Squeezy, the payment processor: your licence key and this Mac's name. Never any content — not a word you dictated or read. The app re-checks the key occasionally when the network happens to be available, and the check fails open: an unreachable server never locks you out, and only a definite answer that the key was refunded or moved to another Mac changes anything. If you want to watch it happen, the only host the app ever contacts beyond your own machine is api.lemonsqueezy.com for this check, and our own domain for update checks and for issue reports you choose to send.

The update check

About once a day, the app checks univocalapp.com/updates/appcast.xml for a newer version. The request includes the app name, the app version and the version of Sparkle, the updater. It includes no identifier, settings or content you dictate or read.

We use these checks to estimate how many copies of the app are in use. For each check, we record the day, the app version and a hash of your IP address (the address, or for IPv6 its network prefix). We do not store the IP address itself.

The hash uses a random value for the current month. During that month, we can recognise checks from the same address. We do not try to work out the address from the hash. On the first day of the next month, we delete that value. It can still be restored from our database host’s backups for up to 30 days after deletion. After that, the records can no longer be linked to an address. We delete the records after 13 months.

The browser extension

Univocal Read Aloud works in Chrome, Microsoft Edge, Brave, Vivaldi and Arc on Mac. When you ask it to read page text aloud, it sends that text only to the Univocal app on the same Mac. The connection uses the browser’s native messaging and Univocal’s helper program. The page text never leaves your Mac and is not stored.

Univocal asks for permission to connect once for each browser profile. The extension keeps the permission token in its local storage. Your extension settings sync through your browser’s own sync storage. The extension does not require an account or use analytics.

The extension uses the activeTab, scripting, storage and nativeMessaging permissions. It also runs a content script on all HTTP and HTTPS pages to show the hover ▶ button. At installation, Chrome warns that the extension can “Read and change all your data on all websites” and “Communicate with cooperating native applications”.

Analytics, telemetry, crash reports

The app has no feature-usage analytics or automatic crash reporting. We do not know which features you use or when the app crashes.

We do estimate how many copies of the app are in use, using the update checks described above. Those checks do not tell us what you dictate or read, or which features you use.

Reporting a problem

Report Issue… (in the menu-bar menu and Settings › General) is the one way the app tells us anything, and only when you press Send Report. Nothing is sent when you open the form, and nothing in the background.

What is sent is exactly what the form shows: the topic and description you write, the reply-to email address if you give one, and the block of facts under "Sent with your report": app and macOS versions, the Mac model, chip and memory, free disk space, which speech models are on disk, your language and voice settings, permission states, and whether the app is licensed or in trial. Never the licence key, never your name, and never anything you dictated or had read aloud. The app's log is included only if you tick "Include recent log", and only after names, email addresses and keys are removed from it; the form shows the log as it will be sent.

It goes over HTTPS to univocalapp.com/api/report, which keeps a copy of the report (so a report cannot be lost if forwarding it fails) and emails it to our support inbox. Alongside the report we record when it arrived and the country Cloudflare places the request in. Your IP address is used only to limit how many reports one network can send, and is not stored with the report. Reports are used only to answer and fix what they describe; to have one deleted, write to support@univocalapp.com.

If sending fails, the form offers to put the same report in an email from your own mail app, or on the clipboard, and you send it yourself.

Third-party services

None at runtime in the app, except when you send an issue report: it passes through Cloudflare, which hosts univocalapp.com and stores the report, and arrives in our support inbox, which is hosted by Google (Gmail). Purchases are handled by the payment processor named on the purchase page, which sees your payment details under its own privacy policy; we receive only the information needed to issue and support a licence.

The website

univocalapp.com is a website, not the app, and its footprint is separate:

Children

The app is not directed at children and collects nothing from anyone, so nothing is collected from children either.

Changes

If a future version ever sends anything anywhere, this document will say so plainly before that version ships, and the change will be in the changelog. A version that quietly started reporting usage would be a betrayal of the only thing this product actually promises.

Contact

Questions: support@univocalapp.com