Scope

This Privacy Policy explains how information is handled when you use Phravia for Android, Phravia for Windows, or the Phravia website at phravia.com.

Phravia does not require you to create a Phravia account. In this policy, “Phravia” means the Phravia apps and their developer.

Information We Collect

Phravia stores the following information locally on the device where the app is installed:

  • Transcription history: The latest 20 transcribed texts may be saved in the app's private local History so they can be viewed and reused. This applies separately to the Android and Windows apps.
  • API keys: Keys for cloud AI providers you configure are stored locally using operating-system-protected storage where available. On Windows, Phravia uses Windows Credential Manager, with an encrypted current-user file as a fallback. These keys are not sent to Phravia.
  • App settings: Language, provider, model, output, keyboard, microphone, hotkey, and customization choices are saved locally as relevant to the platform.
  • Saved content: Saved replies, custom vocabulary, and other content you deliberately save in an app feature are stored locally.

Voice recordings: Phravia accesses the microphone when you start dictation or another microphone feature. Recordings are used to produce the transcription. The Windows app records audio in memory and does not write the recording to disk as part of its normal dictation flow.

Failed Android dictation recovery: If an Android dictation fails, Phravia may temporarily store the latest recording and related retry information—including the selected processing route and, where text cleanup failed, the raw transcript—so you can retry it. This information is removed after a successful retry, when you dismiss it, or after no more than 24 hours.

Text insertion and active fields: On Android, if you enable Phravia's Accessibility service or keyboard, Phravia uses that access to identify the active editable field, operate its input features, and insert the text you requested. On Windows, Phravia may locally inspect the active field, its selection, and nearby text as needed to place the transcription and detect secure or password fields. Phravia does not use this access to build a record of your screen contents or activity, and it does not send surrounding field content to the developer or an AI provider.

Clipboard: If you choose a copy option, the transcription is placed on the system clipboard. Windows may also use the clipboard temporarily as a text-insertion method and then make a best-effort attempt to restore its previous contents. Clipboard contents are subject to the operating system's normal behavior and may be accessible to other apps as permitted by the operating system.

Website Analytics

phravia.com uses Cloudflare to deliver and protect the website and may use Cloudflare Web Analytics to understand basic website usage. Cloudflare may process technical request information such as IP address, browser or device information, requested page, and request time.

Phravia uses this information to operate, secure, and improve the website, not for targeted advertising. Cloudflare handles this information under the Cloudflare Privacy Policy.

How We Use Information

Voice recordings and transcript text are processed according to the options selected in the app:

  • Cloud transcription: The recording, selected language, and request settings needed for transcription are sent directly to the cloud service selected for that dictation.
  • Online text cleanup: If online cleanup is enabled, the transcript and cleanup instructions are sent directly to the selected cleanup service. It may be different from the transcription service.
  • Offline processing: Where supported, offline transcription and cleanup process audio or text on the device. When both transcription and cleanup are offline, audio and transcript text are not sent to a cloud AI provider.
  • Android system recognition: If you select an Android system speech-recognition option, processing is controlled by the recognition service configured on the device and that service's privacy settings.

The resulting text may be inserted into the active app, copied to the system clipboard, or saved to local History depending on your settings and actions. Phravia may avoid inserting text into secure or password fields.

Phravia does not operate a dictation server that receives your recordings or transcripts, and it does not use app data for advertising.

Third-Party Services

The cloud services available depend on the platform, language, and feature you select:

  • Android: Groq, Google AI, Sarvam AI, OpenAI, Deepgram, ElevenLabs, Mistral, OpenRouter, Cohere, xAI, Fireworks, DeepInfra, Lemonfox, AssemblyAI, Gladia, Speechmatics, Rev AI, Soniox, Anthropic, DeepSeek, and Together AI.
  • Windows: Groq, Google AI, and Sarvam AI. The Windows app also offers supported offline models that process locally.

Only the service selected for the relevant transcription or cleanup route receives that audio or text. These providers process information under their own terms and privacy policies. Provider-side storage, asynchronous processing jobs, retention, training choices, and deletion are controlled by the provider and by the terms of your account with that provider.

Android purchases: Android purchases are processed by Google Play. Phravia does not receive or store your card number, bank details, or other payment credentials.

