The most common question we get is a version of: do my screenshots go to you?
The short answer, quoted straight: No. hypershot has no account system and no hypershot cloud. Your captures are files on your machine; when you share one, it goes through your own operating system’s share options or out as a file you pick. OCR runs on-device. The one time hypershot touches the network is license activation.
What “private” means for a screenshot tool
A screenshot is the most intimate thing you copy off a screen. It might contain a customer’s name, a password field you didn’t mean to frame, a dashboard with someone’s payroll. So the question is never “does the app say it’s private.” The question is: trace the image’s path from your screen to the other person’s hands, and name every machine it touched in between.
In hypershot, that path is short:
- Capture. The frame is recorded on your device. Nothing is transmitted.
- Edit. Annotations, redactions, spotlights — all local. The OCR tool reads text using macOS’s Vision framework or Windows’s OCR APIs; it never ships your pixels to a server to be read.
- Share. You pick a destination from your OS’s share panel — AirDrop, Nearby Sharing, mail, a message, a chat app — or you save a file, or you drag the image into another app. The bytes go from your machine to wherever you point, using your OS’s channels. hypershot does not run a relay, a link service, or a file host.
There is no step four where the image also quietly lands in someone else’s storage.
No account, by design
Most “capture and share” tools solve the sharing problem by turning it into an account problem: sign in, get a URL, and your screenshots live on their servers until they expire (or, in a few notorious cases, until they’re leaked). Every one of those is a machine in the middle that could keep your image after the job is done.
We’d rather you send the actual file. It’s 2026. A PNG travels fine.
The one honest exception
License activation checks in when you activate a key. That’s it — that’s the only thing that reaches out. Nothing about your captures, no telemetry about what you shot, and no “help us improve” folder.
What this buys you
Send a screenshot of a client’s screen to a client without a cloud in the middle. Paste a redacted error into a support ticket without the raw version sitting in a third party’s bucket. OCR a form on a screen your compliance policy says never leaves the office.
Privacy for a capture tool isn’t a feature page. It’s the architecture refusing to add a step.