Wintty privacy notice

Wintty is a terminal. You type passwords, API keys and private code into it, so this page starts with what does not happen.

What we do not collect. The app has no telemetry and no analytics, so there is nothing to opt out of. Nothing in Wintty sends your terminal content, keystrokes, scrollback, files or configuration anywhere. What the app does have is local crash capture: when it crashes, it writes a crash report on your own machine, and it reaches us only if you choose to send it. The Support dumps section below says exactly what is in one. The website runs no analytics and loads no third-party scripts. We never see your card details, and we do not sell or share data with anyone.

What we hold to run the paid service. Sign-in is how we know who bought what. If you sign in with GitHub, we hold your GitHub numeric id and username, your sponsorship status and tier, the edition and channel you are entitled to, and a sign-in token that expires by itself after 30 days. The token stays on your machine, encrypted with Windows' own protection tied to your user account. If you link Discord for the sponsor role, we hold your Discord id and username next to your GitHub id. If you buy outside GitHub, we record your handle and a payment reference so the thing you paid for keeps working. Everything else we hold is logs, described next.

Logs and retention. Our server records each sign-in, download and update check: time, edition, outcome, a shortened IP address, your network operator and country. This is what lets us serve the right download and notice when one licence is being shared by many people. Detailed records are deleted after 180 days by a job that runs every 12 hours. IP addresses are shortened for everyone: IPv4 to the first three octets, IPv6 to the first /48. For an account we flag for licence sharing we keep the full IP address while the flag stands and for 90 days after the case closes, then it goes too. We keep no per-account totals beyond that.

Support dumps. You can send a diagnostic dump when you ask for help. You see everything in it before it is sent, and you can edit or delete anything in it first. It is meant to hold version, GPU and settings information, not personal data, and support works without it. Crash reports are separate: the app writes one by itself after a crash, either immediately or on its next launch, depending on the kind of crash, as a .winttycrash file under %LOCALAPPDATA%\wintty\crash in your own user profile. A report holds a stack trace, the list of loaded modules, a tag recording which kind of thread crashed, the engine version and a few build tags. File paths in it are cut down to a placeholder and the file name, so the username is not meant to be in it. The crash code also keeps a working folder, %LOCALAPPDATA%\wintty\sentry, that it fills as it runs and empties on its next launch. Nothing is transmitted anywhere: the crash code has no server address and no network code. Nothing prunes the files either, so deleting them is safe and is yours to do. Whether we ever see one is your decision, made when you attach it to a support request.

Contact. Questions, data requests, or objections: support@ship.digital. The paid tiers EULA, including the legal bases for this processing, is served at https://api.wintty.io/legal/eula. The site's terms of use and refund policy say what buying here means and how to get your money back.