Local configuration. No behavioral telemetry.

Policy status

This page documents behavior visible in the current source and repository security policy. The project's formal privacy notice tracked in GitHub issue #86 is not yet approved. Review this page again before relying on a future release, because implementation behavior may change.

Current information version: 0.1. Effective date: 28 July 2026.

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 terms and data handling. The project has not yet published a separate private support-data controller contact or retention schedule. For security-sensitive material, follow the security reporting route and request a private communication channel before sending details.

Project contact

The publicly identified publisher is KeyffMS / aiteracja.pl. General project contact currently routes through the GitHub repository owner. Do not send personal or confidential data before a private route and its handling terms are agreed.