StreamView privacy policy
Last updated: 1 September 2026
StreamView is a Windows desktop application published by LTC Labs. This policy covers what the application does with your data. The short version: your terminal sessions never leave your computer.
What StreamView stores on your computer
StreamView is local-first. Everything it records stays in folders on your machine under your control:
| Data | Where it lives | Why |
|---|---|---|
| Session history | {data directory}\history\ | Search and export past sessions |
| Settings and stream templates | {data directory}\settings.json, custom-profiles.json | Preferences and saved terminals. Environment variables are encrypted for this Windows user (DPAPI). |
| Screenshots you paste | {data directory}\screenshots\ | So a terminal application can read the image by path |
| Session state and logs | %LOCALAPPDATA%\StreamView\ | Restoring your layout, and diagnosing problems |
| Speech models (if you enable voice input) | %LOCALAPPDATA%\StreamView\whisper-models\ | Transcribing dictation on your machine |
Session history can be pointed at its own folder, separately from everything else, under Settings → Data → History Location.
The data directory defaults to %APPDATA%\LTCLabs\StreamView and can be changed in Settings → Data.
If you point it at a synced folder such as OneDrive or Dropbox, that provider's own terms apply to the copy it syncs. StreamView has no cloud service of its own and never uploads this data anywhere.
Environment-variable values in those files are DPAPI ciphertext bound to this Windows user, so a synced copy is not plaintext, and is not readable on another PC.
You can delete any of it at any time. Deleting the folder is enough; nothing is retained elsewhere.
Microphone
StreamView does not use your microphone unless you turn on voice input in Settings → Data → Voice Input, which is off by default.
When it is on, the microphone is opened only while you hold the microphone button or the dictation hotkey, and closes when you release it (with a two-minute hard limit on any single recording). The audio is transcribed on your computer, by a speech model stored on your computer, and is held in memory only long enough to do that. It is never written to disk and never uploaded anywhere. There is no speech service, no API key, and no network request involved in transcription. The only network access the feature makes is the one-time download of the speech model itself, from Hugging Face.
Dictated text is typed into the terminal exactly as if you had typed it, so it is covered by that stream's recording mode like any other input.
What StreamView sends to LTC Labs
Four things, all listed here in full and all optional except the first:
- A startup request to
https://www.ltclabs.dev/api/app/update-check, once per launch. This is how the application learns whether a newer version exists and retrieves a support token. It carries a hashed machine identifier (below). - Two anonymous usage events per session:
app_launchedandapp_closed. The closing event carries a summary of counts, settings values, and feature-used flags: how long the app ran, how many panes were open, which layout and theme you use, and similar. Numbers, enumerations, and true/false only. Off switch: Settings → Data → Privacy → Send anonymous usage data. - Crash reports, only if the application crashes: exception type, message, and stack trace. Off switch: Settings → Data → Privacy → Send crash reports.
- Support tickets, only when you press Help → Contact Support: what you typed, the email address you supply, and the recent application log. You see the contents before it is sent.
Every field of the usage payload is documented, item by item, in Telemetry.
What is never sent
Not in any request, not in crash reports, not in update checks:
- Terminal output, scrollback, or session history
- Commands you run, environment variables, working directories, or file paths
- Workspace names, stream names, or template names
- Screenshots, keystrokes, or window contents
- Microphone audio, or anything transcribed from it
- Your name, email address, or account details, except in a support ticket you choose to submit
How "anonymous" works
StreamView identifies a machine by a SHA-256 hash of the Windows MachineGuid value. The original value never leaves your computer, and the hash cannot be reversed to identify you or your machine. It exists so that distinct installations can be counted. There is no user account and no sign-in anywhere in StreamView.
Children
StreamView is a developer tool with no content directed at children and no social, messaging, or user-generated-content features. It does not knowingly collect information from anyone, of any age, beyond what is listed above.
Third parties
StreamView contains no advertising, no analytics SDKs, and no third-party trackers. The only network destination is ltclabs.dev. Data is not sold, rented, or shared with anyone.
Terminal panes run programs you choose: shells, and tools such as AI coding assistants. Those programs have their own network behaviour and their own privacy policies; StreamView neither controls nor inspects what they send. Running a tool inside StreamView is the same, privacy-wise, as running it in any other terminal.
Your choices
- Turn off usage data and crash reports independently in Settings → Data → Privacy
- Turn off update checks in Settings → General → Updates
- Turn off session recording entirely, or per stream, in Settings → History and the stream editor's recording mode
- Leave voice input off, or turn it off again, in Settings → Data → Voice Input. With it off the microphone is never opened, and you can delete the downloaded speech models from the same place
- Delete your history and settings folders at any time
With every toggle off, the only remaining request is the single startup call described above.
Retention
Anonymous usage and crash data are retained for up to 24 months for product analysis. Support tickets are kept until the request is resolved and for a reasonable period afterwards for follow-up.
Contact
Questions about this policy, or requests concerning data associated with your machine identifier or a support ticket:
- In-app: Help → Contact Support
- Email: [email protected]
- Web: ltclabs.dev
Changes
Material changes to this policy will be noted in the product updates and reflected in the date at the top of this page.
Related: Telemetry field-by-field · StreamView documentation · LTC Labs site privacy