Terms & Conditions

These Terms & Conditions ("Terms") govern your download and use of the Plexus desktop application ("Plexus", the "App"). Please read them carefully. By installing or using Plexus you agree to these Terms. If you do not agree, do not install or use the App.

1. Who we are

Plexus is made and distributed by CodedWords ("we", "us", "our"), a sole proprietorship (eenmanszaak) established in the Netherlands.

Trading name: CodedWords
Registered with the Dutch Chamber of Commerce (KvK) under number: 75572214
Registered address: Korhoenstraat 124, Tilburg, Netherlands
Contact for legal notices: timo@codedwords.com

2. Acceptance and eligibility

By installing, accessing, or using Plexus you confirm that you:

are at least 18 years old, or the age of majority in your jurisdiction;
have the authority to accept these Terms (and, if you use Plexus on behalf of an organisation, that you are authorised to bind that organisation); and
will use Plexus in accordance with these Terms and all applicable laws.

3. Definitions

AI Agent — any third-party artificial-intelligence coding tool or command-line interface (CLI) that you choose to run through Plexus, such as Claude Code. AI Agents are created, operated, and controlled by their respective providers, not by us.
AI Provider — the third party that develops and operates an AI Agent and/or its underlying models (for example, Anthropic for Claude Code).
Output — any code, text, commands, files, or other material produced, suggested, or executed by an AI Agent.
Your Content — the code, files, repositories, credentials, and other materials on your system that you make available to Plexus or to an AI Agent.
Hosted Content — the part of Your Content that you have asked us to hold on a managed service, and that we therefore store on our servers rather than only on your system: today, what Settings sync keeps, the prompt templates you save to your account, the workspaces an organisation shares with the people in it, the settings an organisation manages for them, and the prompt templates an organisation publishes to them (section 14). It is a subset of Your Content and everything these Terms say about Your Content applies to it; it has its own name only because a few clauses have to say something about material on our servers, and stretching a definition written about your system to cover ours would have made both of them vaguer. The third, fourth and fifth of those are the ones that somebody other than you can put there, and that we hand to somebody other than whoever wrote them: an organisation's administrator writes a shared workspace, publishes a setting or publishes a prompt, and the members of that organisation who hold a seat receive it. So where a clause about Hosted Content says you, it means whoever put the content there — for a shared workspace, a managed setting or an organisation's prompt that is the organisation, not the member whose machine received it.

4. Licence to use Plexus

Plexus is proprietary, closed-source software. Subject to these Terms, we grant you a personal, limited, non-exclusive, non-transferable, non-sublicensable, and revocable licence to download and use the App for your own software-development purposes. The App itself is provided free of charge.

This licence does not depend on paying us anything. Buying a subscription (section 14) does not widen it, and cancelling one does not narrow it. The App you download, install and run is the same App whether you pay us or not, and it is free of charge either way.

What a subscription changes is what our servers will do for you, not what the App is licensed to do. Since version 0.21.0 five features — Settings sync, the prompt library, the workspaces an organisation shares, the settings an organisation manages and the prompts an organisation publishes (all section 14) — work only while your account holds a plan or a seat, because what you are paying for is the managed service on our side that carries each of them. Everything the App does on your own machine sits outside that: sessions, worktrees, the agent terminal, the review tab, the git client, hooks, the dashboard and every setting behave identically for a licence holder who has never signed in and never paid us anything. Nothing that already worked has moved behind the plan, and section 14 explains why that is a commitment rather than a description of today.

Except to the extent this restriction is prohibited by applicable mandatory law, you may not:

copy, resell, rent, lease, distribute, or otherwise make the App available to third parties;
modify, adapt, translate, or create derivative works of the App;
reverse engineer, decompile, or disassemble the App, or attempt to derive its source code;
remove or alter any proprietary notices; or
use the App to build a competing product.

We retain all rights not expressly granted to you. This licence does not transfer any ownership in the App.

5. AI Agents are third-party tools — important

This section is the most important part of these Terms. Please read it carefully.

Plexus is an orchestration layer — a tool that helps you launch, manage, and coordinate AI Agents and terminals on your own computer. Plexus is a wrapper around AI Agents; it is not an AI Agent and does not itself generate code, make decisions, or determine what an AI Agent does.

You acknowledge and agree that:

AI Agents are operated by their providers, not by us. When you run an AI Agent through Plexus, that AI Agent and its models are provided and controlled by the relevant AI Provider under that provider's own terms and policies. We have no control over, and accept no responsibility for, the AI Agent's behaviour or its Output.
We do not review, validate, or endorse Output. Output may be incorrect, incomplete, insecure, outdated, biased, or may infringe third-party rights. AI Agents can make mistakes, "hallucinate", run unintended commands, and modify or delete files.
Plexus acts only on your authorisation. Any action an AI Agent or terminal performs on your system happens because you have run, permitted, or configured it to do so. You control which agents you run, what access they have, and what they are permitted to do.
You must comply with AI Provider terms. Your use of any AI Agent is also subject to that AI Provider's terms of service, acceptable-use, and privacy policies. You are responsible for reviewing and complying with them, including any usage fees the AI Provider charges you.
No affiliation. Plexus is an independent product. We are not affiliated with, endorsed by, or sponsored by any AI Provider. "Claude" and "Claude Code" are trademarks of Anthropic, and all other product names are the property of their respective owners; they are used for identification only.

