Privacy Policy

Introduction

This Privacy Policy explains how Scribe Saas, LLC ("we", "us" or "our"), the company that operates ScribeToAny, collects, uses, stores and protects your information when you use our audio and video transcription service (the "Service"). By using the Service, you agree to the practices described here.

Who We Are

ScribeToAny is operated by Scribe Saas, LLC. For the personal data described in this policy, Scribe Saas, LLC is the controller — the party that decides why and how that data is processed. Where a payment provider acts as Merchant of Record for your purchase, that provider is independently responsible for the payment data it collects; see "Payment Data" below.

You can reach us about any privacy matter, including a request to exercise your rights, through our contact page.

Information We Collect

Account information: your name and email address, provided when you register or contact us, and managed through our authentication provider.
Uploaded media: the audio and video files you upload or import for transcription.
Transcripts: the text transcripts generated from your media, including any edits you make.
Usage and quota data: how you interact with the Service, including transcription minutes used, jobs run, and pages visited.
Device and log data: technical details such as IP address, browser type and operating system.
Payment metadata: limited billing details needed to manage your subscription. We do not store your card numbers (see Payment Data).

How We Use Your Information

We use your information to provide and maintain the Service, transcribe your media, manage your account and subscription, provide customer support, enforce usage quotas, improve and secure the Service, and detect and prevent abuse.

Uploaded Files and Transcripts — Retention and Deletion

Original media is deleted automatically. After your file has been transcribed, the original uploaded audio/video is automatically and promptly deleted from our storage. If a transcription fails, the original file is retained only for a short retry window (currently up to 7 days) and then deleted.
Transcripts are kept until you delete them. Your generated transcripts remain available in your account so you can view, edit and export them, and are stored until you delete them or close your account.
You are in control. You can delete your transcripts at any time from within the Service.

No Training on Your Data

We do not use your uploaded media or your transcripts to train machine-learning models, and we don't sell or give them to anyone for that purpose. Your content is processed only to produce and deliver your transcripts to you, and the AI summaries or answers you request.

Some optional features send transcript text to a third party that handles it under its own terms: translation (Google Translate), the AI assistant (summary and chat), AI apps you connect to your account, and Export to Notion. Each is described below, and none of them runs unless you use it.

Optional Translation (Google Translate)

Translation is optional and happens only when you choose Translate on a transcript. When you do, the text of that transcript is opened in Google Translate through a signed link that expires after 24 hours, and Google processes that text under Google's own terms and privacy policy. Only the transcript text is shared, never your uploaded audio or video. If you save the result, the translated text is stored in your account with your transcript. If you never use Translate, none of your content is sent to Google.

Optional AI Summary and Chat

The AI assistant on a transcript (a summary, and questions about the recording) is optional and runs only when you use it. When you do, the text of that transcript and your question are sent through Cloudflare (our AI gateway) to OpenRouter, which forwards them to the third-party AI model provider that generates the answer. OpenRouter and that provider process the text under their own terms (see OpenRouter's privacy policy), and we cannot guarantee that they will not retain it or use it to train AI models. If a transcript contains information you don't want a third party to see, don't use the assistant on it.

Only the transcript text and your questions are sent, never your uploaded audio or video. The summary and chat history are stored in your account with the transcript; you can clear the chat at any time, and both are deleted when you delete the transcript. If you never use the AI assistant, none of your content is sent to an AI provider.

Connected Apps (AI Assistants via MCP)

You can connect an AI app that supports the Model Context Protocol (MCP), such as ChatGPT or Claude, to your ScribeToAny account. Nothing is shared until you sign in and click Allow on our connection screen, which names the app asking for access.

Once connected, the app can, on your behalf:

list your transcripts (name, status, language, duration, creation date);
read the text of a transcript, with timestamps and speaker labels;
check your plan usage;
see your account name and email address, if the app asks for them when connecting, so it knows which account it is using;
start a new transcription from a link you give it, or from an audio or video file you attach in the app (for example in ChatGPT), which counts toward your plan's limits like any other transcription.

A connected app cannot edit or delete your transcripts, and it never receives your uploaded audio or video files. When you attach a file in ChatGPT, OpenAI gives us a temporary link to it; we download the file from OpenAI to transcribe it and handle it like a file you upload here. We don't keep that link, so such a transcription can't be retried: attach the file again instead. What the app does with the data it reads (for example, showing it to its AI model) is governed by that app provider's own terms and privacy policy, not by this policy.

We store the app's registration (its name and the address it returns to) and the access tokens issued to it, linked to your account. Access tokens expire after one hour; a refresh token lets the app stay connected and expires 30 days after it was issued unless the app renews it. To cut off an app's access, contact us and we will revoke its tokens; all tokens are deleted when you close your account.

Optional Export to Notion

Export to Notion is optional and runs only when you click it on a transcript. The first time, you connect your Notion workspace through Notion's own authorization screen. When you export, we send that transcript's file name, language, duration, timestamps, speaker labels and text, plus a link back to the transcript, to Notion, which creates a private page in your workspace. Notion processes this content under Notion's terms and privacy policy. We never read your existing Notion pages; the connection is used only to create the pages you export.

To do this we store the access token Notion issues, your Notion workspace ID and name. Clicking Disconnect deletes them from our servers; to also remove ScribeToAny from your workspace, remove the connection in Notion's settings (Settings → Connections). Pages you've exported stay in Notion until you delete them there.

Payment Data

Payments are handled by our payment provider (Stripe or Creem). Your full card details are entered directly with the provider and are not stored on our servers. We receive only limited billing metadata (such as subscription status) needed to manage your account.

Your Rights

Depending on where you live, you may have rights under laws such as the GDPR or CCPA, including the right to access, correct, delete, or export your personal data, and to opt out of analytics. You can exercise these rights, or ask any privacy question, by contacting us.

Data Security

We implement appropriate security measures, including encryption in transit, time-limited presigned URLs for file access, and access controls, to protect your information from unauthorized access, alteration, disclosure or destruction.

International Data Transfers

We use global infrastructure (including Cloudflare's edge network), so your information may be processed in countries other than your own. Where required, we take steps to ensure your data receives an adequate level of protection.

Children's Privacy

The Service is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us personal information, please contact us.

Analytics

We use two kinds of analytics to understand how the Service is used and to improve it:

Cookie-based analytics (Google Analytics, Microsoft Clarity) load only after you accept analytics cookies in the cookie banner. You can change your choice at any time; see our Cookie Policy.
Cookieless analytics (Cloudflare Web Analytics) runs for all visitors. It does not set cookies, does not store anything in your browser, does not fingerprint your device and does not follow you across other websites. It records aggregated statistics such as pages viewed, the referring site, country, and browser and device type. Your IP address is used by Cloudflare only to process the request and is not used to identify you.
How you found us. When you create an account, we save the website that sent you to us (its address without any query string), the page you first opened, and any campaign tags in that page's link (such as utm_source), together with your country. We keep this only in memory in your browser until you sign up, so nothing is stored on your device, and we use it only to learn which sites and pages bring us users. It is deleted with your account.
Invites. If you sign up through another user's invite link, we record which user invited you and whether you have transcribed a file since. The inviting user sees only how many friends joined and how many transcribed, never who you are. It is deleted with your account.

We rely on our legitimate interest in understanding and improving the Service for the cookieless analytics. Cloudflare processes this data on our behalf as a service provider. You can object at any time by contacting us, or block the script with your browser's tracking protection or a content blocker; the Service works the same either way.