Local transcription does not mean an online page makes no network requests. We inspected the currently published file decoding, worker and export paths. The application reads the selected file into audio and passes it to its browser worker. The worker is configured to load the speech model and runtime from this site. Those program resources are a different data path from the recording. This is a source investigation, not a certification of browser extensions, all dependencies or offline behavior.

We ran the current analytics script in a local controlled JavaScript harness. The document, storage and cookies were synthetic. No external tag was executed and no recording was supplied. The fresh and saved-no controls did not append a tag. The saved-yes control appended one. Turning that choice off set the disable flag but left the already created script element in place. The record keeps both facts. A script count by itself would not tell you the active choice.

Use the footer choice for optional page analytics, rather than as a switch for the speech engine. Model requests and ordinary site delivery remain separate. Our test did not execute the analytics provider code, measure its final network payload or test a disconnected browser. The article provides the exact source hashes, real controlled-run record and a reproducible harness. No accuracy guarantee, private media or third-party footage is used. Original diagrams and locally synthesized narration explain the findings.