Extension Store — Developer Terms
Everything you need to know before publishing an extension for ENCY.
These documents govern how extensions are submitted, reviewed, distributed and supported on the ENCY Extension Store. They are published in full and are available to read before you register — you do not need an account.
The documents
Developer Agreement
Version 1.0 · effective 1 November 2026
The contract between you and ENCY SOFTWARE LTD. Covers intellectual property, warranties, liability, fees, termination and governing law.
Publishing Policy
Version 1.0 · effective 1 November 2026
The rules your extension must meet. Content requirements, the review process, how enforcement decisions are made, ranking, and how we treat our own products differently.
Schedule A — Reserved Functionality
Version 1.0 · effective 1 November 2026
The list of capabilities that ENCY licenses to end users under a separate entitlement, and which ENCY licence unlocks each one. Read this before you start building.
Schedule B — Technical Requirements
Version 1.0 · effective 1 November 2026
SDK usage, packaging, code signing, security, and how to call the entitlement-verification API.
Schedule C — Enforcement and Appeals
Version 1.0 · effective 1 November 2026
How we take, communicate and review decisions to refuse, restrict or remove an extension — and how you appeal.
Commercial Terms
Version 1.0 · effective 1 November 2026
Commission, pricing, settlement, refunds and taxes.
SDK Licence Terms
Version 1.0 · effective 1 November 2026
The terms on which the ENCY SDK is made available.
Trade Mark Guidelines
Version 1.0 · effective 1 November 2026
How to refer to ENCY and its products in your extension name, listing and documentation.
Standard Extension EULA
Version 1.0 · effective 1 November 2026
Default end-user terms, applying only where a developer does not supply its own.
Start here
Can I build what I have in mind? Check Schedule A first. Most extension ideas are outside it entirely — integrations, post-processors, tool libraries, automation, reporting and file translation are all open with no conditions attached.
My extension overlaps with something ENCY sells separately. That is allowed. It is published as a gated extension: it checks that the user holds the matching ENCY licence before it runs. Your extension is then sold in addition to that licence, not instead of it. See Publishing Policy §4.3.
I am not sure which side of the line I am on. Ask before you build. Send us a description and we will give you a written determination within 20 business days. It binds us for 24 months. See Publishing Policy §4.6.
Something has gone wrong and I disagree with a decision. Every decision comes with written reasons and a right of appeal, reviewed by someone not involved in the original decision. Write to [email protected] within 30 days.
What changes, and how much notice you get
| Document | Notice before a change takes effect |
|---|---|
| Developer Agreement | 15 days |
| Publishing Policy | 15 days |
| Schedule A — clarifications and renaming | 15 days |
| Schedule A — reserving a new capability | 30 days |
| Schedule B | 15 days |
| Commercial Terms — commission changes | 60 days |
Changes are never applied retroactively. We notify you by email and in the Developer Portal. Where a change is material, you will be asked to accept the new version before submitting again.
Every previous version stays published. See the changelog.
Contact
| Publishing, submissions, general questions | [email protected] |
| Appeals and complaints | [email protected] |
| Security and vulnerability reports | [email protected] |
ENCY SOFTWARE LTD 9 Aiolou and Panagioti Diomidous, Katholiki, 3020 Limassol, Cyprus Registration No. HE 460544 · VAT No. CY 60079628L +357 95 907793