Privacy Policy for Audio Transcriber

Last updated: October 10, 2026

Audio Transcriber ("we", "us", or "our") provides a Chrome extension that helps users convert audio and video into text transcripts. This Privacy Policy explains what information the Audio Transcriber extension and our backend collect, how we use it, and when it is shared with service providers, including payment processing and subscription management.

By using Audio Transcriber, you acknowledge this Privacy Policy. If you do not agree, please do not use the extension.

Information We Collect

Audio, video, and captured tab audio

When you choose to transcribe a local file or record audio from a browser tab, the extension processes the audio or video you selected. The selected content is uploaded to our backend infrastructure so it can be converted into text.

Audio and video content may include personal or sensitive information depending on what is present in the recording. You should only upload or record content that you have the right to process.

Transcription results

The extension receives generated transcripts from transcription service providers and displays them to you in the extension interface. A transcript may include personal or sensitive information if that information is present in the uploaded or recorded content.

Google account and authentication information

You may use Google Sign-In to create or access an Audio Transcriber account. If you sign in, Google and Firebase Authentication provide or process information needed to authenticate you. We receive and store:

• the email address associated with the Google account you selected;
• whether that email address is verified;
• a Firebase Authentication user identifier (Firebase UID);
• an internal Audio Transcriber account and support identifier;
• account creation and last-seen timestamps.

The extension uses authentication credentials and tokens to establish and maintain your session. Our backend receives a Firebase ID token to verify authenticated requests. We do not receive your Google password, and we do not intentionally record authentication tokens or Authorization headers in application logs.

Anonymous identity linking

Before you sign in, the extension uses an anonymous identifier to associate requests and usage with the same installation. When you sign in, we link the current anonymous identifier to your Audio Transcriber account. Usage from the linked anonymous identifier is then counted as part of your authenticated usage for the applicable usage period.

If you sign in after reaching the guest limit, a pending transcription may be reassigned to your account so processing can continue without uploading the file again. The link between the anonymous identifier and the account remains after sign-out unless it is deleted following a verified request.

Payment and subscription information

When you start checkout for a paid subscription, we provide Monetize with your internal Audio Transcriber account identifier and verified email address to create checkout, associate the purchase with your account, and manage your subscription.

To provide paid access, we receive and store:

• your payment provider user identifier and its link to your account;
• subscription identifiers, status, and whether a subscription is active;
• your plan and the dates covered by paid access;
• identifiers, types, and timestamps of payment, subscription creation, update, cancellation, and refund events;
• event receipt and processing timestamps and a checksum of the provider message.

We also receive information about the next payment, when available, to display it in the extension. These records are payment information even though they do not contain card details.

Checkout opens on a separate payment service page. Card details, including card numbers and CVC/CVV codes, are processed by the payment service and its payment partners. The extension and our transcription backend do not receive or store those details.

Usage and transcription metadata

We may collect technical and usage information needed to operate, protect, debug, and improve the service, including:

• an anonymous user identifier generated by the extension;
• a separate pseudonymous identifier used for analytics and feature flags;
• a device identifier used for analytics and feature flags;
• extension version and supported client capabilities;
• authentication availability, sign-in status, and sign-in events;
• selected transcription language;
• whether speaker separation was enabled;
• approximate audio duration;
• upload and transcription status;
• transcription mode;
• service provider response status;
• error messages and diagnostic events;
• timestamps of requests;
• usage totals for metering, applying service limits, and abuse prevention.

Local extension storage

The extension stores anonymous, analytics, and device identifiers in your browser's local extension storage. If you sign in, Firebase Authentication also stores session information in browser storage so that your session can be restored when you reopen the extension.

Local authentication data is cleared when you sign out, clear the extension's stored data, or remove the extension. Signing out also clears cached Google authentication tokens used by the extension and creates a new anonymous identifier for subsequent guest use.

Automatically processed technical information

When the extension communicates with our backend and service providers, standard technical information may be processed automatically, such as IP address, request headers, browser information, and server logs. This processing is necessary for network communication, security, fraud prevention, debugging, and service reliability.

Information We Do Not Collect

The extension and our transcription backend do not intentionally collect your mailing address, phone number, payment card details, Google password, contacts, full browsing history, or the contents of web pages you visit. Information you enter on the separate checkout page is processed by its operators under their own policies.

Google Sign-In requests access to your Google account email address for authentication. It does not request access to your Gmail messages, Google Drive files, contacts, or calendars.

The extension uses Chrome permissions only to provide its stated transcription and authentication features. Browser tab audio is accessed only when you start a recording or transcription action that requires it.

How We Use Information

We use the information described above to:

• provide audio and video transcription functionality;
• upload, process, and retrieve files for transcription;
• generate and display transcripts;
• authenticate users through Google and Firebase Authentication;
• create and maintain Audio Transcriber accounts;
• link guest usage and eligible pending transcriptions to an account;
• calculate and display usage limits and remaining usage;
• create checkout, link subscriptions to accounts, and provide paid access;
• check subscription status, process payment and refund events, and cancel renewal at your request;
• support speaker separation and language selection features;
• measure usage for service limits, reliability, and abuse prevention;
• debug errors and improve performance;
• operate feature flags and gradual rollouts;
• protect the service from fraud, misuse, and technical failures;
• identify an account when responding to verified support or privacy requests.

Data Sharing

We share information only as needed to operate the extension, provide transcription and authentication functionality, process payments and manage subscriptions, protect the service, and comply with law.

Backend, hosting, and storage infrastructure

Uploaded files, recorded tab audio, generated file links, account and identity records, usage records, subscription and payment event records, and related metadata are processed by our backend, hosting, database, and cloud storage infrastructure so the extension can authenticate requests, upload files, send content for transcription, retrieve results, apply usage limits and paid access, and delete temporary files where supported by the current processing flow.

