Skip to content
English
Add to Chrome
Privacy

What we see, what we keep, what we share.

The honest version. Updated 2026-05-07.

First, what's a Glance?

A Glance is what we call a single use of baki.sh on a video: you open a YouTube page, baki.sh fetches the transcript, our backend summarizes it through an LLM, and the reading panel slides in next to the player. One Glance per video, per fresh summary. Everything below describes what happens, and what we keep, when you do that.

What we see, what we keep, what we share

When you Glance a video: the video ID and the transcript reach our servers and our LLM provider. We cache results keyed to the video, so the same video Glanced again = no LLM cost. We log that you Glanced this video (user ID, cost, model) for 13 months, then purge. We store a salted hash of your IP, country, and network operator (ASN) for abuse detection. Salts rotate yearly. We never store your raw IP. We do not log videos you watched without summarizing.

What we publish

Quarterly transparency report (totals, retention, government/legal requests, warrant canary). Weekly open cost ledger (LLM spend, Stripe revenue, gross margin). Auto-published postmortems within 24h for any outage > 30 min.

Your controls

Self-service delete and export from your account. See who looked at your data: every admin read of your account is logged with a reason and visible to you. Cancel from the extension popup, no retention page.

Anti-abuse

baki.sh deploys rate-limiting, captcha challenges, and degraded service for traffic matching automated-scraping patterns. Specific triggers are not disclosed; trigger rules live as code in our backend with public commit history; aggregate counts published quarterly. If caught by mistake, email [email protected]. Human review within 48h. Degraded service = stale/cached responses. We don't lie to scrapers; we just stop trying for them.

Anonymous aggregate

Once a week the extension sends a single number to our backend: how many megabytes of video bandwidth you saved that week. The number is keyed to a random UUID generated when you installed the extension; it has no link to any account, email, IP, or video. We use the totals to publish "baki has saved X TB across all users" on /transparency. We delete the rows after 90 days. You can turn this off in the extension popup; the local counter still works.

Latency telemetry

When you Glance a video we record how long each step took (transcript fetch, model response, render). The numbers are tied to your account so we can spot if a particular user is having a bad time, but they're aggregated for the public /transparency SLO page. Default off for Free, on for Pro. You can toggle this in the extension popup. We delete the rows after 90 days.

Featured videos on the homepage

The "Try it!" block on baki.sh shows real videos that real baki users have actually Glanced. When a Glance lands on a video with broad popularity (variable threshold based on traffic) and a non-divisive topic per the LLM-inferred meta, we save the public YouTube ID, title, channel name, and view count to a small table called featured_demo_videos. The homepage reads the top rows from there. We never store who Glanced it, when in their session, or any per-user signal: only the video and how many distinct Glances it has accumulated. A video appearing on the homepage means "at least one baki user has looked at this", not "user X looked at this". If you'd rather your Glances never be eligible for that surfacing, email [email protected] and we'll add a "skip-featured" flag to your account.

What we don't promise

We're not zero-knowledge. We see your transcripts. We see your prompts. We have to. What we do promise is exactly what we have, why, for how long, and who's looked at it.

Last updated 2026-05-10