Privacy Policy

Last updated: 2 July 2026

This Privacy Policy explains how CodedWords ("we", "us", "our") handles personal data in connection with the Plexus desktop application ("Plexus", the "App") and our website. We are committed to protecting your privacy and to processing personal data in line with the EU General Data Protection Regulation (GDPR).

Note. This policy describes the anonymous, opt-out usage analytics Plexus now collects, and the managed connection service it uses when you connect a git provider — see sections 3 and 5.

1. Who is responsible

The controller for the processing described here is:

CodedWords (a sole proprietorship / eenmanszaak established in the Netherlands)
Registered address: Korhoenstraat 124, Tilburg, Netherlands
KvK number: 75572214
Contact: [email protected]

2. Plexus is local-first

Plexus is a desktop application that runs on your own computer. Your code, files, repositories, terminal sessions, credentials, and the prompts and Output you exchange with AI Agents stay on your device and are not sent to us.

Some data is stored locally on your machine so the App can work — for example, your settings, workspace and session state (in a local database), and any credentials you ask the App to store (kept in your operating system's secure keychain). This data does not leave your device except where you explicitly connect a third-party service (see section 5). The one routine exception is that the App periodically checks our release server for updates (see section 4); that check carries no usage data and none of Your Content.

Two limited, opt-in / opt-out exceptions are described below: when you choose to connect a git provider we use a managed sign-in service (section 5), and Plexus sends anonymous usage analytics you can turn off (section 3). Neither sends us your code, file contents, prompts, file paths, or repository names, and neither changes the local-first default.

3. Usage analytics

Plexus sends anonymous usage analytics to help us understand adoption and improve stability. This processing is active by default; you can turn it off at any time via the analytics.enabled setting in the App (Settings → Privacy).

What is collected: your operating system (coarse — e.g. macOS / Windows / Linux), the app version, a daily-rotating salted hash derived from a random install identifier, and a total-downloads count when you download the App. The salt rotates every day, so the daily hash cannot be linked across days — this lets us count daily active users without being able to recognise a returning user or build a profile.
What is never collected: your code, file contents, prompts, Output, file paths, or repository names.
All analytics data is stored within the European Union.
Legal basis: our legitimate interest in maintaining and improving the App (Article 6(1)(f) GDPR). Because the data is anonymous and non-identifying, we rely on legitimate interest rather than consent; you can opt out in Settings at any time.
The App also honours the DO_NOT_TRACK environment variable, and never sends analytics from development builds.

4. Update checks and our website

To let you know when a new version is available, Plexus periodically contacts our release server — the public plexus-releases repository hosted on GitHub — to download a small update manifest and, if you choose to update, the new release. Like any web request, this reveals your IP address and the current app version to GitHub as the host, but it carries no usage data and none of Your Content. This is a routine update check, not the analytics described in section 3.

When you download Plexus from our website, the download button routes through a lightweight redirect that increments an anonymous total-download counter and then forwards you to the file hosted on GitHub. This records standard request metadata (such as your IP address in transient server logs, processed in the EU) but no usage profile and none of Your Content.

When you visit our website, our hosting provider may process limited technical data needed to deliver the site securely and reliably (such as your IP address in server logs). The website is a static site and does not currently use advertising or cross-site tracking cookies. If we add analytics or other cookies in the future, we will update this policy and provide any required cookie controls.

5. Third-party services you connect

Plexus lets you connect third-party services that you choose, such as:

AI Providers (for example, Anthropic for Claude Code). When you run an AI Agent, your prompts and the relevant parts of Your Content are sent directly from your device to that AI Provider under that provider's own terms and privacy policy. We are not a party to, and do not control, that processing.
Git hosting providers — GitHub and Bitbucket — when you sign in to manage repositories or pull requests.

Managed connection service (OAuth broker). When you connect a git provider, Plexus uses a small service we operate in the European Union to complete sign-in. The provider returns a short-lived authorization code; the service exchanges it for an access token (and refreshes it) using our confidential app credentials, and the token is returned to your device and stored in your operating system's keychain. We do not receive or store your repositories, pull-request contents, or code — after sign-in your device talks to the provider directly. We process only the minimal technical data needed to complete the exchange (such as the authorization code and the provider's token responses), on the legal basis of performing the connection you asked us to make.

Commit author avatars (Gravatar). The project Git client can show avatars next to commits. To resolve an avatar, Plexus sends a one-way SHA-256 hash of a commit author's email address (taken from your local repository's history) directly from your device to Automattic's Gravatar service (gravatar.com), which is how Gravatar is designed to be queried; the email address itself is never sent, and we receive nothing. Results — including "no avatar exists" — are cached on your device so each author is looked up at most occasionally. You can turn this off with the git.avatars.gravatar setting (Settings → Git), in which case Plexus renders initials locally and makes no request. Gravatar's own processing is described in Automattic's privacy policy.

We encourage you to review the privacy policies of any service you connect. We are not responsible for how those third parties process your data.

6. How long we keep data

Data stored locally on your device remains until you delete it or uninstall the App. We retain the anonymous analytics only for as long as necessary for the purposes described above and then delete or further aggregate it; because the daily hash cannot be linked across days, the data is not tied to an identifiable person. We do not retain provider tokens — they live only in your keychain.

7. Your rights

Under the GDPR you have the right to access, rectify, erase, restrict, or object to the processing of your personal data, and the right to data portability, where these rights apply. Because Plexus is local-first, most data is under your direct control on your own device. For any personal data we process, you can exercise your rights by contacting us at [email protected].

You also have the right to lodge a complaint with a supervisory authority — in the Netherlands, the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl).