Licence Terms for Custom Code & Connectors
Last updated: 14 September 2025
These Licence Terms apply to custom code, connectors, scripts, and configuration we deliver. They sit with our MSA, DPA, and your SoW. If there is a conflict, the SoW overrides these terms for that project.
- You get a perpetual, non-exclusive licence to use Deliverables in your business.
- We keep ownership of our pre-existing IP and shared libraries.
- Open-source parts stay under their own licences.
- Support and updates are separate services unless the SoW includes them.
- Deliverables: workflows, code, connectors, scripts, configurations, and docs we create for you.
- Libraries: our reusable modules, snippets, and templates used across clients.
- Third-party software: open-source or commercial software from others.
- On full payment we grant you a worldwide, perpetual, non-exclusive, non-transferable licence to use the Deliverables for your internal business.
- You may modify Deliverables for your use. You must keep our copyright notices in source files.
- You may run Deliverables in your own or third-party environments.
- No resale, sublicensing, or providing Deliverables as a service to unrelated third parties, unless we agree in writing.
- Do not publish Libraries or share them outside your group companies.
- Security keys and credentials must not be hard-coded in public repos.
- Your data and your pre-existing IP stay yours.
- We own Libraries and our pre-existing IP. We may reuse generic know-how across clients.
- If a Deliverable includes Libraries, you receive a licence to use them only with that Deliverable.
- We may use open-source components (e.g., npm packages). Those remain under their original licences.
- If an open-source licence requires attribution or disclosure, we will note it in the repo or docs.
- We deliver by Git repo, export file, or platform handover (e.g., n8n JSON).
- We can host a private repo or push to yours. Admin access is removed on exit.
- We keep a secure archive for 30–90 days unless the SoW says otherwise.
- Platform changes (APIs, rate limits, node updates) can break things. Ongoing updates are not included unless your SoW or SLA covers them.
- Bug fixes after handover follow the SoW. Otherwise they are chargeable.
- We recommend pinned versions and a test environment before upgrades.
- By default you receive all project source needed to run and modify Deliverables.
- If you require code escrow, we can add an escrow arrangement at your cost.
- Deliverables may depend on services like OpenAI API, Twilio, Stripe, Google, Xero, or WordPress.
- You are responsible for those accounts, fees, and their terms.
- We are not liable for outages or changes in third-party services.
- We design with least privilege, separate secrets, and encryption in transit.
- You must run Deliverables in a secure environment and review access regularly.
- Where personal data is processed, our DPA applies.
- We warrant we have the right to grant the licence.
- Deliverables are provided with reasonable skill and care per the MSA.
- We do not warrant uninterrupted operation or compatibility with all setups.
- Liability limits and exclusions are as set out in the MSA.
- Nothing limits liability for fraud or for death or personal injury caused by negligence.
- These terms end if the MSA ends. Your licence continues for Deliverables already paid for.
- If you materially breach these terms and do not fix within 14 days, we may end the licence to Libraries. Your licence to project-specific Deliverables remains.
English law applies. The courts of England and Wales have exclusive jurisdiction.
Technophobia Ltd · Company No. 14898332 · VAT GB 495 7043 58
13B Devonshire Road Industrial Estate, Millom, LA18 4JS, United Kingdom
+44 1229 774591 • hello@technophobia.uk
