Last changed 2026-09-16. This page describes what the app will do at its first release; it is written before the code so the code can be held to it.
opsty makes one kind of request on its own: an HTTPS GET of the release feed at https://dl.opsty.dev/releases/latest-<os>.yml, on launch and once an hour. It carries no version, no identifier and no machine information. The server does not log it. A switch in settings turns it off, and the first run asks before it is ever made.
Electron's crash reporter is inactive unless an application starts it. opsty never starts it with uploads enabled. Crash files stay on your machine and you decide whether to attach one to an issue.
Chromium downloads spell-check dictionaries from a Google CDN by default. opsty disables that. A network trace runs in CI and fails the build if any host other than the release feed is contacted.
Shell integration sends prompt marks and the working directory to the terminal on your own machine. Command history and blocks are stored in a local SQLite file, with credentials scrubbed before writing, and you can delete it. Hosts come from your own ~/.ssh/config; opsty does not keep a second copy in a cloud.
Nothing is installed on a remote host unless you ask for it per host, and hosts tagged production refuse it entirely.
There is no sign-in. There is no analytics script on this website. Server access logs for the release feed are discarded at the web server, not rotated later.
계정도, 수집도 없습니다. 앱이 스스로 보내는 요청은 업데이트 확인 하나뿐이며, 식별자를 담지 않고 기록되지 않으며 설정에서 끌 수 있습니다.