Terms of Service

1. Acceptance of these terms

These Terms of Service become binding at the earliest moment that you perform an act of acceptance. That moment may be when you visit a page, submit a form, send a written enquiry, or sign an electronic quotation. Simply by continuing to use any HYHDATA LLC property after you have been given the opportunity to read this document, you agree to be bound by everything written here.

Nobody is forced into an agreement. If you do not agree with any clause of these terms, your remedy is straightforward and costs you nothing: stop using our websites and do not open a project with us. By choosing to proceed after a chance to read these terms, you confirm that you accept them fully and without reserving a silent exception to a later paragraph.

Where we work with an organization on your behalf, these terms bind the legal entity that you represent. When you click confirm for a business, you confirm that you hold the authority to bind that business to these terms. Individuals acting in a personal capacity are bound as individuals. In every case the word you means the party that engages us, however that party is named in correspondence.

2. Who we are and what we do

HYHDATA LLC is a professional organization in the field of computer integrated systems design and related technical services. Our work covers the design of data pipelines, the modeling and migration of databases, the construction of analytics dashboards, the auditing of data quality, and the integration of systems through application interfaces. These are engineering activities performed with care, judgment, and professional accountability.

Our company is a registered entity in the United States. This document is offered by and to all clients regardless of the country in which each client operates. We take pride in a plain and honest working style, and these terms reflect that tone. We have deliberately written them in everyday language wherever the law permits us to do so, rather than burying meaning in phrases that nobody can read.

Nothing in these terms creates a joint venture, a partnership, or an employer relationship between you and us. Each of us remains a separate and independent party, responsible for our own actions, taxes, people, and liabilities. Our engineers work under our supervision, and any subcontractor we choose to engage works under the very same discipline as our own staff and is bound to protect your interests.

3. Your use of our websites

You may browse and read the public content of our websites for your own legitimate purposes. You may not copy the structure, the writing, the images, or the distinctive visual style of our pages for use in a competing service. You may not probe, scan, or test our systems in a way that seeks to sabotage or overload them, and you may not attempt to gain access to an account or a server that has not been given to you.

We grant you the right to view the materials on our sites as they are presented. We do not grant you a license to download large portions of the site for offline use, to republish our content in another place, or to frame our pages inside your own interface. Any use that misleads visitors about the source of the content is prohibited.

When you post a comment, ask a question, or use a tool on our site, you remain responsible for what you submit. You agree not to send us unlawful material, harmful code, deceptive messages, or content that infringes the rights of another party. We reserve the right to remove any contribution that violates this paragraph and to bar the person who posted it.

4. Quotations and engagement letters

Every engagement of any size begins with a written quotation or an engagement letter. That document states the deliverables, the timeline, the fee, and the assumptions on which the estimate rests. It is the definitive scope of the work, and it takes priority over any early and informal conversation when the two things conflict.

A quotation is an invitation to you, not a binding promise to us. We can reconsider or withdraw a quotation at any time before you accept it. Your acceptance may come as a signature, an electronic confirm, or a written approval, whichever the quotation names. Once you accept, the engagement letter becomes a binding contract under these terms.

If the work that you ask for later changes in a material way, we will share a revised quotation before we continue. We will not silently expand the work and then present you with a surprise invoice. Likewise we expect that you will not quietly expand the request without telling us; an honest change order at the time far beats a disagreement at the end of the month.

5. Scope of services and deliverables

We agree to deliver the services and reports named in the engagement letter with reasonable skill and care. Data pipeline work includes the authoring of extraction, transformation, and loading routines that run on the schedule we describe. Database work includes the schema, the indexes, and the migration scripts that the letter names.

Analytic work includes the dashboards, the queries, and the underlying data model that we agree to produce. Quality audit work includes the findings report and the list of recommended corrections. Integration work includes the connectors, the documentation, and the handover notes that let your own team maintain what we build.

Deliverables are accepted against the written acceptance criteria in the engagement letter. Where no acceptance test is written, a deliverable is deemed accepted when it meets the description in the letter and performs its stated purpose without material fault. We keep every deliverable honest: if a piece of work cannot meet its goal, we say so rather than declaring victory for appearance.

6. Fees, invoicing, and payment

The engagement letter states the fee and how and when it is due. We use three common arrangements depending on the size of the work: a fixed price for a well defined deliverable, a monthly recurring fee for an ongoing service, or a time and materials fee for open ended advisory work. The letter makes clear which arrangement applies.

