SERVICE AGREEMENT / WEBSITE TERMS
Clear terms.
Defined deliverables.
Our project framework covers scope, ownership, source files, licences, handover, maintenance and responsibilities across all seven services.
Version 1.0 — 6 November 2026
1. Your agreement and scope
Icon Global Digital is the trading brand used on this website. The written statement of work (SOW) must identify the legal supplier, the client, their authorised representatives and contact details. These service terms apply only when expressly incorporated into a proposal or agreement accepted by both parties. Viewing this website, choosing a package or sending an enquiry does not itself purchase a service or accept a project contract.
The agreed SOW must specify deliverables, quantity limits, platforms, file formats, integrations, revision allowances, fees, billing frequency, payment dates, support period, responsibilities and acceptance criteria. A published package is a scope reference, not an unlimited-service commitment. Unless expressly agreed otherwise, work is for one client business and one defined project or brand.
Mandatory law takes priority. Next comes the signed agreement and any expressly agreed variations, then the applicable service schedule below, then these general terms. A specific written departure must identify the term it changes. Existing contracts are not amended by a website update; the version incorporated at acceptance continues to apply unless both parties agree to a change.
2. Fees, licences and third-party costs
The SOW confirms currency, whether charges are one-time, recurring, time-based or usage-based, any minimum term, taxes, deposits and milestones. No payment frequency or indefinite support entitlement is implied by a headline package price. Deposits are credited to the agreed work; fees for approved completed work and disclosed non-cancellable commitments become earned as incurred.
Domains, hosting, paid themes, fonts, stock media, plugins, app store accounts, payment processing, ad spend, SMS, WhatsApp, AI usage, automation subscriptions and other supplier charges are excluded unless expressly included. Any spending authority and limit must be approved in writing. Provider charges and licence restrictions must be disclosed before purchase where relevant to the delivery.
Clients should purchase ongoing accounts in their own legal name where practicable. Agency subscriptions, seats or partner licences do not automatically transfer. Renewals, price changes and licence replacement after handover are the client’s responsibility unless a current support agreement assigns them to us.
Invoice due dates are those agreed in writing; no default late fee or interest is imposed by this page. The client should notify us promptly of a disputed amount, and both parties will investigate it in good faith. Undisputed amounts remain payable. Suspension for non-payment requires written notice and at least ten business days to resolve the overdue amount, except where an immediate legal or security issue requires action.
3. Delivery, revisions and changes
The delivery schedule begins when the agreed initial payment, approved brief, required content and necessary access are available. Client approvals, third-party reviews, store approvals, supplier outages and changes in scope can affect dates. We will communicate material delays and agree a revised plan; a launch date is binding only if the SOW expressly makes it so.
One revision round means one consolidated set of feedback against the approved brief. A new direction, new page or screen, additional integration, replacement of approved content or reversal of an approved decision is a scope change. We will confirm the fee and schedule impact in writing before undertaking additional work.
Where a package includes unlimited revisions for a specified period, that allowance covers revisions to the same agreed deliverable during that period. It does not include unlimited new concepts, parallel projects, new features or guaranteed turnaround times. Any monthly or quarterly allowance operates only during the funded support term; unused capacity does not carry forward unless agreed.
4. Review and acceptance
We will identify the deliverables submitted for review and the agreed acceptance criteria. Unless the SOW sets a different review period, the client has ten business days to accept them in writing or provide a consolidated list of material failures against that scope. We will correct in-scope non-conformities and resubmit them for review.
Silence alone is not acceptance. If feedback is delayed, we may pause the schedule and agree a restart date. A minor issue that does not prevent the agreed use may be recorded on a written completion list rather than blocking a mutually approved launch. Going live requires client authorisation and does not remove rights concerning undisclosed defects or mandatory legal protections.
5. Ownership, source code and working files
Client-provided materials remain the client’s property. For original bespoke deliverables created specifically under a build or design SOW, the agreed commercial position is that transferable economic rights pass to the client after full payment for those deliverables. The written agreement must record that allocation, any exclusions and any further assignment documents required by law. During development, review access is provided for evaluation. Moral rights and non-transferable rights remain subject to applicable law.
For a bespoke website, mobile app or automation build, handover includes the client-specific source code or workflow export, necessary build/deployment instructions and a dependency or licence list where these exist and can legally be delivered. The SOW identifies the repository, export format and delivery milestone. A subscription, hosted platform, template configuration or SaaS service does not imply access to the platform vendor’s source code or ownership of its software.
Pre-existing tools, reusable libraries, generic methods and agency background materials must be identified as exclusions before incorporation. Unless the SOW provides broader rights, the client receives a perpetual, non-exclusive licence to use, copy, maintain and modify any agency-owned background material embedded in the paid deliverable, including through a replacement maintainer, to the extent necessary to use that deliverable. This does not authorise selling that background material separately. Open-source and third-party components remain under their own licences.
Only the approved final design and the working-file formats listed in the package or SOW are included. Rejected concepts, unused alternatives, internal research, raw production footage and internal tools are excluded unless purchased separately. A promise of editable source files in a selected package remains binding within the agreed scope; this clause does not remove it.
We will identify material licence restrictions, attribution requirements and relevant open-source obligations. We will not represent third-party assets as exclusively owned by the client. The client must hold the licences needed for its own editing, deployment and distribution. Stock assets and AI-assisted outputs may not be exclusive or suitable for trademark registration; rights and permitted use require review for the intended application.
6. Handover, accounts and portability
The handover checklist identifies the final files, source or platform export, repository access, client-owned account administration, deployment instructions, configuration variable names, dependency licences, agreed data export and training. Secrets are transferred securely, not committed to source code. Agency-wide credentials and other clients’ information are never included.
Domains, stores, advertising accounts, analytics properties and app store accounts should be client-owned where the provider allows. We use delegated access where possible. Provider transfer rules, account verification and export limitations must be explained before selection. We do not promise a complete export from a platform that does not support one.
We will not use hidden disabling code or withhold access to pre-existing client-owned accounts or client-provided data as security for a fee dispute. Payment conditions for new deliverables do not transfer ownership of existing client assets to us. Additional migration, training or transition assistance beyond the agreed handover may be quoted separately.
7. Defects, maintenance and support
Unless a longer period is included in the SOW or selected package, bespoke website, ecommerce, mobile app and workflow builds include a thirty-calendar-day defect correction period from written acceptance or client-authorised production launch, whichever occurs first. A covered defect is a reproducible failure of our delivered work to meet the agreed specification in the supported environment. This is a contractual support allowance, not a restriction of rights that cannot lawfully be limited.
New features, content changes, redesigns, third-party outages, provider policy changes, expired licences, unsupported devices and changes made by another party are not covered defect work unless our own failure caused the issue. We will assess the cause fairly; unrelated third-party edits do not automatically void all support. Issues must be reported with steps to reproduce and relevant access.
Maintenance is a separate service unless included for a stated duration. Its schedule must identify updates, backups, restore testing, monitoring, security patching, supported versions, included hours, response targets, escalation and exclusions. Monthly marketing or SEO deliverables are ongoing service work, not a permanent software warranty.
Support is through the agreed email or ticket channel during the business hours and timezone recorded in the SOW. Priority support means queue priority unless an explicit response time is agreed. No 24/7 availability, uptime percentage, recovery objective or guaranteed resolution time exists without a specific service-level agreement. Response time is distinct from resolution time.
The party responsible for hosting must maintain backups and agreed access controls. A backup schedule, retention period and recovery responsibilities must be documented before launch. Where backups are not included, the client must arrange them. After maintenance ends, updates and renewals are not performed automatically; we will explain known expiry and handover requirements.
8. Client responsibilities and approvals
The client appoints an authorised decision-maker, supplies accurate content and lawful assets, obtains required permissions, provides timely consolidated feedback and maintains necessary subscriptions. The client approves business claims, prices, translations, policies, product information and regulated statements before publication. We remain responsible for performing the agreed professional work with reasonable care and skill.
Legal advice, tax advice, accessibility certification, penetration testing, regulatory certification and trademark clearance are not included unless expressly commissioned. The SOW must still identify any agreed accessibility, security, browser/device or compliance requirements; an exclusion does not excuse failure to meet those agreed requirements or mandatory law.
No party may supply unlawful material, infringe others’ rights, access systems without authority or instruct deceptive practices. We may refuse the affected instruction, explain the issue and agree a lawful alternative. Unaffected work and existing client assets will be handled fairly.
9. Confidentiality, personal data and AI tools
Each party protects the other’s non-public information, uses it only for the agreed work and restricts access to people who need it and are bound by suitable duties. Exceptions cover information already lawfully known, independently developed, publicly available without breach or lawfully obtained elsewhere. Required legal disclosures are limited to what is necessary, with notice where permitted. These duties survive the project; trade secrets remain protected while confidential.
Where we process personal data on the client’s instructions, the parties must agree a data-processing schedule before access. It records roles, purposes, data categories, permitted instructions, retention, security measures, subprocessors, locations/transfers, incident contacts, assistance and return/deletion arrangements. Each party must meet the legal duties that apply to its role and are in force for that processing; the contract is not a substitute for those duties.
We will not place client confidential information or personal data into public AI tools, or authorise its use for model training, without the client’s informed written approval and suitable provider/data terms. Approved AI use still requires human review for accuracy, rights and confidentiality. No AI output is guaranteed to be accurate, exclusive or free of third-party claims.
Both parties use proportionate safeguards, least-privilege access and secure credential handling. A suspected incident affecting project data must be reported to the designated contact without undue delay, with cooperation on containment, investigation and any legally required notifications. No system is promised to be risk-free.
At completion or termination, project personal data must be returned or deleted under the agreed schedule, subject to lawful retention requirements. Retained backups remain protected and expire through the documented cycle. The client’s original data and accounts are not payment collateral.
10. Third-party systems and results
Search engines, social networks, advertising systems, app stores, payment providers and hosting platforms make their own eligibility, review and availability decisions. We will perform the agreed work and address our own errors, but cannot guarantee rankings, AI citations, traffic, leads, revenue, ad approval, store approval or uninterrupted third-party operation.
Changes imposed by a provider after scope approval may require a change request. Paid platform costs and service terms remain subject to the provider. We will notify the client of a material dependency affecting delivery or use rather than silently substituting a materially different solution.
11. Pauses, cancellation and termination
Either party may terminate for a material breach that remains unresolved fourteen calendar days after written notice describing the issue, unless mandatory law or an urgent security/legal risk requires another approach. For an ongoing service without a different agreed minimum term, either party may cancel on thirty calendar days’ written notice. There is no automatic fixed-term renewal unless expressly agreed.
A fixed-scope project may be ended by written notice. The client pays for properly completed work up to termination and previously approved, disclosed non-cancellable third-party commitments; an itemised reconciliation is provided. Any unearned prepaid balance is refunded after that reconciliation. No blanket “all deposits are non-refundable” rule applies.
If delivery fails because of our uncured material breach, the parties will reconcile undelivered work, available remedies and a fair refund, subject to mandatory rights. Fee disputes do not prevent return of client-owned accounts or client-provided data. Paid-for completed deliverables are handed over in their current state, with known limitations identified.
A pause caused by missing access, approvals or content does not silently consume a complete project fee. The parties will record completed work, committed costs and a revised schedule. Archiving or restart charges require prior written agreement. Transition work outside the included handover is separately scoped.
12. Responsibility, remedies and liability
Each party is responsible for losses caused by its own breach, negligence or unlawful conduct, subject to applicable law. The parties must take reasonable steps to reduce avoidable losses. Where a third-party rights claim concerns supplied material or delivered work, the receiving party must notify the other promptly and allow reasonable cooperation; settlements affecting the other party require its consent.
If these terms are incorporated without a different express liability provision, each party’s aggregate contractual liability relating to a fixed-scope SOW is limited to the fees paid or payable under that SOW. For a recurring SOW, the proposed cap is the fees paid or payable for that service during the twelve months preceding the event giving rise to the claim. To the extent lawful, neither party is liable for indirect or consequential losses; ordinary direct loss is not excluded merely because it involves data or remediation.
Those limits do not restrict fraud, wilful misconduct, unpaid agreed fees, or any liability, remedy or consumer protection that cannot lawfully be excluded or limited. They do not grant permission to misuse intellectual property or confidential information. Any insurance, enhanced security exposure, indemnity or different cap must be expressly negotiated in the signed agreement.
13. Events beyond control, law and disputes
A party affected by an event genuinely beyond its reasonable control must notify the other, explain the effect, mitigate it and agree a revised plan. This does not excuse fees for work already properly completed. If the event prevents delivery for more than thirty calendar days, either party may end the affected work and reconcile unearned fees and handover.
Unless the signed agreement provides otherwise, the proposed governing law is Sri Lankan law, subject to mandatory protections that apply to the engagement. The parties first refer a dispute to their authorised representatives for a good-faith discussion for thirty calendar days after notice. Mediation may follow by agreement. Failing resolution, a competent court with lawful jurisdiction may hear the matter. No compulsory arbitration or foreign forum is imposed by this page.
Formal notices go to the addresses identified in the SOW. Acceptance and variations must be recorded by authorised representatives in a signed document or another legally valid recorded form agreed by the parties. If a provision is unenforceable, the remaining lawful provisions continue, and the parties seek a lawful replacement consistent with the original purpose.
14. Website use and project publicity
Website content is general information and may change. It is not a binding quotation or a guarantee of availability. Client and third-party names and assets remain subject to their owners’ rights. You may not misuse the website, attempt unauthorised access or copy protected material beyond a lawful permission. External sites operate under their own terms.
We may identify a client or publish project screenshots, testimonials, performance results or case studies only with written permission covering the material and timing. No confidential information, personal data, unlaunched work or invented performance claim may be used for promotion. The client may request correction of inaccurate attributed statements.
Service schedules
Each schedule supplements the general terms. Quantity limits and paid inclusions come from your selected package and agreed statement of work. A specific promise in the accepted SOW takes priority over a general exclusion.
SERVICE SCHEDULE
Brand & Creative
Deliverables and acceptance
The SOW lists logo concepts, revision rounds, approved identity elements, colour references, typography, guidelines, stationery and any social or campaign templates. Print sizes, languages and variants are counted individually unless agreed otherwise.
Only approved final designs are production deliverables. Launch, Growth and Iconic package concept/revision allowances remain as listed; unlimited revisions within the first month do not include unlimited new design directions.
Source files, ownership and handover
Supply the promised final PNG/JPG/PDF exports. Supply AI/PSD or other native editable files where the chosen package or SOW includes them; a flattened PDF is not a substitute for promised editable files.
Identify font and stock licences, colour profiles and printer specifications. Client-specific final artwork rights follow the ownership clause. Font software, stock media, rejected concepts and unrelated production tools do not become exclusive client property.
Maintenance and support
Quarterly minor edits, monthly visual support and seasonal adaptations apply only for the agreed funded term. Record the number of items, turnaround and what counts as a minor change.
Correct our export/specification errors against the approved artwork. New copy, concepts, formats, product variants and print reruns are separately scoped. Obtain an approved proof before production.
Client responsibilities and exclusions
The client checks spelling, contact details, translations, measurements and final proofs. Naming, trademark searches/registration and legal clearance require a separate engagement.
Printing, fabrication, photography, raw footage, paid font licences and production colour matching are excluded unless listed. Screen and print colour variation is expected; responsibility for an actual specification error remains with the party causing it.
SERVICE SCHEDULE
Digital Growth
Deliverables and acceptance
The SOW fixes platforms, post and email quantities, formats, content calendar, approval deadlines, community-response limits, campaign work and reports for each service period.
Ad strategy, creative production, publishing and active ad account management are distinct deliverables. A package offering creative/strategy assistance does not automatically include daily paid campaign management.
Source files, ownership and handover
Client-owned social, ad, email and analytics accounts remain accessible to the client. Handover covers approved final creatives, copy, reports and campaign configuration exports supported by the provider.
Native creative files, raw footage, agency research tools and reusable templates are included only where listed. Audience portability and tracking history are subject to platform rules and lawful data use.
Maintenance and support
Retainers cover the agreed recurring production and optimisation work, not unlimited requests. Confirm service dates, reporting cadence, meeting limits, revision allowance and cancellation/minimum-term rules.
The client must approve a publishing calendar and any delegated spend authority. Work can be held where approval is missing; crisis response, after-hours moderation and urgent shoots require an explicit arrangement.
Client responsibilities and exclusions
Ad spend, influencer fees, shoots, travel, stock media, CRM/email subscriptions and platform usage fees are separate unless included. Client approval is required before increasing budgets.
The client is responsible for truthful offers, required customer permissions and lawful audience lists. No purchased follower, spam or deceptive review service is included. Results depend on budget, offer, market and platform decisions.
SERVICE SCHEDULE
Growth Automation
Deliverables and acceptance
Specify each workflow’s trigger, actions, connected systems, approval gates, run volume, error behaviour and acceptance test. Two workflows in Lite and five or more in Growth refer to the workflows agreed in scope, not unlimited integrations.
AI agents, custom models, historical data cleanup, legacy-system integrations and complex orchestration are separate unless listed. The advanced tier is custom quoted.
Source files, ownership and handover
For bespoke builds, provide client-specific scripts or supported workflow exports, configuration instructions, connection/dependency list, runbook and agreed test cases. Transfer client-owned workspace administration where possible.
Provider engines, SaaS source code, model weights and agency background modules remain under their own rights. Document any non-exportable component and continuing licence before selection. Rotate or securely transfer credentials.
Maintenance and support
The build defect period covers failures against the agreed workflow tests. Continuing monitoring, failed-run response, API changes, prompt tuning and monthly flow optimisation require the documented support term.
Agree monitoring hours, alert recipients, retry limits and a manual fallback. A workflow should not make payments, publish content or take other consequential action without the authorised controls defined in scope.
Client responsibilities and exclusions
The client supplies authorised API access and suitable test data, approves business rules and controls production permissions. The data-processing schedule governs personal data.
Automation licences, hosting, CRM, AI tokens, WhatsApp/SMS and provider usage are separate unless included. Provider limits, unavailable APIs and unreliable input data may require scope changes; automated output requires the agreed human oversight.
SERVICE SCHEDULE
AI Search & SEO
Deliverables and acceptance
Define the audited domain, page count, keyword/topic coverage, technical implementation allowance, local locations, content quantities and reporting period. Separate recommendations from fixes we are authorised to implement.
SEO and GEO content tiers are separate scopes unless bundled in the SOW. AEO covers the customer questions and answer content expressly agreed. A monthly content allowance applies only during the agreed service term.
Source files, ownership and handover
Provide the agreed audit, keyword/topic map, approved articles, technical change log and reports. Client-owned Search Console, Business Profile and analytics properties stay under client administration.
Approved original content follows the ownership clause. Paid research datasets, tool accounts, internal prompts and uncommissioned drafts are not automatically transferred. AI-assisted drafts require human editorial and factual review.
Maintenance and support
Recurring work includes only the agreed publishing, optimisation, reporting and meeting allowance. An initial audit or setup is not perpetual SEO maintenance.
Major code fixes, redesign, translations, migrations and new locations require a separate scope unless expressly included. Search engines control recrawling, indexing and presentation timelines.
Client responsibilities and exclusions
The client verifies expertise claims, local business details, reviews, regulated statements and source material, and supplies access needed for implementation. We must not invent offices, reviews or results.
No ranking, traffic, backlink count, rich result or AI citation is guaranteed. Paid link schemes and bulk deceptive content are excluded. Third-party tool subscriptions and content beyond the allowance are separately quoted.
SERVICE SCHEDULE
Smart Ecommerce
Deliverables and acceptance
Specify the platform, theme/custom design, initial product count, variants, categories, payment path, shipping zones, tax configuration, checkout, transactional emails and included integrations. Initial uploads are not unlimited catalogue management.
Acceptance tests should cover an agreed test order, payment success/failure, shipping/tax calculation, stock behaviour, refunds where supported and admin handover. Data migration needs its own mapping and validation plan.
Source files, ownership and handover
The client receives store administration and agreed configuration/product exports. Bespoke storefront/backend source is delivered where commissioned and legally transferable; Shopify or other platform software is not sold as client-owned source.
List theme/plugin/app licences, renewal costs and export limits. Client-owned payment and courier accounts remain in the client’s legal name. Platform checkout restrictions and merchant eligibility are confirmed before committing to a solution.
Maintenance and support
The build defect period covers the delivered agreed store behaviour. Patches, backups, product changes, merchandising, abandoned-cart flows and ongoing integrations require a stated maintenance/marketing scope.
Agree responsibility for fulfilment, refunds, stock accuracy, fraud checks, backups and recovery. Site support does not mean managing the client’s warehouse or customer service unless separately contracted.
Client responsibilities and exclusions
The client supplies lawful product information, images, prices, tax instructions, delivery/return policies and merchant approvals. Provider approval and settlement decisions cannot be guaranteed.
Platform fees, processing charges, courier fees, paid apps/themes, photography, subscriptions, tax/legal advice and additional uploads are excluded unless listed. Do not provide raw card data to the agency; use the approved payment provider flow.
SERVICE SCHEDULE
Websites
Deliverables and acceptance
The SOW lists pages and templates, CMS fields, responsive layouts, forms, integrations, content responsibilities, supported browsers and any agreed accessibility/performance targets. Package page limits do not imply unlimited templates, languages or custom applications.
Acceptance checks include the agreed navigation, mobile layout, form delivery, CMS editing, links and production configuration. A visual mockup approval is separate from acceptance of the implemented website.
Source files, ownership and handover
For a bespoke coded website, provide the paid client-specific repository/source, dependency list, build/deployment instructions and required configuration names. For a CMS/theme or hosted builder, provide administration, client-specific changes and available exports.
Domains and hosting accounts should be client-owned. Proprietary platform engines and non-transferable agency licences are excluded from ownership; any replacement licence and portability constraint must be disclosed before selection.
Maintenance and support
After the included build defect period, updates, backups, monitoring, security patches, form/email troubleshooting and content changes require the agreed maintenance scope.
Record the duration of monthly backups and one/two-hour editing allowances in the chosen plan. New features, redesigns, major framework upgrades and migrations are not ordinary content edits.
Client responsibilities and exclusions
The client supplies approved copy/assets and DNS/email/hosting access, designates reviewers and approves production launch. Data collection, cookies and analytics require an agreed implementation and appropriate notices.
Domain/hosting renewals, paid plugins, email services, translation, copywriting, photography, legal policies and certification are separate unless included. Reasonable testing does not promise zero vulnerabilities or automatic statutory certification.
SERVICE SCHEDULE
Mobile App
Deliverables and acceptance
Define screen count, iOS/Android coverage, framework, supported OS/devices, backend/admin functions, authentication, notifications, offline behaviour, integrations and store submission work. Starter, Business and Pro allowances remain limited to the agreed three/eight/fifteen-screen scope.
Identify whether a screen means a distinct layout or functional flow and how variants count. Admin panels, custom APIs and real-time features are included only if listed; optional items are not automatically bundled.
Source files, ownership and handover
For a bespoke app build, provide the paid client-specific repository, build instructions, dependency/licence list, agreed backend source and reproducible configuration. Transfer or securely manage client-owned signing credentials and developer accounts.
App binaries alone do not replace promised source code. Third-party SDKs, proprietary services and platform software retain their licences. Identify store-account transfer and signing limitations before development.
Maintenance and support
The selected package’s longer stated support period takes priority over the general thirty-day build default. State its start date, coverage and the precise cadence intended by ambiguous wording such as “bi-monthly”.
OS upgrades, new devices, SDK/policy changes, store resubmissions, new features and ongoing backend operation require explicit maintenance coverage. A submission service does not guarantee approval or permanent store availability.
Client responsibilities and exclusions
The client provides verified developer accounts, lawful privacy disclosures, test users and required merchant/API approvals. Review permissions and data collection before submission.
Store memberships, hosting, databases, maps, OTP/SMS, processing and external APIs are separate unless included. Agree production monitoring, backups and emergency contacts; no 24/7 incident response is implied by “priority support”.
Questions before signing?
Ask us to clarify any deliverable, licence, support allowance or legal party before accepting a proposal. Contact [email protected] or send a project enquiry. See our privacy information for website enquiry handling.