Terms of Service

1. Acceptance of These Terms

By accessing this website, by using any part of it, or by instructing the company to perform services, you confirm that you have read and understood these terms and that you agree to be bound by them. If you do not agree, please do not use the website and do not send us a service instruction.

These terms apply together with any written proposal, statement of work, adoption sheet or master agreement that the company signs with you. If a signed document contradicts these terms, the signed document controls for that project, and these terms continue to govern the rest of the relationship.

Where you accept these terms on behalf of an organisation, you confirm that you have authority to bind that organisation. If it later appears that you did not have that authority, the person accepting these terms remains personally responsible for the obligations that arise.

2. Definitions

The following definitions apply throughout these terms. They are written to be read by people, not only by lawyers.

• Company means WeiFang TuMao Information Technology Co., Ltd., including its employees and authorised representatives.
• Website means the pages served from https://www.bunnycat.autos and every page under that domain.
• Services means the computer integrated systems design work and the related advisory work described on the services page and in a signed project document.
• Client means the person or organisation that engages the company for services.
• Deliverable means a document, design, configuration, script, integration or other item that the company produces for the client under a project document.
• Adoption sheet means the written record that names the scope, the owners and the acceptance criteria of a project.
• Hutch desk means the working method of the company, including note runs, letter desks, play windows, review rounds and sittings.

3. Our Services

The company provides professional, scientific and technical services, with a focus on computer integrated systems design. The services we offer are organised into six families, and each family is described in more detail on the services page of this website.

Adoption Sheet Bays

The intake stage in which we write the adoption sheet for a project. The sheet records the problem, the people involved, the systems in scope and the criteria by which success will be judged.

Hutch Note Runs

Regular written notes that record decisions, open questions and risks. Note runs keep a project traceable without turning every week into a long meeting.

Family Letter Desks

Plain language letters that explain technical change to the people outside the build, so that managers and clients can follow the work without a translator.

Play Windows

Scheduled periods in which a client team may use a system in a safe environment, testing real workflows under supervision and recording what needs to change.

Feed Review Rounds

Structured reviews that place performance, cost and reliability side by side and feed the results back into the next adoption sheet.

Hutch Sittings

Attended working sessions in which our engineers sit beside client staff and improve the system together, ending with a short written record.

The descriptions on this website are a general overview and do not themselves create a binding obligation to deliver a particular result. The specific obligations of a project are those written in the signed project document, and the company may adjust its method where the client agrees to the adjustment in writing.

4. Eligibility and Authority

This website is intended for business and professional users. By using it, you confirm that you are at least eighteen years old or that you are using the site under the supervision of a person who is responsible for you.

Where the client is an organisation, the client must ensure that each individual who sends instructions has the authority to do so. The company may rely on an instruction that appears to come from an authorised address, and it may ask for confirmation before it acts on an instruction that seems unusual.

If the client operates in a sector with special rules, for example in health, finance or public infrastructure, the client must tell the company about those rules before work begins. The company will then decide whether it can accept the project and what additional controls the work requires.

5. Website Use and Conduct

We provide this website so that people can learn about our services and contact our desk. We ask that you use it in the same way that a visitor to an orderly room would behave: with care, with honesty and without disturbing the other visitors.

You agree that you will not attempt to gain unauthorised access to any part of the website or to any system that supports it. You will not probe our servers for vulnerabilities without a written invitation, and you will not use automated tools to copy the site at a volume that interferes with ordinary visitors. You will not introduce malicious code, and you will not present our content as your own.

Where we provide a form, you will submit accurate information and you will not use the form to send bulk advertising, chain messages or content that is unlawful. Where we provide a free document, you may read it and share a link to it, but you may not remove our attribution or resell the document as your own product.

If we find conduct that breaches this section, we may limit access to the website, refuse further correspondence and take any other step that is reasonable to protect the site and its visitors.

6. Project Engagements

A project begins when the company and the client sign an adoption sheet or a statement of work. The document identifies the scope, the schedule, the responsibilities of each side and the acceptance criteria for the deliverables.

Changes to scope are made in writing. When a change is requested, the company will describe the effect on schedule and fees, and work on the change begins only after both sides agree. This protects the client from unexpected cost, and it protects the company from silent growth in the workload.

Unless a project document says otherwise, dates are estimates rather than guaranteed deadlines. The company will notify the client promptly if a date is at risk, explain the cause, and propose a revised plan. The client will give timely feedback on deliverables, because a delay in feedback naturally moves the later stages of the project.

The company may use subcontractors for a specialised task. Where it does, the company remains responsible to the client for the quality of the subcontracted work, and it requires the subcontractor to protect the client information that the task requires.

7. Fees and Payment

Fees are set out in the project document. The company may charge a fixed fee, a time based fee or a blended arrangement, depending on the nature of the work. Where a fee estimate is given, it is based on the information known at the time, and the company will discuss any significant variation before it arises.

Unless the project document says otherwise, invoices are payable within thirty days of the invoice date. Payments are made in the currency stated on the invoice. The client is responsible for any bank charge or transfer fee that its own payment route incurs.