6. Your responsibilities

You are solely responsible for everything that happens through your use of Plexus and any AI Agent you run, including:

Reviewing all Output before relying on it, committing it, deploying it, or executing it;
the security and integrity of Your Content, your system, your credentials, and your accounts;
maintaining backups and using version control so that unwanted changes can be reviewed and reverted;
any commands run, files created, modified, or deleted, and any commits, pushes, or deployments made;
what the App does on your git provider at your request when you use stacks and ordered merging (section 14) — syncing (rebasing) and re-pushing branches it created (always with a lease that refuses to overwrite a push someone else made), changing the target branch and the stack list in a pull request's description, on GitHub creating, extending and dissolving a stack of your pull requests, and merging the pull requests you choose to merge with Merge, Merge up to here, Merge stack or Merge in order — all of which happen under your own account, as if you had done them yourself — and, unless you change the When a sync conflicts setting, handing a conflict, or uncommitted edits that are in the way, to that session's own AI Agent to resolve in its worktree (section 5);
any data you choose to send to an AI Provider, to another third party, or to us — through the App's Feedback form, or by switching on Settings sync (section 14), which shows you in full what it would send before it sends anything and lets you exclude any workspace or project — including whether that data may contain confidential, personal, or proprietary information;
if you administer an organisation, what you hand to its members through a workspace it shares (section 14) — its name, its description, the repositories attached to it and the clone address every member's machine is offered — the setting values you recommend to them or enforce on their machines (section 14), and the prompt templates you publish to them (section 14) — text their AI Agents will be asked to act on — and whether you are entitled to hand those to the people you are handing them to; and
any costs, fees, or charges you incur with AI Providers or other third-party services.

We strongly recommend running AI Agents only on code you can afford to lose or restore, and reviewing the permissions you grant them.

7. Acceptable use

You agree not to use Plexus to:

break any applicable law or regulation, or infringe anyone's rights;
develop or distribute malware, or carry out unauthorised access to any system or data;
violate the terms or acceptable-use policies of any AI Provider or third-party service;
attempt to disrupt, compromise, or circumvent the security or intended operation of the App; or
submit feedback through the App that is unlawful, abusive, deceptive, or that contains malware; that contains someone else's personal data, or confidential or proprietary material you are not entitled to disclose; or that is sent in volume, automatically, or in any way intended to overload or abuse the feedback service; or
store Hosted Content with us that is unlawful, or that contains material you are not entitled to store or disclose; or use a managed service in volume, automatically, or in any way intended to overload or abuse it.

We do not read what you store there, and this rule is not a licence to start. The rule above exists because a hosting service needs one, not because anything of ours inspects Hosted Content: we have built no screen that reads it and no process that scans it, the Privacy Policy says so field by field, and we would have to change both this document and that one before either could become untrue. If a lawful request or an abuse report ever obliged us to look at a specific account's Hosted Content, that is the only circumstance in which we would, and we would tell you unless the law forbade it.

8. Third-party services and open-source components

Plexus integrates with third-party services you choose to connect (for example, AI Providers, git hosting providers — GitHub and Bitbucket — and the work-management service Plnnrly) and, when you connect a git provider, uses a managed connection service we operate in the EU to complete sign-in (see the Privacy Policy). A Plnnrly organization is connected directly from your device to that organization, without that service, and what you do in a Plnnrly tab is done in Plnnrly under your own Plnnrly account. Your use of the third-party services themselves is governed by their own terms — for Plnnrly, by your organization's agreement with Plnnrly — and we are not responsible for them.

Invoicing and payments — Moneybird. If you buy a subscription (section 14), we bill and invoice it through Moneybird B.V., our invoicing and payment provider, established in the European Union. Two things you will see are pages Moneybird hosts on its own domain, not ours: the checkout page where you buy a plan and set up how you pay, and the customer portal you reach from Manage billing in the app or Payment method & invoice PDFs on the account website, where you change your payment details, look at your invoices, and cancel. We send you to each of them with a link that is valid for one hour. While you are on those pages you are dealing with Moneybird, and Moneybird's own terms and privacy policy apply there; nothing in these Terms changes them.

Your card, bank-account and direct-debit mandate details are given to Moneybird and never to us. We do not receive them, we do not store them, and we could not act on them — the most we ever hold is the fact that a valid mandate exists. Moneybird issues and stores your invoices and determines the VAT on them. The Privacy Policy sets out exactly what Moneybird receives and what we keep.

Plexus also includes open-source software components, each licensed under its own terms. A list of these components and their licences is available in the App (Settings → About) and on our website at /attributions. Nothing in these Terms limits your rights under those open-source licences.

9. Intellectual property

Our IP. The App, its design, and all related intellectual-property rights are owned by us or our licensors.
Your Content. We claim no ownership over Your Content. As between you and us, Your Content remains yours.
Output. As between you and us, we claim no ownership of Output. Rights in, and responsibility for, Output are determined by the relevant AI Provider's terms and by applicable law. You are responsible for confirming that your use of Output does not infringe any third party's rights.
Hosted Content. Hosted Content stays yours, and we claim no ownership of it. So that we can actually run the services you asked for, you grant us a non-exclusive, worldwide, royalty-free licence to store, copy, transmit and display it back to you and to the machines you sign in on, for the sole purpose of providing those services — and for nothing else. Where the Hosted Content is a workspace an organisation shares, a setting it manages, or a prompt template it publishes, that licence extends by exactly one step: to displaying it to the members of that organisation it was shared with, on the machines they sign in on — for a setting the organisation enforces, to the App applying it there, and for a prompt it publishes, to the App rendering the current revision into a member's terminal for that member to send or not — because delivering it to them is the whole of the service. It reaches nobody outside the organisation, and nothing a member then does with that workspace, beneath that setting or with that prompt on their own computer becomes ours to see. It is not a licence to read it, to analyse it, to train anything on it, or to show it to anyone but you. The licence lasts only as long as we hold the content: delete it, or delete your account, and it ends with it. Settings sync shipped in version 0.21.0 without this clause and the prompt library made the gap impossible to leave standing; adding it now closes it for both.
Feedback. Feedback you send us through the App stays yours; we claim no ownership of it. By sending it you grant us a non-exclusive, worldwide, royalty-free licence to store it and to use it to diagnose problems and improve Plexus. Feedback is not confidential and we owe you nothing for it, so please do not send us anything you need kept in confidence. You are responsible for what your submission contains — including any screenshot or diagnostic log you choose to attach — and you should not send material you are not entitled to disclose. How we handle it, and how to have it deleted, is set out in the Privacy Policy.

10. Disclaimer — the App is provided "as is"

To the maximum extent permitted by applicable law, Plexus is provided "as is" and "as available", without warranties of any kind, whether express or implied, including any implied warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, or availability.

We do not warrant that the App will be uninterrupted, error-free, or secure, or that any Output produced by an AI Agent will be correct, safe, lawful, non-infringing, or fit for any purpose.

Nothing in these Terms excludes or limits any rights you have under mandatory Dutch or EU consumer-protection law that cannot lawfully be excluded or limited.

11. Limitation of liability

To the maximum extent permitted by applicable law:

We are not liable for the acts, omissions, or Output of any AI Agent or AI Provider, nor for any consequences of actions performed on your system by an AI Agent or terminal that you ran, permitted, or configured.
We are not liable for any loss of or damage to data, code, or files; corrupted or deleted work; security incidents; lost profits, revenue, or goodwill; business interruption; third-party fees or charges (including AI Provider usage costs); or any indirect, incidental, special, or consequential damages, in each case arising out of or in connection with your use of the App or any AI Agent.
Our total aggregate liability arising out of or in connection with the App and the services described in section 14 is, to the extent permitted by law, limited as follows. For the App and the free services, which are provided free of charge, the limit is fifty euros (€50). Where you pay us for a subscription (section 14), the limit is instead the greater of fifty euros (€50) and the fees you paid us for that subscription in the twelve months before the event giving rise to the claim — a limit that grows with what you have actually paid, rather than one premised on your having paid nothing.

Nothing in these Terms excludes or limits our liability where it cannot lawfully be excluded or limited — including liability for death or personal injury caused by our negligence, for fraud or fraudulent misrepresentation, for intent or deliberate recklessness (opzet of bewuste roekeloosheid), or under any non-excludable consumer rights.

12. Indemnity

To the extent permitted by applicable law, you agree to indemnify and hold us harmless from any third-party claims, losses, and reasonable costs arising out of your misuse of the App, your breach of these Terms, your use of Output, or your violation of any law or third-party rights.

13. Privacy

Our handling of personal data is described in our Privacy Policy. Plexus runs locally on your device; the limited, anonymous usage analytics, the managed connection service we operate, the optional feedback you can choose to send us — which, unlike the analytics, is not anonymous — the optional Plexus account you can create, Settings sync if you switch it on, and — if you buy one — the subscription and the invoices raised for it are all described there. Settings sync is the one of them that copies part of your own configuration to us, so the Privacy Policy sets out field by field what it takes, what it structurally cannot take, and how you delete it.

14. Managed and paid services

Plexus is and remains local-first. We operate ten managed services, all hosted in the EU and all described in the Privacy Policy. Four of them are free: an optional connection service (a sign-in broker for GitHub and Bitbucket), anonymous usage analytics, an optional feedback service that receives what you write and choose to attach when you press Send, and an optional account service — a Plexus account and the organisations you can create from it, managed either in the App or in the account panel on our website. The fifth is the subscription itself: an optional subscription service, the plans set out under Paid subscriptions below, billed and invoiced through Moneybird (section 8). The sixth is the first thing a subscription buys: an optional settings sync service, which holds your Plexus settings and the names of your workspaces and projects on your account so that they follow you to the other machines you sign in on. It is off until you switch it on in the App, it runs only while your account holds a plan or a seat, and What a subscription unlocks below says what it does and what it can never reach. The App names it Settings sync where it tells you what your plan includes and Cross-device under Settings → Sync, and version 0.21.0's release notes call it cross-device sync; these Terms mean the same feature by all three. The seventh is the second thing a subscription buys: an optional prompt library service, which holds the prompt templates you save so that they follow you to the other machines you sign in on. It is off until you switch it on in the App, and a plan or a seat is what lets it store a new one — reading, running, exporting and deleting the templates you already have never require one, because a complete copy of your library stays on your own computer. Prompts a project commits to its own repository are never sent to us at all. The eighth is the third thing a subscription buys, and the first of the eight that carries something from one person to another: an organisation workspace service, which holds the workspaces an organisation chooses to share — each one's name, its description, its rule about who may join, and the repositories attached to it — and hands them to the members of that organisation who hold a seat. An administrator writes it and a member receives it; Workspaces an organisation shares below sets out what that lets an administrator do, and the much shorter list of what it does not. The ninth is the fourth thing a subscription buys, and the second that carries something from one person to another: an organisation settings service, which holds the setting values an organisation chooses to manage for its members — each one's setting, its value, and whether the organisation recommends it, enforces it or is only measuring what enforcing it would do — and hands them to the members of that organisation who hold a seat, where the App sets a recommended value once and applies an enforced one above the member's own. It is the first of the ten that can lock something on a member's machine, and Settings an organisation manages below sets out exactly what that lets an administrator do, what it does not, and the one yes-or-no answer a member's machine sends back during a measurement. The tenth is the fifth thing a subscription buys, and the third that carries something from one person to another: an organisation prompt library service, which holds the prompt templates an organisation chooses to publish — each one's name, its description, its text, its fields, and the numbered revisions it has been through — and hands the current revision of each to the members of that organisation who hold a seat and whose role lets them use it, where the App lists it beside the member's own templates, badged with the organisation's name. It is the first of the ten that hands one person's words for an AI Agent to another person's, and Prompts an organisation publishes below sets out what that lets an administrator do, what it does not, and the three things a published prompt may never contain.

The analytics are part of the App and carry nothing that identifies you, your machine, or your work; there is no setting to switch them off, though the App honours the DO_NOT_TRACK and PLEXUS_NO_TELEMETRY environment variables. The feedback service is the only one of the ten that receives something you wrote for us to read — a message, and whatever you choose to attach to it — and the only one that can carry your code, your file contents, your prompts or an AI Agent's Output; it does nothing unless you use it. Settings sync also carries text you typed, in that the instructions you set for the review, fix and commit-message agents travel as part of your settings, but that is your own configuration in transit between your own machines rather than a message addressed to us. The account service holds the details you type into it: your name, your email address, and the names of the organisations you create. If you buy a subscription it also holds what an invoice needs — the billing details you enter (such as a company name, an invoice address, a country, a VAT number and an invoice email address) — together with which plan you hold, how many seats it pays for and which of your organisation's members hold them. None of it is about your work, and none of it is used for anything but running and invoicing the plan.

The settings sync service holds only what the App showed you before it took anything: the settings you have changed from their defaults, the names of your workspaces and projects, each project's repository slug and clone address, and up to twenty previous versions of that so you can restore one. It holds no code, no file contents, no sessions, no transcripts and nothing from your keychain; you can exclude any workspace or project from it; and what it holds is yours personally — attached to your own account and never to an organisation, even where an organisation's plan pays for your seat, so nobody else in that organisation can see it. The Privacy Policy sets it out field by field, including what structurally cannot leave your machine and the two ways you delete what has.

It is a synchronisation service, not a backup service, and we would rather say so here than have you find out. The copy on your own machine is the one that matters; what we hold is there to reach your other machines, and the twenty versions it keeps are a convenience for undoing a change, not an archive of your configuration. Keep your own backups as section 6 asks, and do not treat sync as one.

A Plexus account is free and entirely optional. If you create one:

you are responsible for the details you register, for keeping your password and any two-factor recovery codes secure, and for everything done through your account;
you must be entitled to use the email address you register it with, and you may not create an account for someone else or impersonate anyone; and
we may suspend or close an account used in breach of section 7, and you may delete yours at any time (section 16).

Five parts of the App are conditional on having an account — Settings sync, saving a prompt template to your account, receiving the workspaces an organisation shares, receiving the settings it manages, and receiving the prompts it publishes — and each needs a plan or a seat besides, because a subscription has nothing else to attach to. They are the only five: everything Plexus did before version 0.21.0 works with no account, no plan and no seat, and nothing in this section changes the licence granted in section 4. Nothing that works without an account today will ever start requiring one.

