Local configuration. No behavioral telemetry.

Policy status

The repository privacy notice is approved and is included with the current official binary release. This page summarizes that notice for the product website and must remain synchronized with the authoritative repository copy.

Repository privacy notice last updated: 29 July 2026. Read the complete current PRIVACY.md.

Data read by the application

To identify a selected application and manage its overlay, SightAdapt reads limited Windows window and process metadata. This can include executable names, executable paths, window identity and file metadata. It also reads display geometry and scaling information required to position the overlay.

A Windows path can contain a username, organization name or other identifying text.

Data stored locally

Saved visual profiles, application assignments, enable or disable state, overlay scope, executable identity and related settings are stored in a local, schema-versioned JSON file:

%LOCALAPPDATA%\SightAdapt\settings.json

The current project documentation does not describe cloud synchronization of this file.

Network, telemetry and screen content

• The current alpha does not transmit or save captured screen content.
• No behavioral analytics or telemetry is documented.
• No automatic crash-report upload is documented.
• No automatic diagnostic upload is documented.
• This website uses no cookies, analytics, external fonts, advertising or third-party embeds.

Any future telemetry, upload, update-check or crash-reporting feature requires a separate privacy review before these statements can remain valid.

Inspect, copy or delete settings

Exit SightAdapt before editing its settings. You can inspect or copy settings.json with a local text editor. To delete saved profiles and application assignments, exit the application and delete the file. This action removes your local configuration and is not automatically reversible.

Support data and redaction

Information voluntarily submitted in a GitHub issue, screenshot, log or message is no longer confined to the local application. Before submission:

• remove usernames, organization names and private directory paths;
• crop or redact confidential application content;
• remove credentials, access tokens and account identifiers;
• share the smallest reproduction necessary.

Public GitHub issues are public and subject to GitHub's platform controls and repository history. Privately submitted support material is limited to the people needed to investigate the report, is used only for support, security investigation, compliance evidence or resolving the reported problem, and is normally deleted no later than 90 days after the related support matter is closed. A longer period may apply for an active security investigation, legal obligation, dispute or explicitly agreed follow-up.

For security-sensitive or personal information, follow the security reporting route and request a private communication channel before sending details.

Controller and project contact

When support material is received directly by the project publisher, the responsible controller is KeyffMS / aiteracja.pl. General project contact routes through the GitHub repository owner and issue tracker. For non-public material, request a private communication channel before sending data.

GitHub and any other service used to submit information operate under their own terms and privacy notices.