Back to Home

Trust Center

How VerbScribe Handles Data

VerbScribe combines desktop dictation, web transcription, AI transformation, documents, and meeting intelligence. This page explains the main data flows in plain English so you can decide which features fit your privacy, security, and cost requirements.

Browser Transcription

  • Browser mode is the simplest way to start without adding API keys.
  • Audio is handled by the browser speech-recognition path instead of VerbScribe desktop capture.
  • VerbScribe stores the resulting transcript only when you save or process it in the app.

Desktop Flux Transcription

  • The desktop app captures microphone/system audio only after you start dictation.
  • Audio chunks are sent over an authenticated connection to VerbScribe, then relayed to the speech provider used for that session.
  • Raw desktop audio is treated as transient session data; the product workflow stores text transcripts and usage records, not long-term raw audio files.

BYOK AI Transformation

  • Bring Your Own Keys is optional advanced setup for users who want provider-level control.
  • Keys are submitted to VerbScribe over HTTPS, encrypted on the server before database storage, and decrypted only when needed for provider calls or direct client-side provider workflows.
  • When you use your own provider keys, provider usage and provider billing stay under your own provider account.

Gemini File Search and RAG

  • Gemini File Search uses your Gemini key because persistent Google/Gemini stores must belong to the user account that owns the data.
  • When RAG is enabled, relevant document context can be sent with your transcript or question to the selected AI model.
  • VerbScribe labels RAG and web-search context so you can distinguish retrieved context from generated text.

Meeting Assistant

  • Botless meeting capture runs from your desktop workflow and can use transcript context for live insights.
  • Bot meeting mode uses a visible VerbScribe notetaker and should be used only where meeting consent requirements are satisfied.
  • Meeting insights may use transcript snippets, selected documents, and web results depending on the features you enable.

What VerbScribe Stores

  • Account profile and authentication/session records.
  • Saved transcriptions, generated outputs, reports, and export history where applicable.
  • Uploaded documents, document metadata, retrieval chunks, and project settings.
  • Custom styles, prompts, model preferences, and meeting/RAG settings.
  • Encrypted API-key records and non-secret metadata such as provider name and last-used timestamp.
  • Subscription, billing status, and usage counters needed for limits and support.

Key Security Model

API keys are sensitive credentials. VerbScribe stores them encrypted at rest and uses authenticated routes for key management. Some workflows require decrypted keys at runtime so the app can call the provider you selected.

For maximum control, you can revoke a provider key in the provider console at any time, then delete it from VerbScribe Settings.

Deleting Keys and Data

  • Delete API keys from Settings when you no longer want VerbScribe to use a provider account.
  • Delete saved transcriptions, documents, and projects from their relevant workspace pages.
  • Disconnect provider access by rotating or revoking keys directly in the provider console.
  • Contact support for account-level deletion or billing-data questions that cannot be completed in-app.