Privacy Policy

Who this policy covers

FDO (FlexDevOps) is an open-source project maintained by Oleksandr Nykytenko (AleXvWaN). This policy describes the FDO website at fdo.alexvwan.me, the desktop application and CLI, and information you choose to send to the maintainer.

External providers, websites, and independently maintained plugins have their own data practices. This policy does not replace their privacy policies.

Website visits and hosting

The website is static. Its source does not include advertising, analytics scripts, tracking pixels, third-party fonts, embedded videos, or account registration. The website code does not set cookies or store visitor identifiers in browser storage.

The copy button writes the displayed CLI example to your clipboard only when you click it. It does not read your clipboard or send its contents to the project.

The website is hosted on GitHub Pages. GitHub states that it logs visitors’ IP addresses for security purposes, including visits made without signing in. See GitHub Pages hosting information and the GitHub Privacy Statement for its processing and retention practices.

Cloudflare manages the domain’s DNS. If Cloudflare proxy or security services are enabled for the site, website requests may also pass through Cloudflare and its services may use security cookies. See Cloudflare’s Privacy Policy and cookie information. The absence of tracking scripts in this repository does not mean that hosting and infrastructure providers process no connection data.

Links to GitHub, npm, releases, and other external pages take you to services governed by their own policies.

Data on your device

FDO uses local files and databases to provide its features. Depending on what you use, a profile can contain settings, plugin registrations and grants, signing certificates, credentials, conversations, notifications, AI usage records, diagnostic logs, workspace snapshots, and observability data. Plugin workspaces and exported files may be stored outside the profile.

Supported sensitive values, including signing private keys and saved service credentials, use Electron’s OS-backed secure storage. This does not mean that every profile file, conversation, log, or workspace is encrypted. Device access controls, backups, and any synchronization tools you use also affect how this information is protected.

Local persistence supports the application’s operation, history, troubleshooting, and recovery. It does not by itself send your local profile to the maintainer. Information can leave your device through the connected features described below or when you choose to share it.

AI, plugins, and connected services

AI features. When you configure and use AI features, prompts and relevant context may be sent to your selected provider or endpoint. Depending on the feature and request, this can include workspace or source-code context, attachments, conversation content, and tool inputs or outputs. A configured endpoint may be local or remote. Review the provider’s terms, retention, and training settings before sending sensitive information.

Plugins and GitOps. Plugins and integrations can communicate with services according to their configuration and granted capabilities. GitOps repositories, remote tools, SSH connections, and other integrations may receive the requests, credentials, or content needed for the operation. Review each plugin’s source, configuration, permissions, and external services before using it.

Observability. FDO records local usage and diagnostic information. Capturing prompts, responses, and tool content in observability traces is off by default and can be configured in Settings → Observability. Optional Langfuse export sends trace data to the configured endpoint when enabled. Environment variables can override those settings. Disabling trace-content capture does not stop an AI provider from receiving the content needed to answer an AI request.

These services may process information in countries other than your own and apply their own retention and deletion policies. The maintainer does not control provider-held copies or the operation of independently maintained plugins.

Information you share with the project

If you email the maintainer or submit an issue, pull request, or attachment, you choose what information to provide. It may include your name or account identifier, email address, message, reproduction steps, and diagnostic material. This information is used to respond, investigate problems, review contributions, and maintain the project.

GitHub issues, pull requests, and their attachments are generally public. Do not post credentials, private keys, complete user profiles, or private workspace content. Follow the security policy for private vulnerability reports.

Retention and your choices

Local data remains on your device according to the feature’s retention settings, configured limits, and actions you take. Observability retention can be adjusted in Settings. Uninstalling the application may leave profile data, workspaces, exports, and backups behind.

You can review plugin grants, remove integrations, change AI providers, and disable optional trace export. To manage or remove local profile files, close FDO first and keep any information you need. Copies in backups, exported files, remote repositories, and external services must be managed separately.

Messages sent to the maintainer are retained as needed to handle the request and maintain relevant project records. Public contribution records and provider logs are subject to the hosting service’s retention practices. Contact the maintainer about access, correction, or deletion of information you sent directly; requests concerning an external account or provider-held data should also be directed to that provider. Applicable privacy rights depend on your circumstances and location.

Changes to this policy

This page will be updated when the described practices change. The date above identifies the latest revision. Changes to the website, hosting configuration, integrations, or data collection should be reflected here before they are introduced.

Privacy questions

Contact Oleksandr Nykytenko at [email protected] with the subject FDO privacy request. Describe the information or feature involved without sending passwords, tokens, or private keys.