Workspaces an organisation shares. An organisation can set a workspace up once — a name, a description, a rule about who may join, and a list of the repositories that belong in it — and hand it to the members who hold a seat on its plan. It is the first thing in Plexus where configuration somebody else wrote arrives on your computer, and a workspace can reach you without your having asked for it, because that is what an organisation sharing one means. The App tells you where each one came from. What an administrator can and cannot do is therefore worth stating exactly, and it is shorter than it sounds.

What an administrator provides, and can withdraw. They create a shared workspace; they change its name, its description and its joining rule; they attach and detach the repositories that belong in it; they add and remove the people who have it; and they withdraw the whole workspace from the organisation's catalogue. That is the entire list, and every item on it is the same act — providing shared configuration, or ceasing to provide it.

What an administrator cannot reach on a machine that received it. Your checkouts, your worktrees, your sessions, your branches, your commits, your terminals, what you said to an AI Agent and what it said back, the settings you set on the workspace yourself, and everything else on your disk. None of that is ours to show them: we do not hold it, we have built no screen that would display it, and sharing a workspace with you grants an organisation no access whatsoever to the computer it appears on.

And no instruction of ours deletes anything on your machine. Withdrawing a workspace, detaching a repository, removing somebody from a workspace, leaving one yourself, and a plan that lapses all do the same thing to the computer that has it: the workspace stays, its repositories stay, and their sessions, worktrees and branches are left exactly as they are. The workspace simply stops being the organisation's and becomes an ordinary workspace of your own. The App has no instruction from us that removes a repository, a worktree, a branch or a session — not for a withdrawal, not for a removal, not for a lapse, and not for an organisation that was deleted. Nothing is copied onto your disk in the first place until you ask for it: an attached repository is an address and a name until you choose to clone it and choose where it goes.

Leaving is always yours. Leave sits on the workspace itself and is never refused — not for want of a plan, a seat, a permission or a working connection. Being able to stop receiving something somebody else put on your machine is not the kind of thing a subscription, or an administrator, gets to take away.

If you administer an organisation, what you share is yours to answer for. The name, the description, the repositories and the clone addresses in a shared workspace reach other people's machines because you put them there (section 6), and what you store with us to do it is Hosted Content like any other — section 7 applies to it exactly as it does to everything else.

Settings an organisation manages. An organisation can also publish a setting value to the members who hold a seat on its plan, at one of three levels, and this is the first thing in Plexus by which somebody else can lock part of your configuration. So the three levels, and the limits of each, are stated here rather than left to the App's own description. A recommended value is set once on each member's machine as their global value, and is theirs to change from that moment: the App never writes a recommendation over a value the member has since changed, and withdrawing one removes only a value the member never touched. An enforced value applies on every machine the member signs in on, above every value of their own, and the row it governs is read-only there until the organisation stops enforcing it; the member's own value is kept underneath and returns when it does. An evaluation changes nothing on any machine: each machine answers one yes or no — whether the value there differs from the one proposed — and the administrator sees how many machines answered each way, folded so that fewer than five are never shown, and never who. The settings an organisation can manage are exactly the ones Settings sync can carry: never one that describes the machine itself, and never a credential.

What an administrator can do. Publish a setting as a recommendation or an evaluation; change its value or its level; enforce it and stop enforcing it; and withdraw it. That is the entire list, and every item is the same act as with a shared workspace — providing shared configuration, or ceasing to provide it — with one addition, that an enforced value is configuration a member cannot decline while it stands.

What an administrator cannot reach. Everything on the machine. They cannot see a member's own value for a managed setting, nor for any other; they cannot see which layer a member set it at, nor whether a member changed a recommendation; and the value an enforced setting shadows is still the member's, kept on their machine and shown to them beside the organisation's, never sent to the organisation or to us. Nothing else on the machine — checkouts, sessions, branches, terminals, what a member said to an AI Agent — becomes reachable by managing a setting on it, and the one thing a machine sends back is the yes-or-no answer during an evaluation, which exists only while the evaluation does and carries no value, no override and no name.

An enforced value keeps applying when we cannot be reached, and stops only when the person leaves. Offline, on a plan that has lapsed, or after a seat has been taken back, an enforced setting keeps its last known value on the member's machine — nothing unlocks for want of a connection, because a lock that opened whenever the network dropped would not be one. What ends it is the organisation withdrawing the setting or ceasing to enforce it, or the member leaving the organisation or being removed from it, at which point the organisation's values are dropped and the member's own return. Withdrawing a setting and ceasing to enforce one are never refused — not for want of a plan, a seat or a working connection — for the reason given under Workspaces an organisation shares: an organisation must always be able to take back what it handed out.

If you administer an organisation, what you manage is yours to answer for, as with a workspace: the values you recommend or enforce reach other people's machines because you put them there (section 6), and what you store with us to do it is Hosted Content like any other.

