Voread privacy.

Effective October 25, 2026 · Version 2026-10-25.1

What Voread processes when you read, dictate, activate or contact support.

Operator and contact

Reading, dictation and screen crops

• Reading: text you ask to hear passes through Voread’s Cloudflare speech gateway to Google Gemini or Cartesia, depending on the installed app version and its configured reading provider. Google Gemini returns audio, which is processed locally with Whisper to obtain word timing information for highlighting. Cartesia returns audio and word timing information.
• Dictation: microphone audio captured for your dictation request passes through the gateway to Deepgram. The transcription becomes a draft you can review.
• Screen crops: crop pixels are processed on your computer with Windows OCR. This crop-reading implementation does not send the crop image to speech providers. When read aloud, extracted text passes through the gateway to the configured reading provider, Google Gemini or Cartesia.

Online providers receive the content needed for the action you request. Their processing and retention are governed by their terms and the service settings used by Voread. We do not promise immediate deletion or zero retention by every provider.

On your computer

Settings, license/trial state and dictation drafts are stored in your local Windows profile. Drafts are kept in a local SQLite database, with up to 50 recent drafts. New drafts remove older records beyond that limit. Clear history deletes saved draft records; it does not securely erase disk remnants, backups or every local diagnostic file.

In protected reading and dictation mode, selected/cropped reading text and synthesized reading audio are held in memory rather than added to persistent reading history or a reading cache. Text you copy or insert is also handled by the destination app and, when copied, the Windows clipboard.

The app writes local boot, session and error diagnostics. Assistive logging filters text and transcript fields, but diagnostic files can still contain personal information. Review them before sharing. Local logs do not have a verified automatic age-based deletion schedule.

Account, trial and downloads

The commercial service runs on Vercel and stores records in Neon. Sign-in stores your verified email, account identifier, a device/installation hash, hashed challenge and session material, request and expiry timestamps, device slots and account-trial records. Resend processes sign-in email. Codes expire after ten minutes and sessions last at most 30 days unless revoked sooner. Trials and prior trial claims retain records to prevent repeated free trials. The public download does not ask for your email or create a download lead; hosting services still process technical request data.

The account website uses separate browser sign-in records and essential Secure, HttpOnly cookies. A browser-bound code expires after ten minutes; a browser session lasts at most 30 days and can be revoked by signing out. Website sign-in does not start an app trial, claim an installation or use a computer slot. Browser session tokens are not stored in JavaScript-accessible browser storage.

Polar handles billing and license management. Account access checks can associate your verified email with Polar customer, product, subscription and license identifiers. A signed-in billing action creates a short-lived customer portal link for the customer resolved from your verified email. The shared Darvy billing portal may also show your other purchases from that organization. New app access requires an account session; a license key alone is not a sign-in. Earlier activation and installation-trial records may remain while the new account model is in use.

Expiry of a code, session, trial, earlier activation link or download bucket does not automatically delete its database row. The commercial tables currently have no automatic cleanup schedule. Records are used to deliver access, prevent abuse, answer support requests and administer purchases.

Speech authorization and usage

To authorize speech, the gateway temporarily receives a device-bound account session and installation hash. The account service checks current access and derives the account’s allowance, including with Polar for paid subscriptions. Short-lived signed access proofs let the desktop enforce its local feature lock. Session tokens are stored securely on the computer and are not sent to speech providers. Master speech-provider keys stay on the server.

The gateway stores pseudonymous identifiers, short-lived grant tokens, timestamps, request counts, allowance counters and concurrent-session reservations. It uses these records to enforce access and spending limits. Period allowance records and operational daily counters have configured expiries; an hourly cleanup alarm removes expired records when it runs.

The gateway application does not log speech text, audio, crop images or credentials, and its Worker observability setting is disabled. These are application-level practices, not a guarantee about infrastructure logs, backups or provider records. We do not retain reading text or microphone audio in the commercial database.

Support messages

Messages sent to support@voread.app pass through Cloudflare Email Routing to the operator’s Gmail inbox. Cloudflare and Google receive the message and attachments. Support mail is separate from sign-in email sent through Resend. Avoid sending passwords, license keys, payment-card details or unnecessary private content.

Optional reporting and website services

The app has separate choices for optional product analytics and crash diagnostics, disabled by default. No external product-analytics destination is configured for this launch; crash reporting also requires a configured destination and consent. Necessary access, billing and abuse-prevention counters are separate from those optional choices.

The Voread marketing site does not configure third-party advertising pixels or product-analytics cookies. Hosting and linked account, billing and payment services can process technical request data under their own policies.

Access, correction and deletion

Contact support@voread.app to request access, correction or deletion of information held for Voread. We may ask for enough information to verify the request. Records needed for purchases, legal obligations, security or resolving a dispute can require different handling from local drafts or provider records. We do not promise automated deletion across every system.

See the Terms for the subscription, service limits, cancellation and refund guarantee.