Overview

This Privacy Policy explains how Viora handles information when you use the Viora website, web account features, and Viora Desktop for macOS.

Viora is a cloud-assisted voice dictation and AI assistant product. Audio and related context may be sent to Viora backend systems so we can transcribe speech, refine dictation, run agent workflows, provide meeting captions, maintain subscriptions and credits, and support the product. Viora stores service data in protected backend systems and uses access controls and operational safeguards to protect it.

For Desktop task content, Viora's external model processing is limited to large-model calls through Fireworks AI. Viora does not sell your data, does not use your voice or text to train models, and does not send Desktop task content to unrelated external APIs or advertising services. Separate account, payment, email, hosting, authentication, and website analytics providers may process the limited data needed for those service functions.

Information We Collect

Account and authentication data

When you create or use a Viora account, we may collect:

Name, email address, profile image, account role, and account status.
Password authentication data when you use email/password login. Passwords are stored through our authentication system, not in plain text.
Google login identifiers and OAuth account records when you choose Google sign-in.
Session data, authentication cookies, JWTs, user agent, IP address, and login timestamps.
Invite code status, workspace or organization membership, and admin metadata when those features apply.

Subscription, billing, and credits data

When you subscribe, buy credits, or manage billing, we may store:

Plan, price, interval, credit balance, trial status, renewal status, cancellation status, invoice identifier, checkout session identifier, and payment provider customer identifier.
Payment status and webhook events needed to update your plan or credits.

Viora uses Stripe for payment processing. Viora does not store full card numbers or bank account details in its own application database.

Desktop audio and voice data

When you use dictation, agent mode, or meeting mode, Viora Desktop may collect and send to Viora backend systems:

Microphone audio.
System audio during meeting or loopback recording features when you grant screen recording permission.
Audio metadata such as duration, format, size, language, and selected microphone device information.
Transcripts, refined dictation text, agent answers, meeting captions, and text-to-speech response events.
Task identifiers, retry identifiers, processing status, timing, and error state.

Desktop recordings may also be saved locally on your Mac in the app's recordings folder unless Privacy Mode or the specific feature flow skips local persistence.

Context used to improve results

To make dictation and agent responses more useful, Viora Desktop may collect contextual information around a task, including:

Selected text.
Whether the cursor is in an editable field.
Active application name, application bundle identifier, and window title.
Browser page title or URL/domain when available from the focused window context.
Selected file names or file paths when a file-selection feature is used.
Language, formatting style, time zone offset, and shortcut timing.
Personal dictionary terms and custom skill names, descriptions, and guidance.
Available connector identifiers, such as whether a connector is connected, so the backend can decide which capabilities are available.

We collect this context only to provide the requested product behavior, such as deciding whether speech should become inserted text or an agent answer.

Text-input agent tasks

If you type or edit an agent prompt instead of recording audio, Viora may send the text input and the same limited task metadata to the backend.

Local history, records, and files

Viora Desktop stores some information locally on your Mac, including:

Dictation and agent history.
Recording file paths, filenames, size, format, duration, transcripts, task IDs, and agent event history.
Local settings such as language, shortcut preferences, selected microphone, Privacy Mode, launch-at-login, and UI preferences.
Local custom skills and optional skill files you create or install.

Local data remains under your operating system user profile. Anyone with access to your Mac account or backups may be able to access local Viora files.

Meeting notes and recordings

When you use meeting mode, Viora may:

Capture microphone and system audio.
Stream VAD-detected audio segments to Viora backend systems for live captions and related agent responses.
Save a combined meeting recording locally on your Mac.
Store notes, note recordings, transcript segments, backend task IDs, and session IDs when the notes feature is used.

Skills, learned workflows, and memory features

Viora supports custom skills, learned workflows, and memory-like guidance. Depending on the feature you use, we may store:

Custom skill names, descriptions, guidance, and optional local files.
Learned workflow drafts, active or disabled status, rationale, and updated timestamps.
Memory guidance, traits, events, and related user-controlled settings.

These features are used to personalize future Viora behavior. You can edit, disable, or delete supported records through the product where those controls are available.

Connectors and OAuth integrations

Viora may let you connect external services. When you connect a service, we may store:

Connector ID, title, connection status, OAuth tokens, token expiration metadata, and granted scopes.
The minimum metadata needed to show whether a connector is connected and available.

Current Desktop task content is not sent directly to third-party connector APIs. If a future connector feature reads from or writes to an external service on your behalf, we will disclose that behavior in-product and update this policy before using connector data in that new way.

Feedback and support data

If you send feedback, contact support, or report transcription quality issues, we may collect:

Your user ID, email address, task ID, recording ID, transcript, feedback message, source, and created timestamp.
Support messages and attachments you choose to provide.

Feedback may include sensitive content if you include it in the message or attach it to a report.

Diagnostics, logs, and telemetry

