Skip to content
Legal & Service Terms

Terms of Service

These terms explain the general rules for using the NUSTFORGE website, sending project inquiries, receiving estimates, agreeing project scope, making payments, and working with us on software projects.

Last updated

May 31, 2026

What it covers

Scope, payments, delivery and support

Applies to

Website use and project work

Read our Privacy Policy
On this page

Terms overview

These general website terms work alongside any accepted proposal, statement of work, invoice, contract, or project-specific agreement between NUSTFORGE and a client.

1. Scope and acceptance of these terms

These Terms of Service apply when you visit https://www.nustforge.com, use the NUSTFORGE website, submit a project inquiry, request an estimate or consultation, or communicate with us about potential services.

By using the website, you agree to follow the website-use provisions of these terms. A project inquiry, conversation, estimate, or consultation does not by itself create a binding development contract.

Actual project services are governed by the proposal, statement of work, invoice, written project agreement, or other written terms accepted by both sides.

If you do not agree with these terms, you should not use the website or submit an inquiry.

2. About NUSTFORGE

NUSTFORGE is an independent remote-first software engineering studio providing services such as website development, mobile and web application development, SaaS and MVP development, dashboards, portals, e-commerce systems, booking systems, AI tools, automation, cloud and API integrations, technical consulting, maintenance, and support.

The exact services, deliverables, responsibilities, timeline, payment terms, support arrangements, and technical scope for a project must be confirmed in the relevant written project documents.

3. Website information and availability

The website provides general information about NUSTFORGE, its capabilities, services, work, articles, and contact options.

Website content is provided for general informational purposes and does not constitute a binding offer, fixed quotation, technical guarantee, legal advice, financial advice, regulatory advice, or promise of a particular business result.

We may update, correct, reorganise, suspend, or remove website content or functionality without notice where reasonably necessary.

We aim to keep the website available and accurate, but we do not guarantee continuous availability or that every page will always be complete, current, or free from technical errors.

4. Permitted website use

You may use the website to learn about our services, review public case studies, read content, contact us, and request a project discussion.

You must not attempt unauthorised access, interfere with website operation, bypass security, introduce harmful code, submit fraudulent information, scrape the website in a harmful or excessive manner, impersonate another person, or use the website for unlawful, abusive, misleading, or malicious activity.

You must not copy, republish, falsely represent, or commercially exploit protected website content in a way that infringes intellectual-property rights or creates a misleading association with NUSTFORGE.

5. Project inquiries and initial communication

When submitting an inquiry, you should provide information that is accurate, relevant, and reasonably sufficient for us to understand the requested work.

Initial calls, messages, discovery discussions, technical suggestions, preliminary estimates, or informal recommendations are exploratory unless a written agreement states otherwise.

We may accept or decline an inquiry at our discretion, including where the requested work is outside our capabilities, conflicts with existing commitments, creates unacceptable risk, lacks sufficient information, or involves unlawful or inappropriate activity.

6. Proposals and written project agreements

A project begins only when the required scope, deliverables, responsibilities, payment arrangements, and start conditions have been accepted in writing and any required initial payment has been received.

A project may be documented through a proposal, statement of work, contract, invoice, email confirmation, or combination of written documents.

If a signed or expressly accepted project agreement conflicts with these general website terms, the project-specific agreement controls for that project.

Verbal discussions do not modify an accepted project agreement unless the change is later confirmed in writing by authorised representatives of both sides.

7. Estimates, pricing, taxes, and external costs

Custom software pricing depends on project scope, features, design requirements, integrations, content, infrastructure, technical complexity, urgency, risk, testing, support, and other requirements.

An estimate provided before detailed scope confirmation is indicative and may change when requirements, assumptions, timelines, third-party costs, dependencies, or requested features change.

Unless stated otherwise, prices do not include taxes, duties, payment-processing charges, currency-conversion costs, travel, specialist licences, third-party subscriptions, hosting, domains, API usage, AI usage, messaging costs, app-store fees, or other external expenses.

The client is responsible for applicable taxes and third-party costs unless the written project agreement clearly states otherwise.

8. Project scope and change requests

The agreed scope should identify the relevant pages, features, workflows, integrations, user roles, design direction, content responsibilities, technical requirements, deliverables, assumptions, and acceptance requirements.

Requests outside the accepted scope may require a revised estimate, additional payment, timeline adjustment, or separate statement of work.

