Security
Security
Hindsight holds video of your screen in memory, so it is reasonable to want to know what it can reach. The short answer is: your clips folder, and nothing else.
Reporting something
Mail help@hindsightclips.com with enough detail to reproduce the issue. You will get a human reply, normally within a few days. There is no bug bounty programme and no reward budget — saying so plainly is fairer than leaving it implied. Please give us a reasonable window to ship a fix before publishing.
What the app touches
- The replay buffer stays in RAM. Frames are hardware encoded as they arrive and discarded as they age out. Nothing is written to disk until you press the shortcut.
- Clips are written only to the folder you chose, which defaults to ~/Movies/Clips.
- The Mac App Store build makes no network requests at all. Apple handles the purchase and the updates.
- The direct download build makes two. It validates your licence key with Lemon Squeezy, and it checks an update feed on this domain. Neither carries anything about what you have recorded.
- There is no account, no telemetry that identifies you, and no analytics inside the app.
The screen recording permission
macOS will not let any app see the contents of a window without the Screen & System Audio Recording permission, granted by you in System Settings and revocable there at any time. Hindsight uses Apple's ScreenCaptureKit rather than any private interface, so it is subject to exactly that gate. Revoking the permission stops capture immediately.
Distribution
Both builds are signed with an Apple Developer ID and notarised by Apple before release. The direct build updates through Sparkle over HTTPS, and updates are signed with an EdDSA key, so an update that has been tampered with is refused rather than installed.