Privacy Policy

Who this applies to

This policy covers the Konstruct marketing website at konstruct.dev (including the download and store pages) and the Konstruct desktop application.

This website

Page analytics

Our public pages load PostHog analytics (via s.konstruct.dev) to understand how visitors use the site — for example page views, navigation, and clicks on store links. This is standard marketing-site analytics, not tied to your Konstruct app usage or your repositories.

We do not use advertising trackers or sell visitor data.

Web server logs

When you visit konstruct.dev or download files from our site, the web server may record standard access logs — for example your IP address, browser type, and the time of the request. Those logs are used for delivery and security, not for profiling.

Download accounts

The download page may require a free account (email and password) before installer links are shown. Account sign-up and authentication are handled by Supabase on our behalf. We use that email to gate downloads and send confirmation messages — not to market unrelated products.

Purchasing a Pro license through our store is handled by our payment provider; that flow is separate from the download sign-up. Questions about orders, billing, or refunds belong with sales — see Contact below.

The Konstruct desktop application

Konstruct is designed to run locally. We do not receive your source code, chat history, or project files unless you explicitly connect the app to a third-party service you configure (such as an LLM provider).

Data stored on your device

The app stores data locally on your computer, including:

• Project and global configuration
• Chat sessions and conversation history
• Code search indexes and dependency-graph data derived from your repositories
• License data you enter (license.txt, purchaser email, or hosted activation details)

This data remains on your machine unless you back it up or share it yourself.

Optional telemetry (opt-in only)

On first launch, Konstruct asks whether you want to share optional telemetry. Nothing is sent unless you turn it on. If you opt in, events are sent to PostHog through our s.konstruct.dev proxy using an anonymous installation ID — not your name, email, or license key.

You can choose two levels independently:

• Essential reports — app version, operating system, and anonymous crash or error stack traces. No source code, prompts, or file paths.
• Product analytics — anonymous feature usage (for example screens visited or agent runs started), LLM provider category and model name (not API keys or message text), and token counts for agent runs. No repository names, file paths, or chat content.

You can change or disable these preferences anytime in the app settings.

Licensing

Konstruct supports two ways to unlock Pro features:

• Signed license file — If you use an offline license.txt file, validation happens entirely on your device. The app verifies a cryptographically signed license against an embedded public key. No network request is made to Konstruct.
• UUID license key (hosted activation) — If you activate with a UUID-format license key, the app contacts our license service to register this installation and to periodically re-validate that the key remains active (results are cached locally for about 24 hours). For subscription licenses, the app may also call Konstruct’s API at konstruct.dev to check renewal status. Billing-provider details are handled on our side — the app does not talk to payment processors directly for routine checks.

On the hosted-license path, we transmit licensing-related data only — your license key, installation instance identifier, purchaser email for verification, and subscription lookup parameters — not your source code, chat history, or project files.

If you do not activate a license, no license-related data is sent to Konstruct.

Connections you configure

Konstruct connects to external services only when you set them up. Depending on your configuration, the app may send data to:

• LLM providers (for example OpenAI, Anthropic, Google Gemini, AWS Bedrock, Ollama, RunPod, or others you configure) — prompts, code context, and related content you include in a session are transmitted to the provider you selected.
• Git and GitHub — when you use Git or GitHub integration, requests go to those services under your credentials.
• Other integrations — such as JIRA or web search, when enabled and invoked by you or the agent.

Those services have their own privacy policies. Konstruct does not control how third parties handle data you send them.

What we do not collect from the app (unless you opt in to telemetry above)

• No usage analytics or product telemetry sent to Konstruct by default
• No crash or error reports sent to Konstruct by default
• No automatic upload of your source code, chat logs, or project files to Konstruct servers
• No device fingerprinting beyond licensing instance identifiers when you activate a hosted license

Children

Konstruct is a developer tool and is not directed at children under 13. We do not knowingly collect personal information from children.

Changes to this policy

We may update this page if our practices change. The “Last updated” date at the top will reflect the most recent revision. Material changes to how we handle data will be described here.

Contact

Questions about this policy can be directed to privacy@konstruct.dev.

For other topics: general inquiries at info@konstruct.dev; sales, licensing, and billing at sales@konstruct.dev.