Security & Trust

Last updated: 2026-04-18

Transcripts are sensitive: customer calls, voice memos, interviews, lectures. Here's exactly what happens to your audio when it passes through Whipscribe — short enough to read in a meeting, specific enough to forward to your security team.

At a glance

AI training
Never on your audio or transcripts
Retention
Audio kept 30 days on your plan
In transit
TLS 1.2+ end-to-end
Storage
Vultr EU / US — your region stays in-region
Third parties
No data sent to OpenAI / Anthropic / Google
Rights
Affirmative attestation on every upload

Data handling

What we receive

Where it lives

Everything is hosted on our own servers at Vultr (EU + US regions). Speech-to-text runs on the same host family — no third-party AI vendor ever sees your audio. The transcription engine is self-hosted. The storage layer is either Vultr Object Storage (S3-compatible) or an encrypted disk volume, depending on tier.

We do not use OpenAI, Anthropic, Google Cloud Speech, AWS Transcribe, or any other hosted model for the transcription itself. When a user opts to forward a finished transcript to an LLM (e.g. "send to Claude"), that action is their own — we don't proxy it and we don't store the result.

Retention

ArtefactGuest (anonymous)FreePaid
Uploaded audio3 days30 days365 days
Transcript (text)3 days (attached to the audio)Kept in your personal vault until you deleteKept in your personal vault until you delete
Job metadata3 days30 days365 days
Payment records7 years (statutory)

Ask us to delete sooner at contact@neugence.ai — we honour deletion requests within 7 days.

Your data is never used to train AI models

Not our models, not anyone else's. Uploads, transcripts, and derived artefacts are used solely to deliver the service you asked for. We do not sell data, and we do not share it with advertisers or analytics brokers beyond aggregate product metrics.

Authorization

We treat Whipscribe as a tool, not a library. You upload content, we transcribe it. That model depends on three things:

If you're recording a call, a lecture, or an event with other people in it, the law treats you as the party doing the recording. Whipscribe is the tool; you are responsible for obtaining consent from the other parties involved.

Twelve US states require all-party consent for recording audio (California, Connecticut, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, Nevada, New Hampshire, Pennsylvania, Washington). The EU's GDPR requires a lawful basis plus notice. When in doubt, disclose that the call is being transcribed.

Coming soon: auto-generated consent disclosure you can paste into the chat of a meeting or live Space. See the roadmap below.

Infrastructure

Sub-processors

VendorPurposeData they see
VultrCompute, object storageEncrypted blobs + metadata
Firebase (Google)Auth / sign-inEmail, OAuth profile
RazorpayPaymentsName, billing email, amount
CloudflareDNS + edgeIP, request metadata
PlausiblePrivacy-first analyticsNo cookies, no PII — aggregate page views only

Compliance roadmap

ItemStatusNotes
TLS 1.2+ / HSTSLiveAll traffic.
Data deletion on requestLiveEmail contact@neugence.ai; 7-day SLA.
Per-upload rights attestationLiveBlocking checkbox.
Regional storage (EU / US)LiveAccount region determines residency.
Consent-disclosure generator for meetingsQ2 2026One-click notice for live calls.
DPA (Data Processing Agreement) — Team / EnterpriseQ2 2026Available on request today for enterprise pilots.
SOC 2 Type IIPlannedTargeting 2027 once team-tier signups warrant it.
Customer-managed encryption keysPlannedEnterprise ask; scoped for self-hosted tier.

Responsible disclosure

Found a security issue? Please send it to security@neugence.ai (GPG on request). We commit to:

For enterprise buyers and SOC 2 reviewers: we'll gladly answer a security questionnaire and sign a DPA before a pilot. Email contact@neugence.ai and we'll turn a round in under a week.

Whipscribe is built by Neugence Technology Pvt. Ltd. See also the Privacy Policy and Terms of Service.