Media2Text

Privacy Policy

Effective: August 8, 2026 · Last updated: October 3, 2026

This policy explains how Media2Text handles information when you use our website and transcription workspace. Media2Text is designed to limit the media sent to our servers: for supported video workflows, your browser prepares an audio track locally and the original video is not uploaded for transcription.

Information we handle

How we use information

We process information to provide transcription, speaker and timestamp features; create requested exports; secure and troubleshoot the service; prevent abuse; answer support requests; and improve reliability. We do not sell personal information or use uploaded recordings to target advertising.

Media processing and retention

Prepared audio must be transmitted to the selected transcription infrastructure for processing. The original video remains on your device in supported browser-extraction workflows. Processing files, results and operational logs are retained only as needed to deliver the requested workflow, support workspace features, maintain security and meet legal obligations. Retention can differ between guest and account-based features. Product controls may let you delete a transcription or cached audio sooner.

Do not upload content you lack permission to process. Recordings can contain sensitive personal data, voices and confidential conversations.

Service providers and international processing

We may use hosting, storage, security, analytics, authentication and AI processing providers acting on our instructions. Depending on the selected infrastructure and your location, data may be processed outside your country. We use reasonable contractual and technical safeguards where required.

Cookies, browser storage and trial-abuse prevention

Media2Text may use strictly necessary cookies or browser storage for authentication, security, preferences and application state. To enforce the one-time free transcription trial, the browser also calculates an abuse-prevention identifier from technical browser and device characteristics. The server stores domain-separated keyed digests of the browser identifier, random device identifier and network address; it does not use these risk identifiers to authenticate you or reveal another browser's transcript history. Minimal abuse records also use keyed digests of verified identities and trial usage. Cross-account risk matching and deleted-account anti-regrant records are limited to 180 days; an active account retains its own cumulative entitlement usage while that account exists. These records do not retain raw email addresses, raw network addresses, recordings or transcript content. Provider-cost records contain only operational identifiers, processing category, timestamps and cost or usage amounts, are kept separately from user works for up to 180 days, and do not disappear when a work is deleted. Browser risk signals may be shared by legitimate users and are not used alone to revoke paid or gifted minutes.

Optional advertising measurement

Google Ads measurement is off until you choose Accept. Rejecting or leaving the choice unanswered does not affect transcription, prices or free minutes, and does not load our Google Ads tag. With consent, we store allowlisted advertising click and campaign identifiers (GCLID, GBRAID, WBRAID and UTM fields) to connect a visit with a purchase. We stop using this attribution after 30 days; expired server identifiers are erased by the next hourly cleanup. Your choice is stored separately so we can remember a refusal.

For an eligible payment confirmed by Stripe or PayPal, we send Google Ads an opaque transaction identifier, the actual amount paid and its currency. Google may also receive advertising cookies, a sanitized page category and technical connection information such as your IP address and browser details. We do not send email addresses, account IDs, uploaded media, filenames, transcript content, private record links or payment credentials to Google Ads. Enhanced conversions and personalized advertising are not enabled. Google processes the data under its privacy policy.

Use Privacy choices on any page to reject or withdraw consent. Withdrawal clears this browser's advertising identifiers, stops new measurement and refreshes the page to unload the tag; save edits and finish uploads first. When signed in, we also revoke account-linked attribution; an offline request is retried after connectivity and sign-in return. Clearing browser storage or withdrawing cannot undo information already sent to Google. Google-side retention is governed by Google's policy, not our 30-day attribution window. Normal billing records remain subject to payment, accounting and legal retention requirements.

Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, restrict or export personal information, or object to certain processing. You can also clear local browser data and avoid uploading a recording. To make a privacy request, email privacy@media2text.app. We may need to verify your request.

Security

We use reasonable administrative and technical safeguards, but no online service can guarantee absolute security. Protect access to your device and account, and avoid uploading highly sensitive material unless the risk is acceptable to you.

Children

The service is not directed to children under 13, or the higher minimum age required in their country. We do not knowingly collect their personal information without appropriate authorization.

Changes and contact

We may update this policy as the service evolves. The current version and effective date will remain available here. Questions or requests can be sent to privacy@media2text.app.