Invoices are due within the period named on the invoice, which is commonly thirty days from the invoice date. For work delivered in stages, each stage is invoiced as it completes. We may ask for a deposit on larger projects, and we will list that deposit in the engagement letter so that no payment comes as a surprise.

An invoice that remains unpaid past its due date may be subject to a reasonable late fee to the extent the law allows, and we may pause further work until the balance is settled. Disputed amounts are handled separately and do not hold up the payment of the parts that are not in dispute. When you pay, your payment closes the amount in full unless we agree in writing that a balance remains.

7. Customer responsibilities

For a project to succeed, each side has duties. On our side the duties are to deliver skilled work and to communicate honestly. On your side the duties are to supply what we need and to decide within a reasonable time. A project starves without timely answers, valid access, and a clear idea of what success looks like.

You agree to provide the information, the accounts, the sample data, and the internal contacts that our work reasonably requires, and you agree to keep that access current. You also agree to review drafts and deliverables within the timeframes that the engagement letter expects, so that the schedule does not slip for a reason that we cannot control.

Where our work depends on another vendor that you have chosen, such as a hosting plan or a software license, you are responsible for keeping that vendor account in good standing. A project delayed by a failure on your side may be rescheduled without cost to us, and any resulting extra work may be invoiced under the change process described above.

8. Access to data and systems

Many projects require us to touch systems that belong to you. Any access that we receive is granted for the purpose of the named work only, and it is not a permanent key to your environment. At the end of the engagement, or when you revoke it, we return or destroy the copies of your data that we hold, except where the law or a standing agreement says to keep them.

We treat the boundaries of that access with discipline. We will not browse records that have nothing to do with the work at hand, and we will not copy your data to a place outside the guardrails that the engagement letter describes. Access credentials are handled under the confidentiality section of these terms.

When you allow us access, you confirm that you have the right to grant it. You agree not to share with us data that you are not permitted to give to an outside party. Our responsibility to safeguard the data is serious, but the initial authority and the initial compliance burden for deciding what can be shared sits with you.

9. Ownership of work product

Upon full payment, ownership of the custom work product that we specifically build for you, such as bespoke schemas, bespoke pipelines, and hand written integration code, passes to you for your own use. This ownership is real and practical: you may run, modify, and maintain the work yourself or with any engineer you choose.

Some elements do not pass to you because they remain the general craft of our firm. Our internal frameworks, our pre written routines, our documentation templates, and our general engineering know how stay with us. When a deliverable contains one of these reusable pieces, we grant you a non exclusive, perpetual license to use that piece as part of the delivered work, so that your project is never blocked by a missing internal part.

Third party software that we license to include in a deliverable keeps its own license terms. Where that third party license requires a notice or an attribution, we will pass that notice on to you with the deliverable. In short, what you pay to have made to your order is yours, our general craft stays ours, and every borrowed part keeps its own honest label.

10. Confidentiality

During a project we see things on both sides that are not intended for the public. Client data, business plans, pricing, source code, internal reporting, and the details of an engagement are all confidential unless the parties clearly agree otherwise. Each side agrees to guard the other side secret information with the same care that it guards its own.

This duty of confidentiality does not apply to information that is already public, that arrives from another source without a duty of secrecy, that the owner has allowed to be shared, or that we are ordered to reveal by a lawful authority. Even in a permitted disclosure, we reveal only the part that is needed and we give you notice when we can lawfully do so.

Confidential information is shared only with the people who need it for the work. It is not passed to third parties, retold for our own benefit, or recycled into a competing project. This obligation survives the end of the engagement, because trust does not expire on the final invoice date.

11. Quality, warranties, and accepted faults

We warrant that our work will be performed with the degree of skill and care that a qualified professional in our field would reasonably apply. We do not warrant that a system will be entirely free of faults, because no engineer can honestly make that promise about complex software. What we do promise is that we will fix genuine faults that we introduced, without padding the bill for the repair.

After the accepted delivery, we provide a short warranty period named in the engagement letter, during which defects in the delivered code that are traceable to our work are corrected at no further fee. Defects that arise from changes you make later, from the failure of a system you operate, or from circumstances beyond our control are addressed under the ordinary change process rather than under warranty.

If you believe a deliverable does not match the agreed specification, you should tell us within a reasonable time of receiving it. We will review the claim, and where it is well founded we will bring the work up to the agreed standard. This correction path is your first and intended remedy for a quality problem, and it keeps the working relationship warm before formal fault notices become necessary.