Prompts an organisation publishes. An organisation can also publish a prompt template — a name, a description, a prompt written for an AI Agent with the parts that change turned into fields — to the members who hold a seat on its plan, and this is the first thing in Plexus by which somebody else's words for an AI Agent arrive in the box you send to yours. So what an organisation's prompt is, and the limits on it, are stated here rather than left to the App's own description. A published prompt appears in a member's own template list beside their own templates, badged with the organisation's name; it never replaces, hides or edits a template of the member's own, and a member's own library is never opened to the organisation by it. It is delivered as numbered revisions with a movable pointer: every proposal is a new revision that is never edited once it exists, publishing moves the organisation's current pointer onto it, rolling back moves the pointer onto an earlier revision, and a member's machine receives only the current one. The App types a rendered prompt into the terminal and never sends it: the member reads it and presses return, exactly as with their own templates.

What an administrator can do. Propose a revision; publish it; roll the pointer back to an earlier revision; discard a draft; and delete (retire) the template, which removes it from every member's list and deletes its revisions. That is the entire list, and every item is the same act as with a shared workspace — providing shared configuration, or ceasing to provide it — with the qualification that here the configuration is text a member's AI Agent will be asked to act on, which is why the next paragraph exists.

What a published prompt may not contain, and what the App does regardless. A prompt's text is typed into an AI Agent's input on the member's machine, where a line beginning with ! runs a shell command, a line beginning with / runs a command of the AI Agent's, and @ followed by a path attaches a file. We refuse to store, publish or roll back to a revision whose text begins with ! or / or names a file as @path, and the App removes those from an organisation's prompt as it types it, on the member's machine, whatever our servers answered. A member's own templates and the ones a repository commits keep all three, because the member chose that content. No organisation prompt can run a command, attach a file or send itself on a machine that received it.

What an administrator cannot reach. Everything on the machine. They cannot see a member's own templates, which templates a member ran, what a member typed into a prompt's fields, or the finished prompt; nothing else on the machine — checkouts, sessions, branches, terminals, what a member said to an AI Agent and what it said back — becomes reachable by publishing a prompt to it, and nothing a member's machine sends back for this exists: asking for the organisation's list carries the sign-in token and a number saying how much of the list the machine has already seen, and nothing else.

A published prompt keeps working when we cannot be reached, and leaves only when the person does. Offline, on a plan that has lapsed, or after a seat has been taken back, every organisation prompt already on the member's machine keeps listing and running at the revision it last received — what a lapse ends is the arrival of the next revision. And no instruction of ours deletes anything of the member's own. An organisation's prompts are removed from a machine when the organisation deletes the template, when the member leaves the organisation or is removed from it, or when the organisation's answer says the member's role may no longer use its prompts — never on a failed connection — and the member's own templates are untouched by all of it. Deleting a template and discarding a draft are never refused — not for want of a plan, a seat or a working connection — for the reason given under Workspaces an organisation shares: an organisation must always be able to take back what it handed out.

If you administer an organisation, what you publish is yours to answer for, as with a workspace and a setting: the prompts you publish reach other people's machines and their AI Agents because you put them there (section 6), and what you store with us to do it is Hosted Content like any other — section 7 applies to it exactly as it does to everything else.

Paid subscriptions. Earlier versions of these Terms said we might in the future offer paid services under separate terms presented to you at the time. That future has arrived, and these Terms are those terms — there is no separate document to agree to, and there will not be one for the plans described here.

