Whisker Privacy Policy

1. Whisker's privacy approach

Whisker is designed as a local-first, ephemeral working aid for live interpretation.

• Local transcription and local translation can run on the user's Windows PC.
• Cloud transcription is used only when the user explicitly selects a Cloud provider.
• Normal live session content is temporary working state, not a conversation archive.
• The licensing service is separate from the live interpretation path and does not need call audio or transcript content to authorize the product.

2. Information processed locally

Depending on the features used, the application may process or store locally:

• Incoming audio buffers during an active call.
• Provisional and confirmed Native text, Target translation, and editing state.
• Client/LEP routing, speaker assignments, temporary session state, and Undo state.
• Application settings, provider configuration, downloaded models, and model metadata.
• Local diagnostic results and licensing state needed to recognize a trial or paid entitlement.

Local session content is designed to be discarded at call boundaries. Settings, models, and deliberate diagnostic artifacts are separate from live conversation state and may remain until the user removes them or uninstalls the product.

3. Cloud transcription and translation

When the user selects Cloud transcription, Whisker sends captured audio to the selected provider for the active session. The provider may process audio, transcripts, language metadata, timestamps, speaker identifiers, and other inputs required by its service.

The selected provider's privacy policy, retention, security, regional processing, and service terms apply to that Cloud session. Whisker does not silently switch a Local session to Cloud or send Local session audio to a Cloud ASR provider.

Target translation normally remains local through CTranslate2, including when Native text came from Cloud ASR. If the user explicitly enables supported provider-native translation, the selected provider may process that translation stream under its own terms.

4. Licensing and purchase information

The separate Whisker Licensing Service may process the minimum commercial data needed to operate trial and paid authorization, including entitlement, purchase, transaction, customer, protected device-fingerprint, license-key, device-token, lease, transfer, refund, and administrative audit information.

The service is not an interpretation backend. It does not require call audio, Native transcript, Target translation, Script content, Preset content, or Cloud ASR credentials for normal authorization.

Payments are handled through the Merchant of Record and payment provider shown at checkout. That provider's privacy policy also applies to information it processes for payment, tax, fraud prevention, refunds, and customer support.

5. Support and diagnostics

If you contact support, Whisker may receive information you choose to send, such as your name, email address, application version, Windows version, hardware details, error messages, and reproduction steps.

Do not send API keys, license keys, device tokens, private transcripts, recordings, or other sensitive content unless a support representative gives you a secure and specific process for doing so. Diagnostic artifacts remain local by default; review and remove sensitive content before sharing one.

6. What Whisker does not do by default

• Upload Local call audio for remote transcription.
• Use the licensing service to store or analyze call content.
• Create a hosted conversation archive from Interpreter Mode.
• Expose permanent Cloud-provider credentials to the ordinary WebView UI.

7. Security

Whisker uses application and operating-system boundaries appropriate to the product, including Native Host isolation for protected operations and Windows user-scoped protection for managed provider credentials where supported.

No security measure is perfect. Users should protect their Windows account, license credentials, provider keys, and any local diagnostic or session data. See the Security page for reporting guidance.

8. Retention and deletion

• Live session content is intended to be temporary and discarded at call boundaries.
• Settings and models remain until removed by the user or product lifecycle.
• Diagnostic artifacts remain until removed by the user.
• Licensing and purchase records remain as needed for entitlement, payment, fraud, support, accounting, and legal processes.

Cloud-provider retention is controlled by the selected provider's terms.

9. Privacy choices and rights

You can choose Local instead of Cloud when the required hardware and model are available. You can also avoid configuring optional Cloud providers and remove local settings, models, and diagnostic artifacts from your Windows machine.

Depending on where you live and which laws apply, you may have rights to request access to, correction of, deletion of, or information about personal data processed by the publisher. Contact the publisher through the privacy contact published with the official product without sending secrets or call content.

10. Children

Whisker is a professional desktop tool and is not directed to children. Do not use the product to collect or process children's information unless you have the permissions and safeguards required by applicable law.

11. Changes to this policy

This policy may be updated when the product, providers, licensing service, or legal requirements change. The effective date identifies the version in force. Material changes should be communicated through the product site, purchase flow, or another appropriate notice channel.

12. Contact

Before public release, publish the publisher's complete legal identity, registered address, privacy contact, and any required data-protection contact here and on the official product site.