Module Developer Agreement

1. What a Module is, and how it comes to run

A module is software extending PDF Pro Panel 3 through its documented module interface: a plugin.json manifest and its accompanying files.

PDF Pro Panel 3 runs a module a user installs only where that user has approved it. Before installation the application shows them the module's name, version, stated author and the permissions it requests — each read from the module's own manifest — and they confirm. The application records a digest of every file in the module and rechecks it at each start; if anything in the module changes, it stops running until they approve it again.

There is no signing key, and we do not sign modules. We do not issue you a key, we do not hold one on your behalf, and nothing you distribute carries a signature from us.

Approval is the user's decision, not our review. We do not review, test, audit, certify or endorse any module we do not publish ourselves. The digest establishes only that a module has not changed since that user approved it; it establishes nothing about its origin, its authorship, or what it does.

You may say truthfully that your module is for or works with PDF Pro Panel 3. You may not call it certified, approved, verified, audited, signed, official, or endorsed by us, or use our name or marks in a way suggesting we wrote it, back it, or are responsible for it.

The install dialog is what most users will read about your module. Your name, description, author and permission list appear in it. They must be accurate and not misleading, and you must not request a permission you do not use.

2. Blocking

We can designate a module as blocked in any update to PDF Pro Panel 3, by its id and optionally by the digest of a particular build of it. A blocked module stops running for every user who has it, regardless of any approval they gave it and regardless of developer mode.

We will do this where a module is found to be harmful, deceptive, or in breach of section 3, and we may do it without notice where users need protecting first. Where we block a module for any other reason, we will tell you why.

Blocking by digest refuses one build. Blocking by id refuses every version, including any you publish later. Which we use depends on what the module did.

The application sends us nothing in order to apply this. The list forms part of each release, so a block takes effect as users update.

If you discover a security defect in a module of yours that is already in users' hands, tell us at security@pdfpropanel.com and publish a fixed version. If you cannot or will not fix it, say so, so that we can block the affected build.

3. What your module must and must not do

You warrant, for every module you submit or distribute, that it:

• Handles documents only as the user directed. It reads, writes, moves, copies or transmits only what the user gave to the tool they opened. PDF Pro Panel's promise to its users is that their documents do not leave their machine; your module is inside that promise, not an exception to it.
• Discloses any network use plainly, in its description, before it is installed.
• Collects no telemetry, analytics or personal information, and contains no advertising, tracking, cryptocurrency mining, or anything unrelated to what its description says it does.
• Requests only permissions it uses. Every one is shown to the user beside your module's name.
• Does not try to escape the module interface — another module's storage, the application's settings or licence state, the file system beyond what the user provided, or the application's internals other than through the documented context object.
• Is reviewable. It is distributed in the form it runs in; obfuscated, packed or minified code will not be listed by us. Provide source and reasonable assistance on request if a module of yours is reported to us.
• Is yours to distribute, infringes nobody's rights, and complies with the licences of any third-party or open-source components in it.
• Contains no malicious or deceptive code — no malware, backdoor, undisclosed remote control, or anything designed to mislead the user about what it is doing.
• Does not misrepresent authorship, origin or affiliation, including by imitating another module or product.
• Complies with applicable law, including data-protection law where it processes personal data, and export-control law.

4. Listing and removal

We may accept or decline any module for any marketplace we operate, at our discretion, and need not give a reason. We do not undertake to review any module; any review we do is limited, for our own purposes, and creates no duty to you or to any user.

We may delist or block any module at any time, without notice where it is or may be harmful to users. Where we do so for a reason other than a breach of section 3, we will tell you why. Blocking is described in section 2.

Keep your module working with supported versions of the application, and fix security defects promptly. If you stop maintaining a module, tell us so we can inform its users.

You support your own module. Do not send your users to our support channels; we will send users of your module to you.

5. Selling a module

You may charge for a module, including for a premium version of, or an extension to, a module we ship.

Selling directly: the sale is between you and the user. You set the price, take the payment, issue the receipt, handle tax, and honour refunds. We are not a party to it and do not process the payment.

Selling through a marketplace we operate: the revenue share, payment schedule, refund handling, taxes and reporting are those in the marketplace terms in force when your module is listed, which form part of this agreement for that module. We may change them on reasonable notice, effective from the next full payment period.

A module requiring an active PDF Pro Panel licence must say so in its description. Do not verify, circumvent, replicate or interfere with the application's licensing.

Do not sell a module that duplicates one we ship without adding real, described value, and do not present a paid module as necessary for the application to work.

If a module is blocked or delisted for a breach of section 3, refunds to its users are your responsibility.

6. Ownership

Your module is yours. This agreement transfers no ownership of it to us.

You grant us a non-exclusive, worldwide, royalty-free licence to do what distribution requires: reproduce it, host it, transmit it, and use its name, icon, description and screenshots to list, describe and promote it and the application. It lasts as long as we distribute your module, and afterwards only so far as needed for copies already distributed.

PDF Pro Panel 3, its name and its marks remain ours, and you gain no rights in them beyond the truthful statements permitted in section 1. You gain no rights in the application or its module interface.

7. Indemnity, warranties and liability

You will indemnify us against any claim, loss, liability, damage, fine or cost (including reasonable legal fees) arising from your module, from your breach of this agreement, or from any claim that your module infringes a third party's rights or has harmed a user or their data.

The module interface, the developer tools and any marketplace are provided "as is", without warranty of any kind. We do not warrant that the interface will stay unchanged, that any module will keep working across versions, that any marketplace will remain available, or that your module will earn anything.

We are not liable to you for lost profits, revenue, data or goodwill, business interruption, or any indirect, incidental, special, consequential or punitive damages. Our total aggregate liability to you is limited to the greater of the amounts payable by us to you under section 5 in the three months before the claim arose, and USD 100. Nothing here excludes liability that cannot lawfully be excluded.

8. Changes, term and termination

We may change this agreement. A material change is notified to the address you gave us and takes effect thirty days later; submitting or continuing to distribute a module after that date accepts it.

Either of us may terminate on written notice. We may terminate immediately, and block or delist your modules, for a breach of section 3.

On termination you stop distributing modules under this agreement and stop using our name and marks; we may delist your modules. Sections 1, 2, 3, 6, 7 and 9 survive. Amounts already earned remain payable, less refunds and any loss from a breach. Users who already installed your module keep whatever licence you granted them, and it continues to run for them unless it is blocked under section 2.

9. General

Governing law. This agreement is governed by the laws applicable to CCI Software Toolkits' principal place of business, without regard to conflict-of-law principles, and proceedings are brought exclusively in the courts of that jurisdiction. The United Nations Convention on Contracts for the International Sale of Goods does not apply.

Independence. We are independent parties: no partnership, joint venture, agency, franchise or employment is created, and you must not hold yourself out as our agent, representative or employee.

No exclusivity. Nothing here stops us developing, commissioning or distributing a module or feature that competes with yours.

Assignment. You may not assign this agreement without our written consent; we may assign it with a merger, acquisition or sale of assets.

Severability and entire agreement. An unenforceable provision is enforced as far as permissible and the rest stands. With any applicable marketplace terms, this is the entire agreement between us about modules.

Your own use of PDF Pro Panel 3 remains governed by its licence agreement. Where the two conflict about your activities as a developer, this one prevails.

10. Contact

• Module submissions: modules@pdfpropanel.com
• Security defects, including in a module of yours: security@pdfpropanel.com
• Everything else: support@pdfpropanel.com