What you can buy. Two plans. An individual plan, held by one Plexus account, and an organisation plan, sold per seat, where you choose how many seats your organisation pays for. Both are monthly, priced in euro (EUR), and both renew automatically until cancelled (section 16). A subscription requires a Plexus account; an organisation plan requires an organisation you own, or one that has given you a role carrying its billing. A single account may hold both an individual plan and one or more organisation plans; each is a separate subscription with its own invoices.
Prices. Prices are shown to you on the checkout page before you pay, together with the VAT that applies to you. We may change a price; if we do, we will tell you before the new price applies to you, and you may cancel (section 16) if you do not want to continue at it. We do not apply a price change to a period you have already paid for.
Seats. You can add or remove seats at any time. A seat change is billed pro rata by our invoicing provider — it raises the additional invoice for a seat you add. Whether removing a seat produces a credit is determined by that provider, not by us. Assigning a seat to a member is how that member gets the paid features your organisation's plan includes. Today that is seven things: Settings sync, saving a prompt template to their account, receiving the workspaces your organisation shares, receiving the settings it manages, receiving the prompts it publishes, working a project's issue tracker inside the App, and stacks and ordered merging. The first two are that member's own sync and their own library, on their own account: paying for somebody's seat gives you no sight of either and no way to reach them — the organisation's prompt library is a separate library, the organisation's own, and publishing to it never opens a member's. The sixth and seventh run between the member's machine and their own GitHub, Bitbucket or Plnnrly account, and you see none of it either. The other three run the other way — they are what your organisation hands to them — and what an administrator may do with each, and may not, is set out under Workspaces an organisation shares, Settings an organisation manages and Prompts an organisation publishes above. A member without a seat keeps everything else the App does, in full and unchanged. More members than seats is allowed, and a member without a seat is a member in every other respect.
VAT and invoices. VAT is determined by our invoicing provider from the country, address and tax number in your billing details, and your invoices are issued and stored by that provider — not by us. You reach them, and your payment details, through Manage billing (section 8). Giving us accurate billing details, including a VAT number where you rely on one, is your responsibility, and a VAT treatment that follows from details you gave incorrectly is not ours to reverse.
Payment. Payment is collected by our invoicing provider using the method you set up at checkout, including automatic direct debit where you authorise it. If a payment fails, that provider sends the reminders. We do not switch anything off while an invoice is merely overdue — an unpaid invoice is a payments matter, and it is handled as one.
What a subscription unlocks, and what it can never take away. Today a subscription unlocks exactly seven things: Settings sync, saving a prompt template to your account, receiving the workspaces an organisation shares, receiving the settings it manages, receiving the prompts it publishes, working a project's issue tracker — its GitHub issues and project boards, or a Plnnrly project's work items, board and sprints — inside the App, and stacks and ordered merging, called stacked pull requests with a land queue before version 1.3.0 — the first five described above and set out field by field in the Privacy Policy, the sixth described in section 5 of the Privacy Policy, because it runs between your machine and GitHub, or your own Plnnrly organization, with your own sign-in and stores nothing with us; what it gates is reading and changing what those tabs show, and attaching a tool, the link a session carries and the closing line in a pull request's description are not part of it. Changes you make there are made on GitHub under your own account, as if you had made them on github.com, and GitHub's terms govern them — or, in a Plnnrly tab, in your Plnnrly organization under your own Plnnrly account, governed by your organization's agreement with Plnnrly. The seventh runs the same way, between your machine and your own GitHub or Bitbucket account: what it gates is the automation — syncing, retargeting and merging a stack, keeping its stack on GitHub in step, and merging pull requests in order — while basing a session on another session's branch, opening a pull request against any branch, seeing a session's state and its stack, unstacking, and the rule that keeps a branch another session depends on are not part of it. Every push, edit, GitHub stack and merge it makes is made under your own account and governed by your provider's terms. None of them existed before the subscription did. It removes no limit, because there is no limit to remove: every session, worktree, git operation, review and agent behaves identically whether you pay us or not, and whether or not you hold a seat. Two commitments govern this and everything we add after it, and they are permanent rather than descriptions of today.
Nothing that already works will stop working, or start requiring a plan. Everything a plan unlocks will be something new, as Settings sync was — it did not exist before version 0.21.0, and nothing that did was moved behind it. We will not put a fence around a part of the App you already have, and we will not introduce a limit on the free part in order to sell its removal — no cap on sessions, projects or worktrees, then or ever.
We will say so before it happens. Any feature that becomes conditional on a plan or a seat arrives as an announced change to these Terms and to the App — in the release notes you see when you update — never silently. That clause has now been exercised seven times, and this is what it looks like: version 0.21.0's release notes carry a section of their own for each — Settings sync, the prompt library, the workspaces an organisation shares, the settings it manages, the prompts it publishes, your issue tracker inside Plexus, and stacked pull requests with a land queue — saying what the feature is, that it needs a plan or a seat, and that nothing which already worked moved behind any of them; and the same changes are in this revision of these Terms, which is the one you are reading. A section in those release notes is therefore a compliance surface, not a courtesy: it is where this promise is kept, and a feature that became conditional without one would be a breach of this clause rather than an omission from a document.
What a subscription buys, then, is the managed services that carry it — Settings sync, your prompt library, the workspaces your organisation shares, the settings it manages, the prompts it publishes, and your plan, your organisation and the seats on it, kept and invoiced by us for as long as you pay for it — and, plainly, your support for the App's continued development.

15. Changes to the App and these Terms

We may update, change, or discontinue the App, or update these Terms, from time to time. If we make material changes to these Terms, we will update the "last updated" date above and, where appropriate, provide additional notice. Your continued use of the App after changes take effect constitutes acceptance of the updated Terms.

16. Termination, cancellation and refunds

You may stop using Plexus and uninstall it at any time. We may suspend or terminate your licence to use the App if you materially breach these Terms.

You can delete your Plexus account at any time from the account panel, once you have deleted any organisation you own. Doing so does not affect your licence to use the App, which does not require an account. If you hold a subscription, deleting your account cancels it.

A subscription renews monthly. A paid subscription (section 14) runs for a monthly term and renews automatically at the end of each term until it is cancelled. There is no minimum term beyond the month you are in, and no cancellation fee.

Cancelling is self-service. You cancel through Manage billing — the customer portal our invoicing provider hosts (section 8) — at any time and without asking us. Cancellation takes effect at the end of the period you have already paid for: the subscription runs to the end of that period and then ends. We do not claw back the period already paid, and we do not bill you for it again.