Where a payment is late, the company may charge interest at the rate stated in the project document or, if no rate is stated, at the rate permitted by the law that governs these terms. The company may also pause work until the overdue amount is paid, after giving written notice and a reasonable opportunity to pay.

Fees do not include travel, hardware, software licences or other expenses unless the project document says that they are included. Expenses that are agreed in advance are billed at cost with supporting receipts. Taxes are added where the law requires them, and the client is responsible for taxes that arise in its own jurisdiction.

8. Client Responsibilities

A good integration depends on both sides keeping the desk in order. The client agrees to the following responsibilities.

• Provide accurate information about the existing systems, the business rules and the constraints that must be respected.
• Nominate a contact person who can answer questions and approve decisions within a reasonable time.
• Give the company the access that the work requires, including accounts, documentation and, where needed, a safe test environment.
• Ensure that any data the client supplies has been collected and may be used lawfully for the project.
• Keep its own backups of data that it considers essential, unless the project document says that backup is part of the company scope.
• Review and accept or reject deliverables within the period stated in the project document.

If the client does not meet a responsibility above, the company may be unable to perform a task. In that case the company will tell the client what is missing, and it may reschedule the affected work. The company is not responsible for a delay that is caused by a missing client input, provided that the company has given clear notice of the requirement.

9. Intellectual Property

The website and its written content belong to the company. That includes the text, the visual design of the pages, the structure of the service descriptions and the name of the hutch desk method. You may read the content and share links to it, but you may not copy it at scale or use it to train a competing service without written permission.

For project work, the project document describes which rights pass to the client and which remain with the company. Unless the document says otherwise, the client receives a perpetual licence to use the deliverables for its own business, and the company keeps ownership of the general methods, templates and know how that it uses across projects. This approach lets the client use the result freely while allowing the company to keep improving the method for other clients.

Where a deliverable includes content that the client supplied, the client keeps ownership of that content and grants the company the rights that are needed to perform the work. Where a deliverable includes an open source component, that component remains under its own licence, and the company will identify it so that the client can comply with the licence.

10. Third Party Components

Modern systems are assembled from components that other organisations maintain. The company may use such components in a project, and it will choose them with care. The company does not control those components, and it cannot promise that a third party will continue to support them or will not change their terms.

Where a third party component is governed by an open source licence, the client must respect that licence, including any requirement to publish notices or to share modifications in certain circumstances. The company will give the client the information needed to meet those requirements.

Where a project depends on a commercial service, such as a cloud platform or an email provider, the client is responsible for any subscription that it holds with that service. The company is not responsible for a service interruption that the third party causes, though it will help the client mitigate the effects where the project document allows.

11. Confidentiality

Each side may receive information that the other side treats as confidential. Each side agrees to use such information only for the purpose of the project, to protect it with reasonable care and to disclose it only to persons who need it and who are bound by a comparable duty.

The duty of confidentiality does not apply to information that is already public, that was lawfully known before the project, that is received from a third party without a duty, or that must be disclosed by law. Where a legal authority requires disclosure, the side that receives the request will give the other side prompt notice where the law allows, so that the other side may respond.

The duty of confidentiality continues after the project ends. When a project document sets a specific period, that period applies. When no period is set, the duty continues for five years after the end of the project, or for as long as the information remains confidential if that is longer.

12. Privacy and Data Protection

Our handling of personal information is described in the Privacy Policy, which forms part of these terms. The Privacy Policy explains what we collect, why we collect it and how you may exercise your rights. We recommend that you read it before you send any personal information to our desk.

When we access personal information that belongs to a client, we do so only as instructed by the client and only for the purpose of the project. We do not use client data for our own marketing, and we do not combine it with data from other clients. Where a project requires a separate data processing agreement, the company will provide one and will sign it before the relevant work begins.

If a security incident affects client data that is under our control, the company will notify the client without undue delay and will cooperate with the investigation and the legal notifications that the incident requires. The company will not make a public statement about such an incident without first telling the client, unless the law obliges it to speak sooner.

13. Warranties

The company warrants that it will perform the services with the skill and care that are reasonable for a professional provider of computer integrated systems design, and that the deliverables will materially conform to the project document at the time of acceptance.

If a deliverable does not conform to the project document, the client must notify the company within thirty days of acceptance and describe the non-conformity. The company will then correct the deliverable at no additional fee, or, where correction is not practical, will discuss an alternative remedy with the client.

The warranty above does not cover a defect that results from a change made by the client, from the use of the deliverable outside its documented purpose, or from a fault in a system that the client controls. It also does not cover ordinary wear and tear in a third party service that the client maintains separately.

14. Disclaimer of Certain Warranties

Except for the warranties stated in section 13, the website and the general information on it are provided as they are. The company does not warrant that the website will be available without interruption, that it will be free of errors, or that the information on it will always be current.

The website describes a working method in general terms. It does not give technical advice for a specific environment, and it must not be relied upon as a substitute for a project assessment. Before you change a production system, obtain advice that takes account of your own circumstances.

