Creator ruling 2026-11-09: finish the queue before the new features, gold pass always last. **Retired (platform's surface, not ours):** - 34 scheduled streams — YouTube owns scheduling *and* the reminder that makes it worth anything. - 50 publish recording — Studio owns upload (resumable, quota-aware, explains rejections), and an in-app uploader would widen the OAuth consent to whole-channel video management for one convenience. The app adds "Show in folder" instead. **New tasks:** 65 replay clips (the creator-side buffer YouTube does not give you), 66 timed ticker messages, 67 per-event alert videos, 68 edit-while-live + first-run On-Air. **TASK 65 spec** is the interesting one: 15 s is a clip (10/15/20, default 15); the ring holds encrypted *encoded* fragments in RAM — raw 1080p frames would be ~7.4 GB for 15 s — so there is no steady disk write and no crash debris; F10 saves; the replay layer plays once then hides in Live and loops the last 1–3 elsewhere; silent by default; three kept; the layer is excluded from its own clip (hall of mirrors). **TASK 14 gains Branch 3:** mic input gain ahead of the gate (table boom mics fall under it), webcam blank hotkey, opacity/geometry parity with a collapsed Geometry disclosure, Show-in-folder. **Decisions recorded:** the replay-buffer reversal (it was retired in 2022-era reasoning as "different product"; the case for it won), the platform-surface rule, and voice triggering deferred — always- listening in a streaming app hears the game, so the content is its own false-positive source. Queue refactored to 56 lines by archiving completed rows and the superseded surge plan; HANDOFF at 40.
2.4 KiB
Privacy Policy — LlamaCasty
Last updated: 30 October 2026
LlamaCasty is a desktop application for streaming to YouTube. It runs entirely on your computer. This page states exactly what leaves your machine, what is kept locally, and what is never collected.
What is stored on your computer
| Data | Where | Why |
|---|---|---|
| Your layout: scenes, sources, assets, settings | %APPDATA%\ytLlive\ytLlive.db |
So the app looks the same next time |
| YouTube sign-in token | %APPDATA%\ytLlive\ytLlive.auth, encrypted with Windows DPAPI (CurrentUser) |
So you stay signed in; only your Windows account can decrypt it |
| Diagnostic log | %APPDATA%\ytLlive\startup.log, capped at 5 MB |
To diagnose crashes you report |
| Recordings | the folder you choose | Your files; the app never uploads them |
| Replay clips (if you use them) | clips\ beside your recordings |
Only the three most recent are kept; older ones are deleted automatically. Local only, never uploaded |
Nothing else is written to disk. There is no analytics service, no crash reporter, no advertising SDK and no telemetry of any kind.
What is sent, and to whom
Google / YouTube — only when you sign in and go live, using your own account:
- your channel information, live broadcasts, streams and chat, to run the stream and show the chat overlay;
- your watch-time and subscriber statistics, to draw the YPP progress and scoreboard tiles;
- your recording, only if you press Publish.
Nowhere else. The app talks to googleapis.com and the YouTube ingest
servers. It does not contact the publisher's servers, and no content of yours
is stored on them.
What is never done
- Chat is rendered, never stored. Live chat is drawn on your stream and held in memory; it is not written to disk, not uploaded, and not analysed.
- No viewer, member or donor information is retained after the session ends.
- No microphone, camera or screen content is transmitted anywhere except the YouTube stream you start yourself.
Your controls
Deleting %APPDATA%\ytLlive removes every local trace: layout, assets, logs
and the saved sign-in. Signing out inside the app deletes the saved token.
Children
The app requires a YouTube account, and YouTube requires users to be 13 or older. The app is not directed at children and collects nothing from anyone.
Changes and contact
Material changes will be dated in this file. Questions: llamachile.shop@gmail.com · https://llamacasty.com