Viora uses local logs and optional production error telemetry to diagnose failures. Diagnostics may include:

App version, release, operating system, process type, environment, error messages, stack traces, network status, feature state, and timing.
Sanitized metadata about tasks, such as content length, count of selected files, connector count, skill count, and whether a token was present.

Remote telemetry is filtered to remove sensitive text fields such as tokens, authorization values, selected text, file content, transcripts, and content-like fields. Local logs on your Mac may contain more operational detail and are primarily used for troubleshooting.

Website, analytics, and cookies

When you use the Viora website, we may collect browser and usage data such as IP address, browser type, page views, referrer, approximate region, device information, cookie identifiers, and analytics events. Analytics scripts are used only when configured for the production website.

See our Cookie Policy for more detail about cookies and similar technologies.

How We Use Information

We use information to:

Provide dictation, transcription, agent answers, meeting captions, text-to-speech output, notes, and related Desktop features.
Authenticate users and keep Desktop synced with the web account.
Manage subscriptions, credits, invite access, and billing status.
Store user-controlled history, settings, skills, dictionary terms, notes, and learned workflows.
Improve reliability, latency, accuracy, security, and product quality.
Investigate bugs, abuse, fraud, billing problems, and support requests.
Communicate service updates, security notices, and support responses.
Comply with legal obligations and enforce our Terms of Service.

Backend Processing and Model Providers

Viora Desktop sends audio, text, and relevant context to Viora backend systems when cloud processing is needed. The backend may store the data securely to operate the service, provide history and support, investigate reliability issues, and maintain abuse and security controls.

For Desktop task content, Viora's external model provider is Fireworks AI. We send only the information needed to perform the requested transcription, refinement, or agent task. We do not send Desktop task content to unrelated third-party APIs, ad networks, or data brokers.

We do not use your voice, transcripts, prompts, files, connector data, or feedback to train models.

Privacy Mode

Privacy Mode is designed to reduce persistence for new tasks. In the current Desktop app, Privacy Mode:

Skips local recording or transcript record persistence for supported dictation and agent flows.
Sends a privacy_mode flag to the backend.
May keep temporary context in memory during an active private session so the assistant can respond coherently.

Privacy Mode does not make transcription fully local. Audio, text, and the limited context needed to complete the request may still be sent to Viora backend systems and, when needed for the model step, to Fireworks AI.

We do not sell personal information.

We may share information only as needed with:

Service providers that host, secure, monitor, email, authenticate, analyze, or process payments for Viora.
Fireworks AI for the limited model processing described above.
Stripe for payment processing and customer portal functions.
Google when you choose Google sign-in or authorize a Google connector.
Authorities, courts, or other parties when required by law or necessary to protect rights, safety, security, or prevent abuse.
Successors in a merger, acquisition, financing, reorganization, or sale of assets, subject to appropriate protections.

We require service providers to process information only for the services they provide to Viora and to protect that information.

Retention

We keep information for as long as needed to provide the service, maintain security, comply with legal obligations, resolve disputes, and enforce agreements.

Typical retention depends on the data type:

Account, subscription, credit, invoice, and security records are kept while your account is active and as needed for legal, accounting, tax, and anti-abuse purposes.
Desktop history and recordings stored locally remain on your Mac until you delete them or uninstall/remove local data.
Backend audio, transcripts, task metadata, meeting segments, notes, feedback, and learned workflows are kept as needed for product functionality, support, safety, and reliability unless deleted through available controls or a verified deletion request.
Diagnostic telemetry is kept for a limited operational period appropriate for debugging and release monitoring.

Your Choices and Controls

You can:

Sign out of Viora Desktop.
Delete local dictation and agent records where the product provides deletion controls.
Enable Privacy Mode for supported new tasks.
Manage microphone, accessibility, and screen recording permissions in macOS System Settings.
Disconnect supported connectors where connector controls are available.
Manage billing through the customer portal.
Request access, correction, deletion, export, or restriction of your personal information by contacting us.

We may need to verify your identity before fulfilling certain requests.

Security

We use administrative, technical, and organizational safeguards to protect information, including secure transport, access controls, production monitoring, and telemetry filtering. No system is perfectly secure, and we cannot guarantee that unauthorized access, loss, or misuse will never occur.

You are responsible for protecting your account credentials, device access, operating system account, local backups, and any files you export.

Children

Viora is not intended for children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to Viora, contact us so we can take appropriate action.

International Processing

Viora may process information in countries other than where you live. Where required, we use appropriate safeguards for international transfers.

Changes to This Policy

We may update this Privacy Policy as the product, providers, or laws change. We will post the updated version on this page and update the effective date. If a change materially affects how we use personal information, we will provide additional notice where appropriate.

Contact Us

If you have questions or requests about this Privacy Policy, contact us through the support channels listed in the site footer.