What we keep, what we delete.

Uploads go directly to a private Google Cloud Storage bucket in australia-southeast1. Files are never public and never listed — every status, download, cancel, and delete requires the same anonymous session (or account) that created the job.

Inputs are deleted as soon as processing succeeds. Results stop being downloadable about 90 minutes after completion, and storage lifecycle rules remove the bytes after that. Use “Delete now” any time to remove a job and its files immediately — that path runs straight away rather than waiting.

Being precise about timing: the 90-minute mark is when we stop serving a result, not a guaranteed deletion moment. A scheduled cleanup job that deletes on a fixed timer is not running yet, so an abandoned upload can sit in private storage until the storage lifecycle rule removes it. Treat the 90-minute window as “download it now”.

We log job metadata (tool, sizes, durations, errors) to measure cost per successful job — never file contents.

Your email address. To open a transcript you make from the link box, you give your email and we send a sign-in link and a code. We keep the address on your account, with when you first and last signed in and whether you asked for product news. We send emails about your account and your transcripts (sign-in links, results, receipts) because they are part of the service. We send product news and offers only if you tick that box or say yes when we ask; signing up alone never means yes. Every such email has a one-click unsubscribe link and our postal address, and you can ask us to delete the address at any time on the feedback page. We do not sell or share it. Transcripts made from links are public pages and do not show who asked for them.

Who asked for a public transcript. When you are signed in and make a transcript from a link, we record that your account asked for it. We never show this on the page. We use it only to reach you if the page has to come down, for example under our content policy or after a copyright claim.

Payments. If you buy Pro or credits, Stripe takes the payment. We never see or store your card number. We keep your Stripe customer id, your plan's state, and which credits each payment bought, so a refund can take them back. To allow one free trial per person, we keep the card's fingerprint (an id Stripe gives us, not the number) and, if you sign in with Google, your Google account id. Stripe keeps your billing details under its own privacy policy.

The Blumify Chrome extension. When you click the Blumify icon on a YouTube, Apple Podcasts or Spotify page, the extension sends that page's address to blumify.io to show or make its transcript. It does not read anything else on the page, does not see other tabs, and never downloads video or audio. If you sign in, the extension uses the same Blumify account and sign-in as the website.

Claude and other connected apps. When you connect Claude or another app to your Blumify account, through our MCP server or an API token, the app sends us only what each request needs: a link, a question, a language, a creator's name, or the id of a job or playlist. We never see the rest of your conversation with the app. We keep the app's name, when you connected it and when it last worked, and the transcripts it makes are saved in your workspace like any other. We do not keep your questions: to answer one, we send it with the transcript to OpenRouter, the service that runs the AI models for our summaries and answers. You can disconnect an app or revoke a token at any time under Connected apps in your workspace, and it stops working at once.

Google Analytics. Our website uses Google Analytics to count visits and to see which pages and features people use. It sets first-party cookies (named _ga) and sends Google the page you visit, where you came from (for example a search engine, or a link we tagged), your type of device and browser, and an approximate location worked out from your IP address. Google Analytics does not store IP addresses. We also send it events such as “started a transcript”, “shared a page” or “started checkout”, with the kind of link, tool or plan, but never your email address, your files or your questions. Google keeps the detailed event data for 2 months and user-level data for 14 months. Google signals is off, so this data is not linked to your Google account. Advertising cookies are off: Google Ads gets only cookieless measurement pings, and nothing is used for personalised ads. You can block these cookies in your browser or with Google's opt-out add-on. Google Analytics runs only on the website: the Chrome extension, Claude and other connected apps do not use it.

Anonymous session ids are abuse controls, not reliable personal identity. One job runs at a time per session; a per-day cap is planned but not enforced yet. Do not upload anything illegal or anything you do not have the right to process.