If we change a price. We will tell you before a new price applies to you, so that you can decide. If you do not want to continue at the new price, cancel before it takes effect, and cancellation works exactly as above — you keep the plan for the period you have paid for, at the price you paid.

What cancelling switches off, and what it does not. Today: the seven things a plan unlocks stop, and nothing else does. Your machines stop exchanging settings with us, saving a new prompt template to your account stops, the workspaces your organisation shares stop being updated, and so do the settings it manages and the prompts it publishes; an Issues or Board tab stops fetching and changing what it shows, and the tools you attached, the sessions you started from an issue and the links they carry stay exactly as they are; stacked sessions stop being synced, retargeted and merged by the App, and stay nested where they are, still showing their state. Every machine keeps every setting, workspace and project it already has — the copy on your disk is the real one, and neither cancelling nor anything we do touches it. A workspace your organisation shared with you stays exactly where it is, with its repositories, its sessions, its worktrees and its branches; what ends is the arrival of the organisation's changes to it. A setting your organisation enforced keeps its last known value on every machine that holds it — a lapse unlocks nothing — until the organisation withdraws it or you leave the organisation, and the value of your own that it shadows is kept for that day. A prompt your organisation published stays on every machine that received it, listing and running at the revision it last received; what ends is the arrival of the next one. Your organisation continues to exist, its members remain members, their roles are unchanged, and the seats they were assigned stay assigned. No session, worktree or repository is affected, and the App otherwise behaves exactly as it did the day before.

Cancelling does not delete what the sync service holds, and does not hold it hostage either. We keep it, so that resubscribing picks up where you left off instead of starting empty. You can delete it whenever you like with Stop syncing and forget what we hold in the App, and that button keeps working for the whole of the period you have already paid for, so cancelling never traps it. Deleting your Plexus account removes it too, at any time and whatever the state of your plan. The Privacy Policy says exactly what is kept and names the one case where that button is refused.

And a lapsed plan never traps anybody in a shared workspace, under a managed setting, or with a published prompt. Leaving a workspace, removing somebody from one, detaching a repository and withdrawing a workspace all keep working after a plan has ended, and so do withdrawing a managed setting and ceasing to enforce one, and deleting an organisation prompt or discarding its draft — deliberately, because an organisation that could no longer take back what it had handed out would be unable to stop a departed colleague receiving it, or to unlock a row it had locked on their machine, which is exactly backwards. What a lapse stops is creating and changing; what it never stops is ceasing.

That is the general rule as much as today's instance: cancelling switches off the features a plan unlocks and nothing else. In particular it never reaches what your machine has already produced: anything the App computed from your code stays on your disk, in a format you can read without us, and we do not delete it, move it, watermark it, or put a deadline on exporting it. What ends is the making of new work, not the work already made — and, as today, the subscription and the invoicing for it.

Refunds. Because a subscription is cancelled with effect from the end of a period that has already run, we do not refund part-months, and we do not refund a period during which the service was available to you. This does not affect the withdrawal right below, any refund we owe you under mandatory consumer law, or a payment taken in error.

Your 14-day right of withdrawal, and how you give it up. If you are a consumer in the EU, you normally have 14 days to withdraw from a distance contract without giving a reason. A Plexus subscription is a digital service we begin providing immediately: there is no trial period, and the plan is in place from the moment the purchase completes. So before you can buy, we ask you to tick a box — it is unticked, we never tick it for you, and the Buy button does not work until you tick it — by which you expressly ask us to begin performance immediately and acknowledge that you thereby lose your right of withdrawal. We record the moment you gave that acknowledgement, before the purchase starts. This is the mechanism in article 16(m) of Directive 2011/83/EU, implemented in the Netherlands as article 6:230p(f)(2) of the Dutch Civil Code. If you would rather keep the 14 days, do not tick the box and do not buy: we cannot start a plan without it. Nothing here affects your rights if what we provide is not what we said it would be.

Sections that by their nature should survive termination (including IP, disclaimers, limitation of liability, and indemnity) will survive.

17. Governing law and disputes

These Terms are governed by the laws of the Netherlands, without regard to conflict-of-law rules. Any disputes will be submitted to the competent court in the Netherlands, unless mandatory law (including consumer law) grants you the right to bring proceedings in, or requires the application of the law of, another jurisdiction.

18. Miscellaneous

Severability. If any provision of these Terms is held invalid or unenforceable, the remaining provisions remain in full force, and the invalid provision will be replaced by a valid one that most closely reflects the original intent.
No waiver. Our failure to enforce any provision is not a waiver of it.
Assignment. You may not assign these Terms without our consent. We may assign them in connection with a merger, acquisition, or sale of assets.
Entire agreement. These Terms, together with the Privacy Policy, are the entire agreement between you and us regarding the App.

19. Contact

Questions about these Terms? Contact us at timo@codedwords.com.