Privacy Notice
Last updated 1 October 2026
This notice explains what personal data Bear Tools collects, why we collect it, and what you can do about it.
The data controller is Individual Entrepreneur Aleksandr Gerasimov, Georgia, Tbilisi, Krtsanisi District, Settlement Ponichala 3, Building 5, Entrance 2, Floor 4, Auxiliary Storage Room. For anything privacy-related, write to apps@beartools.dev.
The short version
We collect as little as we can get away with. We do not sell personal data, and we do not run advertising trackers on this website.
What we collect
When you email us. Your email address and whatever you write, so we can reply and keep a record of the conversation.
When you buy a subscription. Payments are handled by our payment provider, which acts as merchant of record — you see who they are at checkout and on your receipt. They collect your name, email, billing address and payment details — the billing address is needed to issue a valid invoice and to calculate tax — and process them under their own privacy policy. Card numbers never reach our servers. We receive the order details we need to give you access and to keep proper accounting records: email address, product, amount, country and invoice data. For MP3 to Text, we also link the subscription to the random installation ID of the browser you bought it in, and of any browser you sign in from with a code we email to that address — that is how the extension knows Pro is on.
When you use an App with an account. The account email and the data you choose to store in the App, for as long as your account exists.
When you use YouTube Transcript Extractor. The extension runs only on the YouTube tab you have open. It reads that video’s available captions and limited metadata — video ID, title, channel, duration, caption language. It does not read your browsing history and it does not run on other sites.
- Reading and searching a transcript happens in your browser. That text is not sent to us. If the browser-side caption request fails, the extension asks our API for the captions instead, sending the video ID and language.
- The AI features — enhanced transcript, translation, summaries and chat — are processed on our servers and by OpenAI. Producing a result sends the caption cues, the video ID and title, the language, and, for chat, your question and up to ten recent messages from that conversation. This text is used to answer the request and for nothing else: we do not sell it and it is not used to train models.
- Your installation is identified by a random installation ID, which we exchange for a short-lived API session and use to apply usage limits and to tell a free allowance from a paid subscription. There is no account and no password; you never send us credentials for anything.
- Our backend providers receive the technical data any server request carries: your IP address, the time, which endpoint was called and whether it succeeded. This is what the Chrome Web Store listing means by “location” — an IP address, not GPS, and we do not derive a position from it beyond what rate limiting and abuse prevention need.
- Product analytics record which feature was used, whether it worked and which extension version you are on. They deliberately exclude transcript text, your questions and answers, video titles and full URLs.
- Feedback you choose to send — a rating, a message, and anything you write in it.
When you use MP3 to Text. The Transcript engine runs on your computer: the recording and its transcript stay in your browser and are not sent to us, and its minutes are counted in the browser too — we keep no usage record for it. When you choose Pro Transcript, the recording is uploaded over an encrypted connection to our storage and transcribed by Deepgram on our behalf, for that purpose only. The recording is deleted as soon as the transcript is back, or when the run fails or is cancelled; the job record — file name, installation ID and the finished transcript — is deleted automatically within 24 hours. Your installation is identified by a random installation ID, which our service uses to count Pro Transcript minutes — free and paid — and to tell a free allowance from a paid subscription. The full detail is in the extension’s own privacy policy.
When you visit this website. Our host records standard server logs (IP address, page requested, user agent, timestamp) for security and diagnostics. We use privacy-friendly, cookie-free analytics for aggregate visit counts; it does not build a profile of you or follow you across sites.
Why we are allowed to use it
- To provide the service and the App you paid for — performance of a contract.
- To take payment and keep invoices — legal obligation and contract.
- To answer support email and keep the service secure — legitimate interests.
- For anything optional, such as a mailing list — your consent, withdrawable at any time.
Who else sees it
Only the processors we need to run the business:
| Processor | Purpose |
|---|---|
| Our payment provider, as merchant of record | Payments, invoicing, subscription management, tax |
| Vercel | Website hosting and cookie-free visitor analytics |
| Railway | Backend hosting for the extension APIs and their rate limits, and short-lived storage of MP3 to Text uploads and job records |
| Deepgram | Speech recognition for MP3 to Text’s Pro Transcript |
| OpenAI | Processing the AI features — enhanced transcripts, translation, summaries, chat |
| PostHog (EU Cloud) | Product and website analytics, with session recording disabled and Do Not Track respected |
| Supabase | Storing the feedback you send us |
| Resend | Sending transactional and support email |
We do not share personal data with anyone else unless the law requires it. We do not sell personal data and we do not share it with advertising networks.
Where your data goes
We are based in Georgia, and the processors above operate in the European Economic Area and the United States, so your data is processed outside your own country. Where data covered by the GDPR leaves the EEA, we rely on the standard contractual clauses in our agreements with those processors, or on an adequacy decision where one applies. You can ask us for details of the safeguards for a particular processor.
How we keep it safe
The website and the Apps are served over HTTPS, access to accounts and administrative tools is restricted to us, and card details never reach our systems — the payment provider handles them. No system is perfectly secure, but if a breach ever affects your personal data we will tell you and the relevant authority as the law requires.
How long we keep it
Chat history sits in your own browser and is purged after 30 days. Translations we have produced are cached on our servers for up to 90 days so that asking for the same one again is instant. MP3 to Text recordings sent for Pro Transcript are deleted as soon as the transcript is back, and their job records within 24 hours. Rate-limiting and security records live only as long as their operational window. Support email: up to 3 years after the last message. Account data: for as long as the account exists, then deleted within 30 days of closure. Invoices and accounting records: as long as tax law requires (usually 7–10 years).
Your rights
You can ask us to give you a copy of your data, correct it, delete it, restrict or object to its processing, or export it in a portable format. Email apps@beartools.dev and we will respond within 30 days. If you are in the EEA or the UK and are unhappy with our answer, you may complain to your local data protection authority.
If you are a California resident, you have equivalent rights to know what personal information we hold, to have it deleted, and not to be treated differently for exercising them. We do not sell or share personal information as those terms are defined by the CCPA. Use the same email address to ask.
Cookies
This website sets no tracking or advertising cookies. Apps that require a login set a strictly necessary session cookie so that you stay signed in. The checkout page may set its own cookies needed to process the payment.
Children
The Apps are not intended for children under 16, and we do not knowingly collect their data.
Changes
If this notice changes materially we will update the date at the top of this page and, where the change affects you directly, tell you by email.