Out-of-scope work may include additional pages, new user roles, new features, major design revisions, extra integrations, data migration, content creation, regulatory work, urgent delivery, AI or automation changes, infrastructure changes, or post-launch improvements not included in the original scope.

We will not be required to perform a material change until its effect on scope, timing, cost, or risk has been agreed where reasonably necessary.

9. Client responsibilities

The client is responsible for providing accurate business information, timely decisions, content, brand assets, feedback, approvals, access credentials, third-party account access, test data, and other materials reasonably required for the project.

The client must identify relevant business, legal, regulatory, accessibility, privacy, security, industry, and compliance requirements before or during planning.

The client is responsible for reviewing deliverables, testing agreed workflows, confirming content accuracy, validating business rules, and ensuring that the system is suitable for its intended operational use.

Delays in payment, content, access, feedback, approvals, decisions, third-party setup, or client dependencies may extend the delivery schedule and may require rescheduling.

11. Credentials, accounts, and security

Where access to domains, hosting, source control, databases, APIs, payment platforms, email systems, analytics tools, or other accounts is required, the client should provide access through secure and appropriate methods.

Clients should avoid sending passwords, secret keys, private keys, recovery codes, payment-card details, or highly sensitive credentials through ordinary email, website forms, or unsecured messages.

The client is responsible for maintaining appropriate account ownership, administrator access, billing details, recovery methods, multi-factor authentication, and credential security after handover.

Security work, monitoring, penetration testing, compliance certification, incident response, or ongoing vulnerability management is included only where expressly agreed.

12. Third-party tools and services

Projects may depend on third-party services such as hosting, domains, payment processors, app stores, databases, authentication providers, email platforms, SMS or messaging providers, analytics tools, APIs, cloud providers, AI services, automation platforms, libraries, plugins, or open-source software.

Third-party services are controlled by their respective providers and may be subject to separate pricing, availability, licences, policies, approval processes, usage limits, and terms.

NUSTFORGE is not responsible for third-party outages, suspensions, price changes, policy changes, security incidents, API changes, model changes, approval delays, account restrictions, discontinued features, or other matters outside our reasonable control.

The client is responsible for maintaining required third-party accounts, subscriptions, billing, licences, and compliance unless the project agreement states otherwise.

13. AI tools, automation, and generated output

Some projects may include AI models, chatbots, assistants, recommendation systems, automation workflows, document processing, generated content, classification, extraction, or other AI-assisted features.

AI-generated or automated output may be incomplete, inaccurate, outdated, biased, unexpected, or unsuitable for a particular purpose.

The client is responsible for implementing appropriate human review, business rules, warnings, permissions, testing, and safeguards before relying on AI or automated output.

AI features must not be treated as a substitute for qualified legal, medical, financial, regulatory, safety, or other professional judgment unless an appropriately qualified person has independently reviewed the result.

NUSTFORGE does not guarantee uninterrupted access to third-party AI services or perfect output in every situation.

14. Payments and invoicing

Deposits, milestones, invoice dates, payment methods, currencies, and final balances will be stated in the relevant proposal, invoice, or project agreement.

A project may not begin until the required initial payment and requested project information have been received.

Invoices must be paid according to their stated due dates. Late or missed payments may delay scheduling, delivery, deployment, support, access, or handover.

The client is responsible for bank charges, payment-provider fees, currency-conversion fees, taxes, and similar transaction costs unless agreed otherwise.

15. Suspension of work

We may pause work where an invoice is overdue, required client information or access is missing, the client has materially changed the scope without agreement, continued work creates a security or legal concern, or the client materially breaches an accepted agreement.

Where practical, we will explain the reason for suspension and the steps required to resume work.

A suspension caused by client delay, non-payment, missing access, or unresolved scope issues may affect availability and the original delivery schedule.

16. Cancellation, termination, and refunds

Cancellation and termination rights should be stated in the relevant project agreement, proposal, or invoice.

A client requesting cancellation remains responsible for completed work, approved milestones, committed third-party costs, and reasonably reserved delivery time where stated in the accepted project terms and permitted by applicable law.

Deposits or advance payments are not automatically refundable where they cover completed discovery, planning, design, development, setup, committed resources, or reserved capacity. Any refund assessment will consider the accepted agreement, work completed, costs incurred, and applicable legal rights.

