Our commitment to protecting your privacy and personal data
2026/05/20
This Privacy Policy explains how TranscribeBee ("we", "us") collects, uses, stores, and shares information when you use transcribebee.com and our transcription service. It is written specifically for what this product actually does: convert audio and video files you upload into written transcripts. For a plain-English summary, see our Trust page.
Audio and video files are the most sensitive information you share with us, so we describe their lifecycle explicitly.
We do not sell your personal information, and we do not use your uploaded audio, video, or transcripts to train any model.
We use a small number of vetted third parties to operate the service. Each one is contractually limited to processing data on our behalf for the specific purpose listed below.
| Sub-processor | Purpose | Data shared |
|---|---|---|
| OpenAI | State-of-the-art speech-to-text used to transcribe your audio. Configured so submitted data is not used to train models. | Audio extracted from your uploaded file, language hint. |
| Cloudflare R2 | Encrypted object storage for uploaded files and transcripts. | Uploaded files, generated transcripts. |
| Neon | Managed PostgreSQL database for account, order, and metadata records. | Account, order, and transcription metadata. |
| Dodo Payments | PCI-compliant payment processor (Merchant of Record) handling checkout, invoicing, and refunds. | Name, email, billing address, payment details (we never see full card numbers), order amounts. |
| Resend | Transactional email delivery (verification, password reset, order receipts, failure notices). | Your email address and the body of system emails sent to you. |
This list covers third parties that actually receive your personal data or uploaded content. Standard infrastructure providers (e.g., our application host) that may incidentally process request logs are not listed here.
If you sign in with Google instead of email/password, that is a direct OAuth relationship between you and Google — we only receive the basic profile fields they return after you authorize the sign-in. Google's handling of that authorization is governed by its own privacy policy.
We will update this section when sub-processors change, with the page's date field bumped accordingly.
We use industry-standard safeguards: TLS in transit, encryption at rest in object storage, scoped database credentials, hashed account passwords, and least-privilege access for operational tooling. No system is perfectly secure, but the surface area is deliberately small.
Depending on where you live, you may have the right to:
To exercise any of these rights, email support@transcribebee.com from the address on your account. We respond within 30 days, usually much sooner.
Our service is hosted in the United States and the European Union via Vercel and Cloudflare R2. By using the service from outside these regions you understand that your data is transferred to and processed in them, under appropriate safeguards.
The service is not intended for children under 13 (or under 16 in the EEA). We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, contact us and we will delete it.
The data controller for this service is the operator of TranscribeBee. For any privacy question, data request, or to report a concern, email support@transcribebee.com or use our contact page.
We may update this Privacy Policy. Material changes are reflected by updating the date field above and, where appropriate, by emailing registered users. Continued use of the service after an update means you accept the updated policy.