This policy describes a request to open-source-gif-maker.pages.dev. It describes what that hostname logs. It skips describing ScreenToGif running on your PC. Once you install from GitHub or winget, capture and export 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 first-party tracker is named |
| Ads | Off. No ad network script, so no ad cookies from these notes |
| Hosting | Cloudflare Pages may keep ordinary request logs |
| Installer files | Stay on GitHub Releases and winget |
| Recordings | Local files on your Windows user profile after you run the program |
No personal accounts
There is no signup, no newsletter form, and no comment box that stores a name. Gif files are not uploaded here. Screen, webcam, and sketchboard takes live on the PC after you run the program. The README names no cloud account. Notes never ask for a Nicke Manarin login because the program does not require one.
The Windows setup MSI and the portable zip are fetched from GitHub Releases. Winget talks to Windows Package Manager with id NickeManarin.ScreenToGif. Microsoft and GitHub have their own privacy statements for those hops. The command notes quote is:
winget install -e --id NickeManarin.ScreenToGifHosting logs
Pages ship on Cloudflare Pages. 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. Gif Maker 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. There is no measurement product to name and no cookie banner for a tracker that is not present. Ads are off. No display network script ships, so these notes 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 a gif maker safely and on home.
Third-party links
Notes link out. GitHub holds the repo, releases, LICENSE.txt, wiki, and Issues. Microsoft holds App Installer and the .NET 9 Desktop Runtime the README requires. The project homepage listed in winget-pkgs is www.screentogif.com. Compare notes link ezgif.com, ShareX, and LICEcap when a fact is quoted from those pages. Each of those destinations applies its own policy once you leave. Related notes: gif maker GitHub, gif maker install, gif maker releases.
The program on your PC
ScreenToGif is a local Windows program. Capture stays on the machine you control. Telemetry is not claimed in the README, and notes skip inventing a tracker for the app. Uninstall from Windows Settings, Apps, then delete project folders in your user profile only if you want a clean slate after a portable zip. First-run and requirements sit on gif maker for this computer. Webcam jobs sit with the rest of gif maker guides. Moving off a browser encoder is a local-files problem, walked in move off web encoders.
MS-PL source stays on GitHub. Building from source is optional. Most readers want winget or the x64 setup MSI. 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 ScreenToGif, injected at build, because the product and the publisher are separate.