The company does not warrant that any third party service will continue to operate, that any third party website will remain available, or that another organisation will keep the promises that it makes in its own materials. Where you depend on a third party, your relationship with that third party is separate from your relationship with the company.

15. Limitation of Liability

To the extent that the law permits, the total liability of the company under a project is limited to the total fees paid by the client for that project during the twelve months before the event that gave rise to the liability. Where a project document sets a different limit, that limit applies.

To the extent that the law permits, the company is not liable for indirect or consequential loss, for loss of anticipated profit, for loss of goodwill, or for loss of data that the client could have prevented with a reasonable backup. The company is not liable for a delay that is caused by a third party or by a client input that arrived late.

Nothing in these terms excludes a liability that cannot lawfully be excluded, including a liability for fraud or for death or personal injury caused by negligence. Where the law of your jurisdiction does not allow a particular limitation, that limitation does not apply to you, and the rest of these terms continues to operate.

16. Indemnification

The client agrees to indemnify the company against a claim that arises from content or data that the client supplied, where the client did not have the right to supply it, or from a use of a deliverable that the client made outside the documented purpose. This obligation applies only to the extent of the clients own contribution to the claim.

Where a third party claims that a deliverable infringes a right, the company will investigate promptly and will, at its option, modify the deliverable, obtain a licence for the client, or provide a reasonable substitute. The company will not be responsible for a claim that arises from a modification that the client made without the company agreement.

Each side will give the other prompt notice of a claim that may fall under this section and will cooperate in the defence. A side that fails to give notice is responsible for any additional cost that the delay causes, but the duty to indemnify remains for the underlying claim.

17. Suspension and Termination

A project may end in several ways. The client may terminate for convenience by giving the notice required in the project document, and the company will then stop work at a natural point and invoice the work completed. The company may terminate for convenience with the same notice, and it will hand over the deliverables that have been paid for.

Either side may terminate immediately if the other side commits a material breach and does not remedy it within thirty days of written notice. Either side may terminate immediately if the other side becomes insolvent, ceases to trade, or is subject to an order that prevents it from continuing.

The company may suspend work if an invoice remains unpaid after the notice period, or if the client does not provide an input that the work requires after a clear written request. Suspension is not termination, and work resumes when the missing condition is resolved.

When a project ends, the sections that by their nature should survive continue in force. These include confidentiality, intellectual property, fees owed, the disclaimer of certain warranties, the limitation of liability and the governing law section.

18. Force Majeure

Neither side is responsible for a failure to perform that is caused by an event beyond its reasonable control. Such events include a natural disaster, a widespread power failure, an interruption of a public communication network, an act of government, a pandemic and a serious civil disturbance.

The side that is affected will notify the other side as soon as it can and will describe the expected effect on the schedule. It will also take reasonable steps to reduce the effect and to resume performance. If the event continues for more than sixty days, either side may terminate the affected project on written notice, and the company will invoice the work completed up to that point.

A force majeure event does not excuse a payment that is already due, unless the event also prevents the payment route from working. In that case the client will pay as soon as the route is available, and the company will not charge interest for the period of the interruption.

19. Governing Law and Disputes

These terms are governed by the laws of China, without regard to rules that would choose the law of another place. A project document may choose a different governing law for that project, provided that both sides sign the choice in writing.

If a dispute arises, the sides will first try to resolve it through direct discussion between the people who are responsible for the relationship. If discussion does not resolve the matter within thirty days, the sides will consider a structured negotiation or a mediation before either side begins formal proceedings.

Where a dispute is not resolved by discussion or mediation, the courts of the place where the company is established have jurisdiction, unless a project document says otherwise or unless the law of your jurisdiction gives you a right to bring the matter before a different court. Nothing in this section prevents either side from seeking urgent relief to protect a right that would otherwise be lost.

20. Changes to These Terms

The company may update these terms from time to time to reflect a change in its services, its website or the law. When it does, it will update the date at the top of this page. If a change is material, the company will describe the change in a short notice on the website so that returning readers can see what is different.

A change to these terms applies to a new engagement from the date of the change. For an engagement that is already running, a change applies only when both sides agree in writing, unless the law requires a different result.

If any part of these terms is found to be unenforceable, that part is limited to the extent needed to make it enforceable, and the rest of the terms continue in force. A failure to enforce a term on one occasion is not a waiver of the right to enforce it later.

21. Contact Information

If you have a question about these terms, if you wish to discuss a project, or if you believe that a term has not been met, please contact the company at the details below. We read every message and we aim to reply within two business days.

WeiFang TuMao Information Technology Co., Ltd.
No 5369, Unit 1-510-284 (Entrusted), Beigong East Street, Beihai Road Subdistrict, Kuiwen District, WeiFang City - 261000, China (CN)

Email: pets@bunnycat.autos
Phone: +16604939529

These terms, together with the Privacy Policy, form the complete agreement between the sides about the use of this website. They replace any earlier discussion on the same subject, except where a signed project document records a different arrangement for a specific project.