These terms of service govern the relationship between you and the provider NUHUEMAN, L.L.C., whose office is at 215 N Quince St APT 12, Salt Lake City - 84103-4569, United States (US). The phone number of the provider is +13313139264 and the contact email is update@nuhueman.mom. Reading these terms is recommended before you place an order, sign a proposal or hand material to the crew.
By continuing to use this website, by sending a flight log form, by asking the crew to quote for work, by signing a proposal or by accepting any deliverable, you agree to be bound by the parts of these terms that concern your action. If you act for a company, a partnership, a trust or another legal body, you confirm that you have authority to bind that body and that these terms then apply to it as well as to you personally.
If you do not accept these terms, please do not send material into our systems and do not commission our work, because every conversation builds on this shared text. We are a small, senior team and we prefer an early, clear agreement about boundaries over a late, messy one. These terms are written so that a new relationship starts with the important things already settled and the small things easy to discuss.
NUHUEMAN, L.L.C. is the provider named at the top of this page and the entity that delivers the engineering and consulting services described across the site. The company is organised under the laws of the State of Utah and its posted office address is 215 N Quince St APT 12, Salt Lake City - 84103-4569, United States (US).
Statements made on the site about capabilities, past work and approach are honest descriptions of what the company does and are not, on their own, a binding promise of a specific result for your particular case. Binding obligations arise only inside a written proposal, a signed statement of work or an order that both parties accept, because that is where the shape of a specific engagement lives.
The site describes a family of services that we can provide: enterprise systems integration, custom software architecture, cloud infrastructure design, legacy system modernisation, data pipeline engineering and IT service management platforms. Descriptions on the site explain the philosophy behind each service; they are not, of themselves, a quotation for your own situation.
An order is formed only when the crew and your organisation agree in writing on the scope, the price, the timeline and the acceptance criteria. That agreement may be a formal contract, a signed statement of work or a clear email exchange that both parties treat as the record. Until such an agreement exists, neither party is committed to deliver or to pay, and either side may walk away without penalty. Any work we do free of charge, such as an early discovery conversation, is provided to help us both decide and never creates a duty to proceed.
A quotation is valid for the period written on it, or for thirty days if no other period appears. We base each quote on the scope we can see at the time. When new facts surface during an engagement, such as a missing data source, a previously hidden system or a change of direction requested by your side, we raise that promptly and we price the change separately rather than folding surprise cost into an old figure.
Neither side should treat a proposal as frozen photography. A useful proposal is a live map. We track changes in a written log, we agree them in advance and we keep both parties understanding the number and the reason at every step. Unapproved changes are our liability to notice and your liability to request clearly, and together we keep the record honest so that no invoice ever surprises a reasonable reader.
Fees are stated in the proposal and invoiced on the schedule that the proposal holds. Unless we agree otherwise, a discovery and design stage may be invoiced at its start, and a build stage is invoiced on completion of agreed milestones. All stated amounts are payable in United States dollars unless a different currency is agreed for a specific engagement.
Payment is due within the number of days shown on the invoice, usually thirty. If payment is late we may pause active work after reminding you, and we may charge the modest late fee permitted by law or by the proposal, whichever is lower. Late payment by one party never excuses the other party from the obligations it still owes under the agreement, and we will always discuss a payment difficulty rather than let a conversation become a dispute.
NUHUEMAN commits named, senior people to the work you have agreed. If a key person becomes unavailable, we will propose a replacement of equal seniority and we will let you approve the swap before your project stalls. Our team works alongside your own people rather than above them, because software that your staff cannot understand is software that will not long survive the crew leaving.
For our part to succeed, you agree to give timely answers, to name a single decision contact who can speak for the business, to give reasonable access to the systems and records that the work genuinely needs and to keep that access lawful and unblocked. If your side delays an answer, a review or an approval, the schedule moves accordingly and we will say so plainly when it happens, not at the end of the project.
Each agreed deliverable has known acceptance criteria captured in the statement of work. When we hand a deliverable to you, you receive a reasonable window, usually ten working days, to test it against those criteria and to raise defects in writing. We then fix confirmed defects within an agreed period and hand the corrected version back for a closing review.
Acceptance is not a trap. If you put a deliverable into live service, or if you fail to raise a defect within the review window, we treat the deliverable as accepted on the facts. Minor, cosmetic differences that do not affect function do not block acceptance, and neither do requested changes that lie beyond the agreed scope. Acceptance of one stage does not bind the next, because each stage is judged on its own terms.
The ideas, processes and components that NUHUEMAN brings to an engagement and that we developed before you arrived, our general methods, our internal tooling and our ways of working remain the property of the provider. In return, everything that we create specifically for you under the engagement, the code, the designs, the documents and the configuration, belongs to you once we are paid in full, unless the proposal says something different for a particular item.
Ownership passes only on payment, and we transfer what we lawfully can without imposing a tangle on your business. We take care not to reuse your private solutions in the work we do for another client, and we expect the same courtesy in return: you will not claim our general methods as solely your own or block us from applying the craft we practiced before we ever met you.
Where an engagement delivers open or internal software, we grant you a perpetual, royalty free, non exclusive licence to use, modify and run that software for your own genuine business purposes. This licence is broad because your business bought the software to use it, and we do not want a legacy licence to throttle a tool your team depends on.
The licence does not give you permission to rebrand the software and sell it as your own competing offering, nor to resell it wholesale to a stranger, because that would take the value of a custom job beyond the click of a contract. If you plan to redistribute a component broadly, tell us during planning and we will build the licence terms deliberately instead of patching them later.
Much engineering rides on third party software: libraries, platforms, cloud services and tools that other parties own. Their licence terms govern our use of them, and we pass those terms through to you in our documentation rather than pretending a third party term is our own invention.
You acknowledge that the availability, price and roadmap of a third party product sit partly outside our control. If a platform we depend on changes its terms or shuts a service, we will react sensibly, we will let you know and we will treat the required adjustment as a scope change that we plan together, not as a breach by either of us. Where the data of your customers flows through such a service, we work only with providers that hold themselves to a respectable security and privacy standard.
During an engagement each side will see material the other treats as confidential: business plans, financial figures, system credentials, customer records and private design notes. Confidential information stays confidential. Each side agrees to use the other material only for the purpose of the engagement and to protect it with care at least equal to the care it uses for its own similar material.
Confidential information does not include material that is already public when received, that later becomes public through no fault of the receiver, or that the receiver already lawfully held. If a law or a regulator demands disclosure of confidential material, the receiving side will give prompt notice where legally possible so that the owner can object. This duty of confidence survives the end of the engagement, because a secret learned in confidence does not lose its nature when a project closes.
NUHUEMAN warrants that the work we deliver will be performed with reasonable skill and care and will meet the agreed acceptance criteria. We also warrant that we have the authority to perform the engagement and that the work we create for you will not, to our knowledge, infringe a third party right where the material originated from us.
Beyond those warranties, and to the extent allowed by law, we provide the services and this website as they are, without further promises. We do not promise that any system will be free of every fault, that a specific business outcome will follow from a technical change, or that third party components will behave perfectly forever. Any warranty claim must be raised in writing within a reasonable period after you discover the issue, so that the problem is addressed while the facts are fresh.
Neither party is liable to the other for indirect, incidental, special or consequential loss, such as lost profit, lost revenue, lost data or interruption of business, that arises from an engagement, even if the party was told that such loss was possible. This is a shared and fair boundary: software work affects real business, and both sides carry risk, so we divide that risk rather than ask one side to bear it all.
Where we can lawfully do so, the total liability of NUHUEMAN for any claim that arises out of an engagement is capped at the amount actually paid to us for the stage of work from which the claim arises. Nothing in these terms excludes liability that cannot be excluded by law, such as liability for fraud or for death or injury caused by negligence. If one of our promises is found void because it is too broad, it will be read down to the widest extent the law allows.
Delivery dates we quote are best estimates made in good faith from the information available at the time. Events that no reasonable party could have predicted, such as a failure of a third party service, a natural event, a legal restriction or a serious illness in the crew, may delay the schedule without making either party liable for the delay.
When such an event occurs, we will tell you as soon as we know and we will agree a revised date. Neither side uses an unforeseen event as a free pass; the party facing the event makes reasonable efforts to limit its effect and to keep the rest of the plan moving. If a delay becomes so long that the purpose of the engagement is lost, either side may end the engagement on fair notice and pay only for the work already reasonably done.
Either side may end an engagement for a material breach that the other side has failed to fix within a written notice period, usually of fourteen days. A material breach includes a failure to pay an undisputed invoice, a failure to deliver the agreed scope, or a serious breach of confidence.
If an engagement ends early, you pay for work properly completed up to the point of stopping, and we hand over any deliverables you have paid for together with the materials needed to continue the work elsewhere. Ending a relationship should be as courteous as beginning one: we want you to succeed after we part ways, because a client who flies well speaks well of the crew that first taught them the air.
You agree to use this website lawfully and considerately. In particular you will not try to break into parts of the site that are not yours, flood the site with excessive traffic, probe it with hostile automation without our consent, or use it to send harmful code or misleading messages.
We welcome honest feedback, respectful criticism and pointed questions. We do not publish offensive content on these pages and we will not tolerate an attempt to use our site as a platform for abuse. Reasonable use of the whole site, including the flight log form, is free and open to any genuine visitor; misuse will draw the simplest remedy that fits, from a polite warning to a block where behaviour justifies it.
Where you ask us to build, host or maintain a system, we bring the discipline of a flight crew: least privilege access, monitored change, tested backups, timely patching and a plan for the day things go wrong. We will never promise absolute security, because no honest engineer does, but we will practice the craft of making a breach unlikely and a recovery quick.
You agree to keep for yourself the parts that only you can guard: the care of your own accounts, the training of your own people and the honest reporting of any incident you become aware of. Security is a shared rope. If we each hold our end firmly, the whole craft is steadier than either of us could hold alone.
These terms are governed by the laws of the State of Utah, without regard to conflict of law rules that would point elsewhere. This does not reduce any consumer protection right that cannot be waived by agreement in your place of residence.
The parties agree that the courts of the State of Utah and the federal courts that sit within that state have exclusive venue for any dispute arising from these terms, except where a different venue is required by law for a particular consumer. Before either side starts an action, both agree to try, in good faith, to resolve the matter through a direct conversation, because nearly every problem we have seen between an honest client and an honest vendor was solvable at a table before it needed a courtroom.
These terms, together with any signed statement of work or accepted proposal, form the whole agreement between the parties about its subject and replace any earlier discussion about that subject. A term may be waived only in writing, and a party giving a concession on one occasion does not lose its right to enforce the same term on another occasion.
If a court finds any part of these terms void or unenforceable, that part is severed and the rest of the terms continue in full force as if the void part had never been written. A heading in these terms is a label for convenience and does not change the meaning of the clause it names. The sections that are meant to survive the end of an engagement, such as those about ownership, confidentiality and limits on liability, endure for as long as their subject requires.
All notices and legal correspondence about an engagement should be sent in writing to the address below, or to the contact method named in our proposal where a quicker path is agreed. We treat the date we actually receive a notice as its effective date, and we respond in good time to any valid notice we receive.
NUHUEMAN, L.L.C.
215 N Quince St APT 12, Salt Lake City - 84103-4569, United States (US)
Contact email: update@nuhueman.mom
Phone: +13313139264
If a question about these terms ever sits between you and a decision, put it to us directly. Questions asked well in advance of a signing save both sides from a misunderstanding later. We would far rather explain a sentence twice than live with a meaning that was never meant.