Privacy Policy
How VokeLine collects, uses, retains, and protects service data.
Last updated:
Scope
This policy applies to the VokeLine desktop client, Web account, gateway APIs, and support operations. Live microphone audio, imported audio files, transcripts, and desktop history stay on the device during local transcription unless you explicitly invoke a network-backed feature.
Data We Process
- Account and authentication data: email address, profile details, browser session records, verification state, and security events.
- Anonymous usage-security data: a random anonymous client identifier, client platform and version, normalized network information, and quota-claim records. The identifier is used only for guest quota and abuse prevention, not to create a signed-in device profile.
- AI requests: the current input and required options are sent to the configured provider only when you explicitly request an AI operation.
- External web search: when you explicitly choose web search, the desktop app opens the chosen search engine in your system browser and passes the current input text as the query. The request does not pass through the VokeLine gateway.
- Usage data: request identifier, operation, provider/model routing metadata, timestamps, status, bounded error classification, quota or credit reservation, and settlement records.
- Billing data: orders, subscriptions, payment event receipts, and credit ledger entries. Stripe processes full payment instrument details; VokeLine does not store full card numbers or CVC values.
- Support and uploaded files: content you intentionally submit for support or a feature that uses managed file storage.
Providers and Sharing
VokeLine does not sell personal information. Required request content may be sent to the selected AI provider. External web searches are handled by the search engine opened in your system browser. We also use infrastructure, email, storage, and support providers as necessary to operate the service, and use Stripe for checkout, subscriptions, refunds, disputes, and related billing services. Gateway AI credentials remain inside the internal security Worker and are not returned to clients.
Website Cookies and Anonymous Analytics
VokeLine uses essential cookies and similar technologies to support sign-in, security, checkout, language routing, desktop download access, abuse prevention, and core service operation. These essential technologies cannot be disabled in Cookie Preferences. VokeLine does not currently use advertising or marketing cookies.
On public pages, VokeLine enables Google Analytics and optional convenience features, such as the Google One Tap sign-in prompt, by default. You can turn them off by explicitly rejecting optional technologies through the Cookie control in a full public-page footer. Google Analytics may process page paths without query strings or fragments, page titles, and a limited set of product events such as sign-in, installer download, checkout creation, and subscription cancellation. We do not send email addresses, names, full user identifiers, search terms, AI input or output, support content, payment instrument details, OAuth information to Google Analytics.
Google Analytics may set first-party cookies such as _ga in your browser. Your optional Cookie settings are saved in the current browser for up to 180 days and can be adjusted at any time through Cookie in the footer of a public page. After optional Cookies are turned off, we stop sending new analytics data, disable the related convenience features, and delete the Google Analytics Cookies the website can clear. These settings apply only to the current browser and are not synchronized with the desktop client.
Retention and Security
VokeLine retains account, session, billing ledgers, and bounded usage metadata for service delivery, security, idempotency, quota enforcement, and reconciliation. Application logs and D1 do not intentionally retain full AI input or provider response bodies. Successful result payloads are encrypted and expire under the configured retention policy. Revocation invalidates affected sessions; financial and security records may remain where required for accounting, fraud prevention, or legal obligations.
We use transport encryption, access control, hashed secrets, encrypted result payloads, internal Worker service bindings, and audit-friendly request identifiers. No Internet service can guarantee absolute security.
Your Choices
You can update account information or sign out the current session from settings. You may request access, correction, export, or deletion where applicable. A regular account keeps one active desktop session at a time; a new sign-in ends the previous session. Deleting the desktop application does not by itself revoke a remote session; sign out or sign in from another client first.
Changes and Contact
Material updates will change the date above and may be announced through the service. Use the support contact published in VokeLine to ask privacy questions or exercise applicable rights.