12. Limitation of liability

To the fullest extent that the law allows, neither party is liable to the other for indirect, special, incidental, or consequential damages. This category includes lost profits, lost revenue, lost goodwill, and the cost of downtime that flows from a failure of the work, where those losses are not the direct and foreseeable result of a breach.

Each side total liability for a claim that arises under an engagement is capped at the total fees that you actually paid us for that engagement. This cap is honest and it is deliberate: engineering projects are priced on the basis of the effort involved, not on the size of the business that the work supports, so a fair cap must follow the fees and not the scale of an unseen operation.

Nothing in these terms excludes liability that cannot lawfully be excluded, such as liability for fraud, for death or personal injury caused by negligence, or for any other category that the law of your region refuses to let a contract remove. Where a region imposes a different rule, the rule of that region applies to the claims that it covers.

13. Indemnification

You agree to defend and hold harmless HYHDATA LLC and its people against claims that arise from your misuse of the services, from a breach of these terms on your side, or from your failure to hold the right to share data that you gave us. This cover is limited to claims that flow from your actions rather than from the ordinary performance of our agreed work.

We likewise owe you a fair account for the work we deliver. Where a third party claims that code we wrote to your order infringes that party intellectual property right, and where we used that code without relying on material that you supplied, we will, at our option and expense, either obtain the right for you to keep using it, replace it with an equivalent that does not infringe, or refund the fee that you paid for the code in question.

Both indemnity duties rely on the principle of fair notice. The party seeking protection must tell the other promptly about a claim, must let the other control the defense where the law allows, and must cooperate sensibly. A failure of timely notice relieves the defending party only to the extent that it was actually harmed by the delay.

14. Suspension and termination

Either side may end an engagement through the notice procedure written in the engagement letter. Where the letter is silent, either side may end the engagement by giving thirty days written notice. Work that was performed up to the end date is paid for, and deliverables that were completed are handed over as far as the rules of ownership allow.

We may suspend work, on notice, where payment is overdue, where you ask for changes that are unlawful, or where you fail to provide the access that the work needs over a sustained period. Suspension is a pause and not a cancellation; it gives both sides a chance to clear the obstacle and restart the schedule.

These terms include the paragraphs that by their nature survive an end to the project, such as the sections on confidentiality, on limitation of liability, on ownership, and on the governing law of the agreement. Winding down a project does not wipe away the duties that the law and good sense say are meant to last.

15. Intellectual property and third party tools

We respect the work of others, and we ask the same of you. The visual identity of HYHDATA LLC, our page designs, our writing, and our internal methods are our own property. Nothing in these terms transfers to you a right to pass off our brand or our materials as your own.

Where our delivery relies on a third party tool, the license of that tool applies to your use of it. We select open source and licensed components with care, and we hand you a note of the licenses that cover the pieces we deliver so that you can stay compliant with the authors of those pieces.

We also guard the value of our own methods. You may use the outputs of our work freely, but you may not reverse engineer our private tools, our internal templates, or the source of our frameworks in order to rebuild a competing service. The craft that we bring to a project is a living asset that we keep honest and whole.

16. Governing law and disputes

HYHDATA LLC is registered in the United States, and these terms are governed by the laws of that country unless your region applies a rule that cannot be displaced. Anything that a region forbids us to remove remains in force despite the choice of a foreign governing law. We do not pick a law to strip you of a protection that your own law guarantees you.

When a disagreement arises, we prefer an open conversation first. Write to us at mail@hyhdata.lat and describe the concern in plain terms. The large majority of disputes between honest parties are settled by a calm and complete exchange of facts, and we commit to taking every message seriously and replying with substance.

If a conversation does not resolve the matter, the parties agree to try a neutral mediation before any claim is filed in court. Only if mediation does not settle the issue would a claim proceed to the courts that have jurisdiction. Any claim must be brought within the period that the applicable law allows, none of us may claim more than the limits this document describes, and the prevailing party in a dispute may be awarded its reasonable legal fees to the extent the court allows.

For every matter that relates to these terms, the addresses that matter are these: the office at 7533 S Center View Ct Pmb R, West Jordan - 84084-5526, United States (US), the mailbox mail@hyhdata.lat, and the telephone line +14707699578. A message to any of these reaches the people who can act, and we answer with the care that this agreement deserves.