Phravia uses RevenueCat to display available products, validate and restore purchases, maintain access to purchased features, provide purchase support, and understand purchase performance. RevenueCat may receive:

  • a randomly generated app-specific customer identifier;
  • relevant app and device technical information; and
  • purchase information such as purchase history, Google purchase tokens, product identifiers, transaction status, renewal information, and entitlement status.

RevenueCat does not receive dictation recordings or transcript text through Phravia's billing integration. RevenueCat processes purchase information as Phravia's service provider under the RevenueCat Privacy Policy.

Managing, canceling, or refunding a Google Play purchase is handled through Google Play and is subject to Google's terms and policies.

App distribution, updates, and model downloads: Google Play and Microsoft Store process normal account, device, purchase, download, and update information under their own policies when you obtain or update an app. If you download an offline model, the hosting service may receive ordinary network-request information such as your IP address, requested file, and request time.

Support and Diagnostics

When you contact support, Phravia receives the email address, message, attachments, and diagnostic information you choose to send.

A prepared support email may include app version, device and operating-system information, permission or service status, selected language, provider and model settings, offline-model status, and recent app activity. If you deliberately include activity logs, those logs may contain recent dictated text. Saved History and API-key values are not automatically included.

You can review, edit, or remove prepared information before sending it. On Windows, temporary email-draft files may be created locally when opening a support request and are automatically removed after they are more than one day old. The Windows app also maintains a local crash log to help diagnose failures. Phravia does not currently use an automatic remote crash-reporting service.

Data Security

  • Provider credentials are kept in operating-system-protected storage where available.
  • Network requests to supported services use encrypted HTTPS/TLS connections.
  • History, settings, and Android failed-dictation recovery information are stored in the app's local storage.
  • Phravia does not sell personal or sensitive information and does not use dictation recordings or transcripts for advertising.

No security method is perfect. Users should protect access to their devices and provider API keys and should revoke a key with its provider if they believe it has been exposed.

Data Retention

  • Android or Windows transcription History: The latest 20 entries in each app, until cleared or the app's local data is removed.
  • Failed Android dictation recovery: Until successful retry, dismissal, or expiry after no more than 24 hours.
  • Windows recording: Held in memory during normal dictation processing and released afterward; it is not written to disk by the normal dictation flow.
  • API keys, settings, saved replies, and vocabulary: Until removed in the app or the app's local data is removed on that device.
  • Windows support drafts: Stored locally and automatically removed after they are more than one day old.
  • Windows local crash log: Stored locally until it is deleted or the app's local data is removed.
  • AI-provider data: According to the selected provider's terms, account settings, and retention policy.
  • Android purchase and entitlement records: According to Google Play's and RevenueCat's applicable retention practices and legal obligations.
  • Support correspondence and attachments: For as long as reasonably necessary to provide support, maintain appropriate business records, resolve disputes, protect security, and comply with law.
  • Website request and analytics information: According to Cloudflare's applicable retention practices.

User Rights and Control

  • Clear history: Delete saved transcriptions from the History screen in the Android or Windows app.
  • Delete failed Android dictation data: Dismiss the failed dictation or complete a successful retry.
  • Delete API keys: Remove configured keys in Settings and revoke them through the relevant provider if needed.
  • Delete local app data: Clear Phravia's app data or uninstall the app to remove locally stored information, subject to the operating system's normal app-data behavior.
  • Contact the relevant service: Contact the selected AI provider regarding data it retains under your account or its policies.
  • Contact Phravia: Request access to, correction of, or deletion of personal information controlled by Phravia, including an identifiable RevenueCat customer record where applicable.

Deleting a RevenueCat customer record does not cancel a Google Play purchase or erase records that Google or another party must retain. Subscriptions and purchases must be managed through Google Play.

Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or objection regarding personal information controlled by Phravia. You may also have the right to complain to your local data-protection authority.

Children's Privacy

Phravia is not directed to children under 13 and does not knowingly collect personal information from them. A parent or guardian who believes a child has provided information to Phravia can contact us to request deletion.

Changes to This Policy

We may update this policy occasionally. Significant changes will be communicated through app updates or on this page.

Contact

Questions or privacy requests can be sent to voiceflow.help@gmail.com.