Plugin Developer Terms

To publish, you need an arbastro account that is signed in and has:

• a verified email address;
• a second factor: two-step sign-in or a passkey;
• acceptance of these terms.

A plugin's id is your author name and the plugin's name (author.name, lowercase). The first account to submit an id owns it, and no other account can publish under it.

You must be old enough to make a binding agreement where you live. If you publish for a company, school or other organization, you confirm you may bind it to these terms, and "you" includes it. Keep your account secure: anything published from it is treated as yours.

You keep ownership of your plugin. You grant arbastro a worldwide, non-exclusive, royalty-free license, for as long as the plugin is in the directory and for a reasonable time after it leaves, to:

• host, copy and store every version you submit, its listing and its images;
• run, test, analyze and screen it, by automated checks and by people, to decide whether to publish it and to keep checking it afterward;
• distribute it to people who install it, and let them run it in Athanor under the license you choose for it;
• show its name, icon, images and listing in the directory, on athanor.arbastro.com and in promotion of the directory;
• sign each version we publish (Athanor's Ed25519 key, over the plugin id, version, the package's SHA-256 and its permissions and sites) and keep the records needed to stop a version from loading.

Athanor hosts every published version, and the app installs only packages Athanor has signed, downloaded from Athanor's own storage, never from your server, so that a version can be stopped everywhere at once if it has to be. Plugins you run in developer mode are unsigned and stay on your own computer. People who install your plugin get the license you state in the listing; if you state none, they may use it in Athanor and nothing more.

For every version you submit, you promise that:

• The work is yours to publish. You own it or have every right needed, including for any code, images, data or structures from others, and you follow their licenses and attribution terms.
• It does what the listing says, and nothing it hides. No malware, no deliberately harmful behavior, no attempt to get around Athanor's sandbox, limits or checks.
• Its permissions are honest. It asks only for what it needs, the reason you give for each permission is true, and it reaches only the sites it names in its manifest (never "any site").
• Your data answers are true. Your answers to the two data questions in the Publish window (does it send document content anywhere, and does it store anything) are accurate, and stay accurate for every update.
• It is lawful, including export, privacy, consumer and intellectual property law where it is offered.
• Your support contact works, and you will answer reasonable questions from people who use it.

• Dangerous chemistry. Offer routes, syntheses or procedures for controlled substances, chemical weapons or their precursors, or ship structures that Athanor's safety screen refuses. The same rule applies inside Athanor itself.
• Harvest credentials. Ask for or collect passwords, tokens, payment details or any account credentials, for Athanor or anything else.
• Use the network undeclared. Send or receive anything outside the domains in its manifest, or disguise what it sends.
• Track people. Fingerprint, profile or follow users, or add advertising or analytics that collect personal data, beyond what the user turns on and your data answers state.
• Sell user data, or share it for any purpose the user did not ask for.
• Infringe anyone's copyright, trademark, patent or other rights, or imitate another plugin, author or arbastro.
• Mislead. A listing that misdescribes the plugin, fake reviews or ratings, or reviewing your own plugin.
• Publish unlawful or abusive content, or anything the community text filter would refuse.

Treat anything a plugin can read, a document's contents above all, as the user's and not yours. Use it only to do what the user asked the plugin to do, keep and send it only as your data answers say, protect it, and never sell it. If any data leaves the user's computer, link a privacy policy from your listing that says what you collect and why. Beyond “Know who you are” (a display name and avatar), a plugin has no access to the person's arbastro account, and Athanor never gives it their password, email address or session token. A person grants each permission and can take any of them back later.

Every version is screened automatically, and new plugins and updates that add permissions or network domains are also reviewed by a person before they reach anyone, as the Review Guidelines describe. An account may submit up to 20 versions a day. We decide what the directory carries. We may, at any time and without prior notice where people or their data are at risk:

• decline to publish a plugin or a version, or ask for changes;
• delist it, so it no longer appears in search while people who installed it keep it;
• take it down, which disables it for everyone the next time Athanor checks its blocklist;
• add a plugin, version or developer account to the blocklist;
• suspend your publishing access.

We will tell you why, unless the law or someone's safety prevents it, and you may appeal by replying to that message or writing to [email protected]. We may also act on reports from users, which can hide a plugin from the directory until it is reviewed.

Publishing is free, and plugins in the directory are free to install. Paid plugins are not available. If that changes, it will come with its own terms, and nothing here gives you a right to charge users through Athanor.

You may unpublish your plugin at any time from its page in Development; people who installed it may keep the version they have unless we take it down. We may end these terms for you if you break them or the law, or if we close the directory, in which case we will give reasonable notice where we can. The sections on the license (for copies already distributed), your promises, user data and liability survive.

The directory, the plugin system and the review are provided "as is". Review lowers risk but does not make a plugin correct or safe, and our publishing your plugin is not an endorsement or a warranty of it. You are responsible for your plugin and for what it does.

To the extent the law allows, arbastro is not liable for indirect or consequential losses, lost profits or lost data arising from the directory or from your plugin, and the liability limits in the arbastro Terms of Service apply. You will cover arbastro's reasonable losses from a claim that your plugin infringes someone's rights or that you broke these terms.

Questions about these terms, an appeal, or a report about a plugin that cannot wait for the in-app Report button: [email protected], arbastro Inc.