Draft legal reference terms. The selected licence confirmation, invoice, proposal, or signed agreement will govern the specific engagement.
Schedule A & B
Landing Page Licence Terms
A1. Scope
This Schedule applies to landing pages developed, customized, configured, deployed, or managed by Naya.
A landing page is a single-page or landing-page-style digital asset designed for marketing, campaigns, launches, lead generation, communication, bookings, enquiries, or promotional conversion.
A2. Covered Landing Page Types
This Schedule may apply to:
| Landing Page Type | Examples |
|---|---|
| Campaign landing page | Meta ad landing page, Google ad destination page, launch campaign page |
| Real estate landing page | Project launch page, highstreet page, residential tower page, plotting project page, commercial project page |
| Lead-generation page | Callback form page, enquiry page, appointment booking page, WhatsApp lead page |
| Event page | Webinar page, event registration page, site-visit campaign page |
| Product or service page | Product launch page, service offer page, waitlist page |
| Offer page | Discount page, limited-time offer page, seasonal campaign page |
| Single-page microsite | Long-form page with multiple sections but one primary route |
| Static frontend page | HTML/CSS/JS/React/Next/Vite/Astro/Tailwind or similar frontend build |
| Builder/no-code page | Webflow, Framer, Wix, WordPress builder, Elementor, or similar tools where applicable |
| Tracking-enabled page | Pixel, analytics, GTM, UTM, event tracking, conversion scripts |
| Form-integrated page | CRM, webhook, Google Sheets, email, WhatsApp, or lead routing integration |
| Template-derived page | Naya template, third-party template, hybrid template, or reusable section-based implementation |
A3. Not Covered by Landing Page Licence
This Schedule does not cover:
| Asset | Reason |
|---|---|
| Multi-page website | Requires website licence |
| CMS website | Requires CMS/content model handover |
| Blog system | Requires website/CMS licence |
| Admin panel / Dashboard | Requires web app licence |
| CRM / Backend API / Database | Requires system licence / database export/migration scope |
| Automation workflow / n8n / Make / Zapier | Requires automation licence |
| AI agent | Requires automation/agent licence |
| VPS/server / Docker/CI/CD / Reverse proxy | Requires infrastructure handover |
| Template library / Design system | Requires template/framework licence |
| Multi-client reusable page builder | Requires commercial framework licence |
A4. Landing Page Licence Tiers
| Code | Name | Commercial Terms | Control Level |
|---|---|---|---|
| NLP-01 | Source Reference Licence | SOW-defined | Limited reference access snapshot |
| NLP-02 | Managed Handover Licence | SOW-defined | Project-specific operational control with Naya attribution retained |
| NLP-03 | Full Landing Page Control Licence | SOW-defined | Full project-specific control with attribution removal right |
A5. NLP-01 — Source Reference Licence
A5.1 Purpose
NLP-01 provides a limited source-code snapshot for internal reference, archive, and continuity purposes.
A5.2 Rights
| Right | Status |
|---|---|
| Source-code snapshot / Internal review & archival | Included |
| Project-specific reference | Included |
| Independent hosting / Third-party developer modification | Not included |
| Repository transfer / Naya attribution removal | Not included |
| Reuse for another project / Resale / Redistribution | Not allowed |
A5.3 Deliverables
| Deliverable | Included |
|---|---|
| ZIP source snapshot / Basic packaging & secret removal | Yes |
| Short source note | Yes |
.env.example / Build instructions / Repository access | No |
A5.4 Timeline
Standard delivery timeline: 3–5 business days after full payment and asset identification.
A6. NLP-02 — Managed Handover Licence
A6.1 Purpose
NLP-02 provides controlled project-specific handover for the same landing page while preserving Naya attribution and Naya’s reusable IP rights.
A6.2 Rights
| Right | Status |
|---|---|
| Clean project-specific source code | Included |
| Independent hosting & modification for same project | Included |
| Third-party developer maintenance | Included, limited to same landing page |
| Repository access | Available where suitable |
| Naya attribution removal | Not included |
A6.3 Deliverables
| Deliverable | Included |
|---|---|
| Clean code package & Security cleanup | Yes |
.env.example, README & basic deployment notes | Yes |
| One handover call | Yes, up to 30 minutes |
| Attribution removal / Live migration / Ongoing support | No |
A6.4 Timeline
Standard delivery timeline: 5–7 business days after full payment, asset identification, and delivery details.
A7. NLP-03 — Full Landing Page Control Licence
A7.1 Purpose
NLP-03 provides full project-specific operational control of the identified landing page.
This includes source-code handover, self-hosting rights, modification rights, third-party maintenance rights, and visible Naya attribution removal rights.
A7.2 Rights
| Right | Status |
|---|---|
| Clean project-specific source code & self-hosting | Included |
| Modification for same project/business purpose | Included |
| Third-party developer or agency maintenance | Included |
| Visible Naya attribution removal | Included |
| Clean repository transfer | Available where suitable |
| Original repository transfer | Only where approved and safe |
| Reuse for other projects / Resale / Re-licensing | Not allowed |
A7.3 Deliverables
| Deliverable | Included |
|---|---|
| Full project-specific code package with Squashed Git Copy | Yes |
Code audit, security cleanup & .env.example | Yes |
| Build/run documentation & detailed deployment notes | Yes |
| Handover checklist, security cleanup note & 3rd-party notices | Yes |
| One comprehensive handover call | Yes, up to 45 minutes |
| Final formal Licence Confirmation | Yes |
| Live hosting migration / Future support / Feature upgrades | No |
A7.4 Timeline
Standard delivery timeline: 7–10 business days after full payment, asset identification, delivery method confirmation, repository destination, attribution choice, and technical contact details.
A8. Meaning of Full Landing Page Control
Full Landing Page Control means the Client may independently operate the identified landing page.
It includes:
| Control Area | Meaning |
|---|---|
| Source control | Client receives the project-specific source package |
| Hosting control | Client may host the page independently |
| Modification control | Client may modify the page for the same project/business purpose |
| Vendor control | Client may appoint another developer/agency for maintenance |
| Attribution control | Client may remove visible Naya attribution |
| Continuity control | Page may operate after Naya-managed hosting ends |
It does not include:
- ownership of Naya’s reusable frameworks;
- right to reuse the code for unrelated projects;
- right to resell the source code;
- right to sublicense the source code;
- right to publish the source code publicly;
- access to Naya VPS or infrastructure;
- access to Naya internal tools;
- access to Naya deployment workflows;
- access to Naya template library;
- access to unrelated code or clients;
- free future support;
- legal or compliance certification.
A9. Landing Page Handover Comparison
| Feature | NLP-01 | NLP-02 | NLP-03 |
|---|---|---|---|
| Source snapshot | Yes | Yes | Yes |
| Security cleanup | Basic | Yes | Yes |
| Environment reference | No | Yes | Yes |
| Build/run instructions & Deployment notes | No | Basic | Yes |
| Independent hosting right | No | Yes | Yes |
| Third-party developer maintenance | No | Limited | Yes |
| Modify same landing page | No | Yes | Yes |
| Remove visible Naya attribution | No | No | Yes |
| Repository access | No | Available | Available |
| Repository transfer | No | No by default | Available |
| Original repo transfer | No | No | Only if approved |
| Reuse for other projects / Resell | No | No | No |
| Live migration / Ongoing support | No | No | No |
| Commercial Terms | SOW-defined | SOW-defined | SOW-defined |
A10. Licence Confirmation Format
Every landing page licence should be confirmed using the following structure:
| Field | Value |
|---|---|
| Licence Code | NLP-[01/02/03] |
| Licence Name | [Selected Licence Name] |
| Covered Asset | [Landing Page Name] |
| Client | [Client Name] |
| Original Project / Campaign | [Project Name] |
| Delivery Method | ZIP / Repo Access / Clean Repo Transfer / Platform Export / Workspace Transfer |
| Attribution Rule | Retained / Removable |
| Commercial Terms | [Signed SOW / quote reference] |
| Payment Status | Paid / Pending |
| Delivery Timeline | [X] business days |
| Support Included | Yes / No |
| Effective Date | [Date] |
| Special Conditions | [If any] |
Only the asset listed in the licence confirmation is covered.
A11. Landing Page Licence Reservation
A landing page licence is not a website licence, web app licence, automation licence, template licence, infrastructure licence, data export licence, or full copyright assignment.
All rights not expressly granted remain reserved by Naya.
Schedule B — Future Licence Categories
Naya may issue additional schedules for other digital asset categories.
| Code Prefix | Category | Applies To |
|---|---|---|
| NLP | Landing Page Licence | Single-page campaign and lead-generation pages |
| NWS | Website Licence | Multi-page websites, CMS websites, structured brand websites |
| NWA | Web App Licence | Dashboards, portals, apps, login systems, admin panels |
| NAU | Automation Licence | Automations, workflows, integrations, n8n, Make, Zapier, AI agents |
| NIH | Infrastructure Handover Licence | VPS, Docker, CI/CD, deployment, DNS, hosting, reverse proxy |
| NTF | Template / Framework Licence | Reusable templates, page systems, section libraries, design systems |
| NDS | Data Export Licence | Leads, CRM records, submissions, analytics exports, logs |
A licence under one category does not grant rights under another category unless expressly stated.