the guides ship as static HTML. This policy describes what hosting may log when those files are served. It skips describing the OBS Project desktop app running on your PC. Once you install from GitHub or winget, scenes, recordings, and streams are the program's, on hardware you control. Publisher: about.
| Item | Status |
|---|---|
| Personal accounts | None. No member database, newsletter, or comment store |
| Analytics | None. No analytics token is set. No first-party tracker is named |
| Ads | Off. Ad IDs stay empty. No ad network script, so no ad cookies from the guides |
| Hosting | Cloudflare Pages may keep ordinary request logs |
| Installer files | Stay on GitHub Releases and winget |
| Local scenes | Stay on the reader's Windows PC. The desktop app is the product. the guides are static HTML |
No personal accounts
There is no signup, no newsletter form, and no comment box that stores a name. Recordings are not uploaded here. Scenes, local files, and stream credentials live on the PC after you run the program. The README names no OBS Project account for local record. Notes never ask for a project login because a local recording does not require one. A stream uses the login of the platform you send it to.
The Windows x64 installer and the portable zip are fetched from GitHub Releases. Winget talks to Windows Package Manager with id OBSProject.OBSStudio. Microsoft and GitHub have their own privacy statements for those hops. The command notes quote is:
winget install -e --id OBSProject.OBSStudioHosting logs
Notes ship on Cloudflare Pages as static HTML. Cloudflare may keep standard web logs: IP address, user agent, referrer, path, and time. Those logs belong to Cloudflare, used to serve the files and to handle abuse. OBS Studio editorial team runs no separate visitor database on top of that. If a log retention question is really a Cloudflare question, ask Cloudflare. If a sentence on a note is wrong, use the four-fact path on contact.
Analytics and ads
Analytics are none. No analytics token is set. There is no measurement product to name and no cookie banner for a tracker that is not present. Ads are off. Ad IDs stay empty. No display network script ships, so the guides set no advertising cookies. If a network is approved later, the advertising disclosure will name it before a script ships, and this policy will be updated in the same change. Until that happens, treat analytics as none and ads as off.
There is no fake download button that is actually an ad. The file link goes to GitHub Releases. The install command is the winget id from winget-pkgs. Both are described on download safely and on home.
Third-party links
Notes link out. GitHub holds the repo, releases, COPYING, and Issues. Microsoft holds App Installer. The project homepage listed on the repo is obsproject.com. Compare notes link Streamlabs Desktop, XSplit Broadcaster, Xbox Game Bar, and NVIDIA App when a fact is quoted from those pages. Each of those destinations applies its own policy once you leave. Related notes: GitHub, how to install winget, releases.
The program on your PC
The OBS Project desktop app is a local Windows program. Local scenes stay on the reader's PC. Telemetry is not claimed in the README, and notes skip inventing a tracker for the app. Uninstall from Windows Settings, Apps, then delete portable folders only if you used the zip. First-run habits sit on for this computer. Longer jobs sit with the rest of guides.
GPL-2.0 source stays on GitHub. Building from source is optional. Most readers want winget or the x64 installer. How a fact is checked: editorial policy.
When this policy changes
If analytics, ads, or a public email appear later, this policy will name them before the change ships. The stamp date moves when a person re-reads the policy against that setup. The current release tag on the stamp is still the GitHub tag for the desktop app, because the product and the publisher are separate.