Simple Terms for Custom Programming Services

The provider will deliver the programming services described in the applicable proposal, statement of work, issue scope, or written project brief. Deliverables may include product requirements documents, UI pages, application features, backend routes, integrations, tests, deployment support, and related technical documentation.

Anything not clearly listed in the approved scope is not included by default. If the client requests extra work, both sides should confirm the added scope, price, and timeline in writing before the provider is required to perform it.

The client must provide timely access to the people, systems, brand assets, and decisions needed to complete the work. This includes approvals, technical contacts, credentials, environment details, and feedback within the agreed review window.

If the client delays approvals or fails to provide required access, the provider may move delivery dates by the amount of the delay and may pause work until the missing dependency is resolved.

• The client is responsible for the legality and accuracy of the content, data, and instructions it provides.
• The client must not give the provider credentials it does not have the right to share.

The client agrees to pay the fees stated in the approved commercial document. Fees may be fixed-price, milestone-based, retainer-based, or time-and-materials, depending on what was agreed for the project.

Invoices are due on the schedule stated in the contract or invoice. Late payments may delay further work, releases, support, or handoff until the overdue amount is paid.

• Third-party software, hosting, RPC, vendor, or infrastructure charges are billed separately unless the contract says they are included.
• Change requests may be quoted separately and do not need to be started before approval.

After the client pays all amounts due, the client owns the final custom deliverables created specifically for the client under the engagement. This includes project-specific code, documentation, and design work identified as paid deliverables.

The provider keeps ownership of its pre-existing materials, reusable utilities, general templates, methods, libraries, and know-how. The client receives a license to use those embedded materials only as needed to use the deliverables.

Each side must protect the other side's confidential information and use it only for the engagement. Confidential information includes non-public business plans, credentials, private technical details, and customer data shared for the work.

The provider will use reasonable care to protect credentials and sensitive project access, but the client remains responsible for rotating access when the engagement ends or if exposure is suspected.

• Real secrets should not be stored in source-controlled files.
• The provider may refuse unsafe instructions that would weaken auth, treasury controls, auditability, or release safety.

The provider does not control third-party platforms such as hosting providers, authentication services, blockchain networks, oracle feeds, wallet software, payment facilitators, or external vendor APIs. Because of that, the provider cannot promise uninterrupted operation of those outside services.

The provider promises to perform the services in a professional manner, but does not guarantee that software will be completely error-free or that external systems will always behave as expected.

• The client should test important workflows before production launch.
• Except where the law does not allow it, the provider is not liable for indirect, special, or consequential losses such as lost profits, lost token value, or missed market opportunities.

Either side may end the engagement if the other side materially breaches the agreement and does not fix the problem within the written cure period, or if the applicable commercial document allows termination for convenience.

When the engagement ends, the client must pay for all approved work completed up to the end date. After payment, the provider will hand over the completed deliverables and any agreed project materials that belong to the client.

• Sections about payment, confidentiality, intellectual property, liability limits, and dispute handling survive termination.
• If the parties need a governing law, venue, or dispute-resolution clause, that should be added in the signed commercial document.