How Friskription handles data when it turns tab audio into live translated subtitles.
Last updated: August 26, 2026Developer: OsakaMcFriskChrome extension
Single purpose
Friskription’s only purpose is to capture audio from a browser tab you choose,
transcribe that audio, translate the transcript, and show the result as an on-page
subtitle overlay.
What data is handled
Stored on your device
API keys you enter (ElevenLabs, OpenAI, and/or Anthropic)
A small record of how often you have used the app (sessions stopped, files opened in the media studio) and whether the review prompt has been shown — used only to decide when to ask you for a store review, and never sent anywhere
These stay in your Chrome profile via extension storage. When you use your own API
keys, Friskription does not run user accounts or a backend for your settings. The
optional Instant mode below is the only feature that uses an account.
Instant mode and Premium (optional, sign-in based)
If you choose Instant mode instead of providing your own API keys,
Friskription operates a small backend (hosted on Supabase) so you can start without
any provider accounts. In that mode we process and store:
Your Google account email and a user ID (from Google sign-in) — identifies your account, and lets us give the free weekly minutes out once per person rather than once per new account
Your minute balance (the free weekly allowance and any minutes you have bought) and usage records — used for metering and rate limiting. The free allowance is topped back up automatically once a week, which reads and writes only this balance
Payment records for purchases (the payment processor's transaction ID, amount, minutes credited, which pack was bought) — card and account details are handled by the payment processor and never reach our backend. Your account tier (Trial, or Premium once you have bought anything at all) is derived from these records and is what unlocks Premium features such as the sync presets
The tab audio you translate plus its transcripts/translations — these pass through our server to our AI providers (speech-to-text via ElevenLabs or OpenAI, translation via Anthropic Claude or OpenAI) transiently and are not written to a database
Instant mode is entirely optional. Bring-your-own-key pipelines keep working with no
account and no Friskription server involved — with one exception: the Premium features
(Live Sync, Balanced Sync, Full sync) require signing in with Google even on your own
keys, because your Premium entitlement is verified against your account on our backend.
Only the sign-in and account/tier checks above happen in that case; your audio and
transcripts still go directly from your browser to your own providers.
Processed to provide the feature
Tab audio from the page you start capture on
Temporary speech transcripts generated from that audio
Translated subtitle text shown in the overlay
Basic tab info needed to keep the session attached to the right page
Optional support link
The extension may link to Ko-fi for tips. Clicking that opens Ko-fi in your browser.
Friskription does not collect payment card details.
The Friskription website also carries a Ko-fi support button. Unlike the
link above, it loads a script from Ko-fi on every visit, so Ko-fi receives your IP address
and may set its own cookies under
Ko-fi's privacy policy,
whether or not you click it. We do not use it for analytics and it is told nothing about
what you watch or translate. The extension itself does not load it.
Third-party services (your API keys)
Friskription is built around bring-your-own-key. Depending on your
pipeline, audio and/or text may be sent from your browser to:
ElevenLabs — speech-to-text
OpenAI — Whisper speech-to-text, and optionally GPT translation
Anthropic Claude — translation (Claude pipelines)
Only the services you configured
Those providers process data under their own policies. With your own keys,
Friskription does not keep a copy of your audio or transcripts on a Friskription
server.
In Instant mode, these services are involved instead:
Supabase — hosts our backend: sign-in, minute balances, usage metering, and the audio proxy
Anthropic — translation via Claude, called by our server with our key
ElevenLabs / OpenAI — speech-to-text (and OpenAI as translation fallback), called by our server with our key
PayPal — payment processing when you buy minutes; your payment details go to PayPal, not to us
Stripe — alternative payment processor, where used; card details go to Stripe, not to us
Google — sign-in (OAuth); we receive your email address, never your password
What we do not do
Sell your data
Use your data for advertising profiles
Use your data for creditworthiness or lending
Collect data unrelated to live translated subtitles
Require a Friskription account
Permissions (why they exist)
tabCapture / activeTab / tabs — capture and identify the tab you asked to translate
offscreen — process captured audio outside the page
scripting — inject and update the subtitle overlay only on the site you start (after you allow access)
storage — save keys and settings on your device
identity — open the Google sign-in window for Instant mode (used only if you pick Instant mode)
Host permissions for
api.openai.com, api.anthropic.com, and
api.elevenlabs.io — send transcription/translation requests only to those APIs
Host permission for our Supabase backend — Instant mode sign-in,
balance checks, and audio processing requests
Optional site access — when you click Start, Chrome asks for access to
that site’s origin only so the overlay can appear. Friskription does not request
access to all websites at install time.
Friskription does not execute remotely hosted JavaScript as part of the extension.
Network requests are API calls for speech-to-text and translation.
Data retention
Local settings remain until you clear them, uninstall, or clear extension storage
Audio/transcripts are processed to generate subtitles and are not stored on a Friskription server (Instant mode passes them through our server transiently, without writing them to a database)
Instant mode account records (email, minute balance, usage events, payments) are kept while your account exists; contact us to request deletion
Third-party APIs may retain data under their own policies and your account settings with them
Children’s privacy
Friskription is not directed at children under 13, and we do not knowingly collect
personal information from children.
Changes & contact
If this policy changes in a meaningful way, the “Last updated” date will be revised and
the updated policy will be posted at this URL.
For privacy questions, contact the developer through the Chrome Web Store listing contact
email for Friskription, or via the project repository maintained by OsakaMcFrisk /
McFrisk-beep.