If a project ends early, the release of source files, designs, credentials, environments, or incomplete work may depend on the project stage, payment status, technical feasibility, third-party licences, and written agreement.

Nothing in this section removes cancellation, refund, or consumer rights that cannot legally be excluded.

17. Timelines and delivery estimates

We aim to work according to agreed schedules, but estimated timelines depend on timely client feedback, approvals, content, payments, access, third-party services, and stable project requirements.

A delivery estimate is not a guaranteed completion date unless the written agreement expressly describes it as a fixed contractual deadline.

Scope changes, delayed client dependencies, third-party problems, technical discoveries, security concerns, illness, emergencies, or events outside reasonable control may require a revised timeline.

Where delivery is delayed, both sides should communicate in good faith and update the project plan where reasonably possible.

18. Testing, acceptance, launch, and handover

Projects may include agreed testing, responsive checks, workflow review, defect correction, performance review, deployment, and client acceptance activities.

The client should review deliverables and report material issues relating to the agreed scope within the acceptance period stated in the project agreement or, if no period is stated, within a reasonable time after delivery.

A defect is an issue where an agreed feature does not materially operate as described. New requirements, preference changes, external-service problems, content changes, or later enhancements are not automatically defects.

Launch or production use may require client approval, final payment, appropriate third-party accounts, production credentials, policies, content, and operational readiness.

Source-code handover, design-source files, documentation, deployment access, training, and data transfer are included only where stated in the agreed scope.

19. Maintenance and support

Post-launch support, maintenance, monitoring, backups, security updates, content changes, new features, infrastructure management, AI adjustments, automation changes, and third-party compatibility work are not automatically included unless stated in writing.

Any included defect-support period applies only to issues within the agreed scope and does not cover client modifications, third-party updates, expired subscriptions, hosting problems, misuse, new requirements, or external changes.

Ongoing support may require a separate maintenance plan, support package, hourly arrangement, or new project estimate.

20. Intellectual property and licences

The client retains ownership of materials, trademarks, content, data, and intellectual property it provides to NUSTFORGE.

After full payment, the client will receive the ownership or usage rights in final custom deliverables specifically identified in the project agreement.

NUSTFORGE retains ownership of pre-existing materials, reusable components, internal tools, generic code, templates, development methods, workflows, libraries, utilities, know-how, and non-client-specific concepts unless expressly transferred in writing.

Where retained NUSTFORGE materials are embedded in a fully paid deliverable, the client receives a continuing, non-exclusive licence to use those embedded materials as reasonably necessary to operate the delivered project, unless the project agreement states otherwise.

Open-source software, third-party packages, fonts, images, APIs, plugins, AI services, and other external materials remain subject to their respective licences and terms.

No ownership or licence is transferred until the relevant payment obligations have been completed, except where mandatory law or a written agreement requires otherwise.

21. Confidentiality

Each side should handle non-public business, technical, financial, operational, credential, and project information responsibly and use it only for legitimate project purposes.

Confidentiality does not normally apply to information that is already public through no breach, was independently developed, was lawfully known before disclosure, was received lawfully from another source, or must be disclosed by law.

A separate non-disclosure agreement may be used where a project involves commercially sensitive information, regulated data, proprietary processes, investor information, or unusual confidentiality requirements.

These website terms do not replace a project-specific confidentiality or data-processing agreement where one is required.

22. Portfolio and case-study use

Unless confidentiality, white-label restrictions, or written project terms prevent it, NUSTFORGE may display publicly available aspects of completed work in its portfolio, case studies, proposals, website, professional profiles, or marketing materials.

Portfolio references may include the client or project name, public screenshots, general service description, publicly accessible features, and technologies used.

We will not intentionally publish private credentials, restricted internal information, confidential datasets, non-public financial information, personal data, or protected business information.

A client may request reasonable portfolio restrictions in writing before publication, and any project-specific written agreement will control.

23. Warranties and disclaimers

NUSTFORGE will aim to perform agreed services with reasonable professional care and skill.

Except for express commitments in a written project agreement and rights that cannot legally be excluded, services and website content are provided without additional implied guarantees.

We do not guarantee that every website, app, integration, AI feature, automation, third-party service, or software system will operate without interruption, security risk, compatibility issue, or error in every environment.

The client is responsible for business continuity planning, appropriate backups, user training, internal controls, compliance review, and operational decisions unless those services are expressly included.

24. Limitation of liability

