TERMS &
CONDITIONS

These draft Terms & Conditions describe the proposed basis for using the Suhoo.dev website and working with our digital product studio. In this document, ‘we’, ‘us’ and ‘our’ refer to the service provider identified in your written project agreement. ‘You’ means a website visitor or a client, as appropriate.

A project agreement should identify the contracting parties and explain the specific work being commissioned. Where an agreed project document expressly sets different project-specific terms, those terms should be read together with this document and applicable law.

This version is a draft for review and is not yet in effect. The service provider’s legal identity, contact details and applicable jurisdiction must be confirmed before publication.

You may browse this website to learn about our studio and consider our services. Please use it lawfully and in a way that respects the website, other visitors and the rights of others.

Some product visuals and customer quotes are illustrative concepts or samples, as labelled. Third-party names and marks belong to their respective owners; displaying them does not, by itself, indicate an endorsement or partnership.

• Do not attempt to gain unauthorised access to the website, its systems or other people’s information.
• Do not introduce malicious code, disrupt the website or use automated activity that materially impairs its operation.
• Do not reproduce or commercially distribute protected website content without the relevant permission or another lawful basis.

Our work may include websites, mobile applications, UI/UX design and custom software. The scope of an individual engagement is established in a written proposal, statement of work or other project agreement accepted by both parties.

An enquiry, preliminary discussion or estimate does not, on its own, commit either party to a project. Before work begins, the project agreement should make the following clear:

• The deliverables, responsibilities and any work that is outside the agreed scope.
• The fees, currency, applicable taxes and payment milestones.
• The expected schedule, review rounds, acceptance process and handover arrangements.
• Any hosting, maintenance, support or ongoing services included in the engagement.

Good work depends on clear communication. We will work with you to understand the brief and provide the agreed services with reasonable care. You are responsible for providing accurate requirements, necessary materials, permissions, access and timely feedback.

Schedules depend on the agreed scope, approvals and both parties’ contributions. If a delay or change affects a milestone, we should discuss its impact and agree an updated plan. A change to scope, cost or timing should be confirmed in writing before the additional work proceeds.

The project agreement and invoices specify the amount payable, payment dates, currency and any applicable taxes or third-party costs. This website does not establish a standard deposit, cancellation charge, subscription or payment schedule.

Additional services and expenses should be discussed and agreed before they are charged. If there is a payment concern or an invoice appears incorrect, raise it promptly with the contact identified in your project agreement so it can be reviewed.

Any late-payment remedies or proposed suspension of work should follow the agreed project terms and applicable law, with appropriate notice and an opportunity to address the issue where required.

Materials you already own remain yours. Please provide only materials that you own or are authorised to use, including text, images, fonts, data, trademarks and software.

The project agreement should expressly state the ownership or licence granted for final deliverables, when that grant takes effect, and how pre-existing tools, reusable components and working files are treated. Payment alone should not be relied on as a substitute for a clear written intellectual property agreement.

Third-party software, open-source components, fonts, images and other licensed assets remain subject to their respective licences. Any relevant licence requirements or continuing costs should be identified as part of the project and handover.

A project may depend on services such as hosting, domains, app stores, payment providers or external APIs. Those providers have their own terms, availability, fees and policies. The project agreement should identify who owns and manages the relevant accounts and who pays any continuing costs.

We should make material dependencies clear and discuss foreseeable limitations. Changes made by an external provider may require additional work; any related changes to the agreed scope or fees should be discussed before that work proceeds.

Where a separate product-specific agreement is provided for a standalone product, it applies to that product together with any relevant mandatory rights.

Both parties should protect non-public business and project information shared in confidence and use it only for the engagement or another agreed purpose. Access should be limited to people who need it for the project, subject to appropriate confidentiality obligations and any lawful disclosure requirements.

If a project involves personal data, the parties should agree the relevant processing roles, permitted uses, security measures and any required data-processing arrangements before that access is provided. Share only information that is necessary for the work and that you are authorised to disclose.

The project agreement should explain how either party can pause or end an engagement, including any applicable notice, opportunity to remedy an issue and arrangements for completed work, handover and outstanding payments.

Any cancellation charge, payment for work already completed or refund of a prepayment should be assessed under the agreed terms and applicable law. These website terms do not impose a blanket non-refundable deposit or remove a cancellation or refund right that the law gives you.

The project agreement should describe the expected standard of work, acceptance process and any agreed warranty or support period. If something does not meet the agreement, contact us with the relevant details so we can discuss the issue and an appropriate response.

Any proposed exclusion or limit of liability must be clearly set out in the project agreement and remain subject to applicable law. This draft does not introduce a fixed liability cap or excuse a party from its agreed obligations.

Nothing in these terms is intended to remove a right or remedy that cannot lawfully be waived, or to exclude liability that cannot lawfully be excluded.

A revised version of these terms should show its updated date and be available for review before it is relied on. Changes to an existing engagement should be agreed in writing; updating a public webpage does not, by itself, rewrite an accepted project agreement.

If a concern arises, the first step is to raise it with the contact named in your project agreement and try to resolve it constructively. Any governing law, forum or dispute-resolution process must be confirmed in the agreement and must respect mandatory rights that apply to the engagement.

For an existing project, use the contact details in your accepted proposal or project agreement. The service provider’s public details will be completed below before this draft is put into effect.

Service provider

To be confirmed

Registration

To be confirmed, where applicable

Registered address

To be confirmed

Governing law / jurisdiction

To be confirmed

Contact email

To be confirmed