How it worksFeaturesPricingSecuritySign inStart free
Security & privacy

It records your meetings. So we take this seriously.

Privacy is not a setting in Woviq — it's the default. Here is exactly how your meetings are captured, processed, and protected.

No bot in the call

Woviq never sends a participant into your meeting. Capture runs in your own browser (tab audio plus your mic), mixed locally, then uploaded for processing.

We don't train on your data

Your recordings, transcripts, and summaries are never sold and never used to train models. They exist to serve you.

Audio is deletable

Once a summary is generated, the source audio can be removed. Delete a meeting and its audio, transcript, and summary are purged.

Encrypted in transit

All traffic runs over HTTPS/TLS. Audio is kept in private storage and ownership is re-checked on every request.

Narrow permissions

The Chrome extension only requests access to meet.google.com and the Woviq API. It asks for nothing it doesn't need.

Processed responsibly

Hinglish handling and INR billing are built in, and meeting data is processed only through the vetted providers listed below.

Who processes your data

A short, named list.

We keep the list of subprocessors short and name them plainly.

Neon
Serverless Postgres database
Vercel
Application hosting and private blob storage
Razorpay
Payments and subscriptions
Resend
Transactional email
Groq (Whisper)
Speech-to-text transcription
Google (Gemini, Chirp)
Summarization and Hinglish speech-to-text

We're a young product and we'll be honest about where we are. We don't yet hold formal certifications such as SOC 2; if that changes, we'll say so plainly on this page. Questions about data handling are welcome on our support page.

No bot. No catch.

Private by design.
Not by promise.

No bot joins, nothing is sold, nothing trains a model on you. Start free and see.