Google and Firebase Authentication

When you choose Google Sign-In, Chrome obtains a Google OAuth credential for the account you select, and the extension uses it with Firebase Authentication. Google and Firebase process account identifiers, your email address, authentication credentials, tokens, and related technical information to complete sign-in and maintain the session. The Google OAuth credential is not sent to our transcription backend; the backend receives a Firebase ID token for verification.

Monetize and payment partners

We use Monetize through platform.audio-transcriber.pro for checkout and subscription management. Our backend provides your internal account identifier and verified email when creating checkout, and provider user and subscription identifiers when checking subscription status or cancelling renewal. Monetize returns checkout links, purchase and subscription information, and payment event notifications.

On the checkout page, Monetize and its payment partners may process payment and contact information you enter, your IP address, and other technical information necessary to complete payment and prevent fraud. Their processing and retention are governed by the applicable operators' policies presented at checkout. We do not send Monetize uploaded audio or video, recorded tab audio, transcript text, or Google and Firebase authentication tokens.

Transcription providers

Audio or video content may be sent to transcription providers that process the content and return transcript results. Depending on the selected transcription mode and service availability, we may use providers such as Lemonfox and Deepinfra.

Analytics and feature flagging providers

We use Amplitude for product analytics and feature flagging. Amplitude may receive pseudonymous analytics and device identifiers, event names, extension version, selected settings, approximate audio duration, backend selection, authentication availability, sign-in events, and error or reliability events.

We do not send uploaded audio, video files, recorded tab audio, transcript text, Google account email addresses, Firebase UIDs, authentication tokens, backend anonymous identifiers, or internal Audio Transcriber account identifiers to Amplitude.

Fallback infrastructure

If the primary upload, storage, or transcription path is unavailable, the extension may use fallback infrastructure, including Vercel, to keep the transcription service working.

Legal and safety reasons

We may disclose information if required by law, legal process, or a valid governmental request, or if we believe disclosure is necessary to protect the rights, safety, and security of users, the public, our service, or our infrastructure.

Chrome Web Store and Google API Limited Use

We use user data only to provide and improve Audio Transcriber's single purpose: converting user-selected audio and video into text transcripts, including the authentication, usage controls, payment, and subscription access management needed to provide that service.

We do not sell user data. We do not use uploaded audio, video, recorded tab audio, transcripts, or Google account information for advertising. We do not transfer user data to data brokers or advertising networks. We do not use user data to determine creditworthiness, lending eligibility, employment eligibility, or similar decisions.

Our use and transfer of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Our use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.

Data Retention

Uploaded files and recorded audio are kept only as long as reasonably necessary to provide transcription, operate the service, troubleshoot failures, and protect against abuse. Where supported by the current processing flow, files may be deleted after successful transcription.

Account records, including email, Firebase UID, internal account ID, anonymous identity links, and account timestamps, do not currently have a fixed automatic deletion period. We retain them while the account remains associated with the service and for as long as needed to authenticate users, maintain usage accounting, prevent abuse, provide support, resolve disputes, and comply with legal obligations.

Payment account links, subscription and access records, and received payment events do not currently have a fixed automatic deletion period. We retain them as needed to provide and verify paid access, handle repeated or delayed notifications, provide support, prevent fraud, resolve disputes, and comply with legal obligations. Cancelling a subscription does not itself delete these records. Payment operators determine retention periods for the data they process in their own policies.

Transcription metadata, anonymous and analytics identifiers, usage records, diagnostic logs, and service reliability data may be retained for as long as necessary to operate the service, measure usage, prevent abuse, debug issues, and comply with legal obligations. Following a verified deletion request, we delete or anonymize account data where reasonably possible, except for information that must be retained for legal, security, fraud-prevention, or dispute-resolution purposes.

User Controls and Choices

You can stop using Audio Transcriber at any time. Signing out ends the local authenticated session. You can remove all locally stored extension data by clearing the extension's stored data or removing the extension from Chrome.

Signing out ends the local authenticated session but does not delete your backend account, its link to previously used anonymous identifiers, or related usage, transcription, and subscription records. Signing out, clearing local data, or uninstalling the extension does not cancel automatic subscription renewal.

You can cancel subscription renewal using the corresponding function in the extension. If it is unavailable or cancellation fails, contact support at the address below. Cancelling renewal and requesting data deletion are separate actions; if you request deletion, specify whether you also want to cancel renewal.

You may contact us to request access, deletion, or correction of personal information associated with your use of the extension. If you are signed in, include the Support ID shown in the extension. We may require confirmation through an active signed-in session or another reasonable verification method; knowledge of an email address alone may not be sufficient to authorize account deletion.

Account deletion is currently handled manually. After verifying a request, we will delete or disable the corresponding Firebase Authentication account and delete or anonymize related backend account data where reasonably possible, subject to the retention exceptions described above. For information processed by payment operators, separate requests to those operators may be necessary; our support team can help identify the appropriate operator.

Security

We use reasonable technical and organizational measures to protect information processed by the extension and our backend infrastructure. However, no method of electronic transmission or storage is completely secure, and we cannot guarantee absolute security.

Children

Audio Transcriber is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information through the extension, please contact us so we can take appropriate action.

International Processing

The service providers used to operate Audio Transcriber may process information in different countries. By using the extension, you understand that your information may be processed outside your country of residence.

Changes to This Policy

We may update this Privacy Policy from time to time. When we make changes, we will update the "Last updated" date above. If our data practices change, we will disclose those changes in the extension and request consent where required. Continued use does not replace separate consent where such consent is required.

Contact Us

If you have questions about this Privacy Policy, want to exercise a privacy right, or want to request account deletion, contact us at:

transcriber.tools@gmail.com