Nothing in these terms excludes or limits liability where exclusion or limitation is prohibited by applicable law, including liability for fraud, fraudulent misrepresentation, or death or personal injury caused by negligence where such liability cannot be excluded.

To the maximum extent permitted by law, NUSTFORGE is not responsible for indirect, incidental, special, punitive, or consequential loss, or for loss of profit, revenue, opportunity, goodwill, anticipated savings, business continuity, or data arising from matters outside the agreed scope or reasonable control.

NUSTFORGE is not responsible for loss caused by incorrect client instructions, unlawful or inaccurate client content, weak client credentials, unauthorised client changes, third-party services, hosting failures, API changes, platform policies, expired subscriptions, AI output, client misuse, or failure to maintain appropriate backups.

Unless a written project agreement states a different lawful limitation, NUSTFORGE’s aggregate liability arising from a specific project will not exceed the fees actually paid to NUSTFORGE for the specific services giving rise to the claim.

Any limitation applies only to the extent that it is fair, reasonable, and legally enforceable in the relevant circumstances.

25. Mandatory and consumer rights

Nothing in these terms removes statutory, consumer, data-protection, or other mandatory rights that cannot lawfully be excluded or limited.

Where you are legally treated as a consumer, provisions concerning service quality, remedies, cancellation, refunds, liability, and fairness apply according to the mandatory law relevant to the transaction.

If a provision conflicts with a mandatory legal right, that provision applies only to the maximum extent permitted without affecting the remainder of the terms.

26. No guaranteed commercial results

NUSTFORGE may help improve software quality, workflow efficiency, user experience, performance, automation, technical structure, and digital delivery.

We do not guarantee particular sales, leads, search rankings, traffic, revenue, funding, user growth, conversion rates, operational savings, market success, or other commercial results.

Business outcomes depend on factors outside our control, including market demand, pricing, competition, marketing, content, operations, customer behaviour, third-party platforms, and the client’s implementation decisions.

27. Events outside reasonable control

Neither side will be responsible for delay or failure caused by events outside its reasonable control, such as major infrastructure outages, natural disasters, war, civil disruption, government action, widespread cyber incidents, internet failures, third-party platform failures, labour disruption, serious illness, or other comparable events.

The affected side should communicate the issue where reasonably possible and take proportionate steps to reduce its effect.

If such an event materially prevents continued delivery for an extended period, the parties should discuss rescheduling, scope adjustment, suspension, or termination in good faith.

28. Privacy and personal information

Information submitted through the website, project forms, email, WhatsApp, and business communication is handled according to the NUSTFORGE Privacy Policy and applicable project arrangements.

A project involving personal information, regulated data, user tracking, or international data processing may require additional privacy documentation, client instructions, consent controls, security measures, or a data-processing agreement.

The client is responsible for identifying its role and obligations concerning personal information processed through the delivered system.

30. Changes to these terms

We may update these general website Terms of Service to reflect changes in the website, services, tools, business operations, or legal requirements.

The updated date shown at the top of the page identifies the current version.

Changes to these website terms do not retroactively modify an already accepted project agreement unless both sides agree in writing or applicable law requires the change.

31. Severability, waiver, and entire agreement

If a provision of these terms is found invalid or unenforceable, it will be limited or removed only to the extent necessary, and the remaining provisions will continue where legally possible.

A delay or failure to enforce a right does not automatically waive that right.

For website use, these terms and the Privacy Policy form the relevant general agreement. For paid services, the accepted proposal, statement of work, invoice, project agreement, and incorporated policies form the project agreement.

32. Governing law and dispute resolution

Any signed or expressly accepted project agreement may identify the governing law, courts, arbitration arrangement, or dispute process for that project. Where it does, that project-specific provision controls.

If no governing-law provision has been agreed, the applicable law and forum will be determined according to the parties, place of business, place of performance, mandatory rules, and other legally relevant circumstances.

Before starting formal proceedings, both sides should attempt in good faith to resolve a dispute through written communication and reasonable discussion, except where urgent legal relief is required.

33. Contact us

If you have questions about these Terms of Service, project scope, estimates, payments, support, or working with NUSTFORGE, contact us at hello@nustforge.com.

You can also use the contact options available at https://www.nustforge.com.

Terms questions

Need clarification before starting?

Contact NUSTFORGE about project scope, estimates, payments, delivery, support, intellectual property, or working with us.