Privacy Policy

Last updated: 26 October 2026

Overview

SnapAway runs locally on your device. The window titles, application names and screen content that SnapAway reads in order to list, hide and restore windows never leave your device. SnapAway needs no account and does not collect names, e-mail addresses, personal files or project content.

What stays on your device

• Your window list, layouts, hotkeys and preferences are stored only in the application's local settings folder.
• A plain-text diagnostic log (iap-telemetry.log) is written to %APPDATA%\SnapAway. You can open or delete it at any time; its content is not uploaded.

Diagnostics we do send

The installed application sends crash and error reports to Sentry (Functional Software, Inc., United States), our error-tracking provider. These reports are what allow us to find and fix failures that we cannot reproduce ourselves: a GPU driver that rejects the overlay, a process that dies on start, a window that fails to restore.

A report can contain:

• the error type, message and stack trace, and the name of the operation that failed (for example app.render-process-gone);
• application version, Windows version and architecture, Electron and Chromium versions;
• technical state relevant to the failure: GPU vendor, device and driver version, which GPU features were disabled, monitor count and display scaling, and whether SnapAway came from the Microsoft Store;
• identifiers randomly generated by the error-tracking SDK, plus the IP address the report arrives from, which the provider receives with any network request and uses for coarse region and abuse protection.

Before a report leaves the device, fields that name a file, folder, URL or user are replaced with [redacted], and any value that looks like a file path is replaced with [redacted_path]. Window titles, the names of the applications you hide, keystrokes and screen content are never part of a report. A memory dump produced by Windows for our own crashed process can, in rare cases, contain fragments of that process's memory; it is used only to diagnose the crash.

When SnapAway uses the network

• Crash and error reports go to Sentry, as described above.
• Update check: SnapAway fetches https://edenware.app/snapaway/update.json to know whether a newer version exists.
• License key: if you activate SnapAway with a key instead of buying through the Store, the key and a device identifier are sent to https://edenware.app/hub. That identifier is a truncated SHA-256 hash of basic machine characteristics (host name, platform, architecture, CPU count, total memory) and not a hardware serial; it exists only to keep the key bound to your devices.
• Microsoft Store: purchases, including SnapAway Pro, are processed by Microsoft under the Microsoft Privacy Statement. SnapAway only receives whether the purchase is active. On Store installs, aggregate events such as "first launch" or "purchase completed" are also logged through the Store Services SDK, under that same statement; they carry the event name only, never content.

This website

edenware.app uses Google Analytics to count visits, and this page loads an assistant widget that answers questions about SnapAway from the text on the page. Neither runs inside the application.

Your choices

Diagnostic reports are always on in the installed application; there is no switch to disable them today. You can delete the local log and settings folder at any time, and uninstalling SnapAway removes them. If you want reports already sent to be deleted, write to contact@edenware.app with the approximate date of the report and we will remove them from the error-tracking project.

Security

Local access to your files depends on operating system permissions. Keep your system updated and review app permissions.

Changes to this policy

If what SnapAway collects changes, this page is updated and the date at the top changes with it.

Contact

For privacy questions: contact@edenware.app