These Terms of Service form the agreement between you and YI ALGORITHMS LLC, a company registered at 4277 W Watchmen Way, Herriman - 84096-2759, United States (US). By visiting the site, sending a problem note, or asking the bench to begin work, you accept these terms as they read on the day you first engage with us. Where a separate written agreement exists for a named project, that written agreement leads, and these terms fill only the gaps it leaves open.
These terms are written to be read, not to be avoided. If a clause would cost you a fair result, the Company would rather strike the clause at the start than defend it later. If you disagree with any part of these terms, please do not use the site or send project work until we have talked about the difference.
The Company that runs this bench is YI ALGORITHMS LLC. The developer behind the build and support work is YiAlgorithms, the name given to the engineering practice this Company sustains. When these terms say YI ALGORITHMS LLC, we, the Company, or the bench, they mean that registered entity and the people who work inside it under its direction.
The client or you means the company, agency or individual that asks for work or uses the site. Where the client is an organization, the person who sends the enquiry states that they hold the authority to bind that organization to these terms. A single individual accepting terms on behalf of a fleet of many vehicles makes a promise that the whole organization will be read as signed on too.
The bench provides algorithm engineering for operations teams. That broad phrase covers optimization model design, scheduling and routing systems, data pipeline engineering, forecasting and estimation models, simulation and scenario testing, and production integration and tuning. Each of these is a craft task built around a client decision, not a rented website or a hosted dashboard.
Engagements begin as a scoped note and grow into a written plan agreed before heavy work starts. The written plan names the inputs, the expected output, the people who will review it and the measure of done. Work the Company never promised is work the Company should not bill for, so the scope line is drawn early and kept sharp for the whole ride.
An algorithm is an opinion about how to decide, and the bench states its opinion in code and math that a client can examine. Delivered work follows the honest arc of an engineering handoff: assumptions are listed where a reader can find them, bounds are shown for the run, and real data is replayed before a plan reaches the floor. This transparency is a feature of the service, not an afterthought.
The Company refuses to dress a gamble as a guarantee. A solver improves the odds, shortens the search and keeps the answer within your rules, but it does not repeal physics or remove every risk of a bad day on the road. Where a plan rests on a wobbly assumption, the sheet says so in plain ink rather than letting a later surprise fall entirely on the client.
The contact page collects a name, an email address, a subject and a problem note so the bench can answer meaningfully. A visitor promises that the details they send are their own, that they are not misrepresenting themselves as someone else, and that the note describes a problem they are entitled to ask about. Questionable claims are checked before trust is placed in them.
Feedback, questions and suggestions sent to the Company become part of the working conversation. A visitor who sends test files or example routes agrees those samples may be examined for the purpose of answering, and understands that sample data will be handled under the same care described in the Privacy Policy rather than spread beyond the enquiry.
Everything the Company writes, derives, draws and ships for a project belongs to the client once paid in full, except for the shared craft the Company keeps. That shared craft means the general methods, frameworks and practice patterns the Company builds up over many engagements, stripped of any identifying client detail. A solver library is a tool; a specific schedule for your fleet is the thing the terms recognise as yours.
You keep rights over your own trademarks, branding and operational material, exactly as you held them before the engagement. Nothing in this arrangement copies your brand onto the Company or makes the Company a partner or owner of your business. When a contract ends, each side takes back its own and leaves nothing of the other lying around.
This website may be used for lawful, personal and professional purposes only. You promise not to interfere with its running, not to scrape it at machine speed for resale, not to probe its security beyond a reasonable test, and not to post content that is unlawful, threatening or deceptive through any form the site exposes.
The site is a door to the bench, not the bench itself. Content on the site is provided on an as available basis and may change as the Company improves its offering. Small corrections and updated contact details happen without notice; the Company keeps the material lines of this agreement, however, as steady and foreseeable as these words intend them to be.
Fees are set in the written plan for each engagement and agreed before work begins. The bench may bill by fixed milestone, by a fixed rate for defined time, or by subscription for a running production service, depending on what the client and Company decide suits the task. Every price is stated in plain terms so there is no surprise line at the end.
Payment falls due as the plan states, usually on acceptance of a stage or against a regular cycle for live services. Unpaid balances may pause production support until they are cleared, but a pause never erases the client claims over paid work. Tax, where it applies, is added as law requires, and the Company keeps invoices that a finance team can reconcile without decoding.
A deliverable is the concrete thing a milestone owes: a model file, a route run, a pipeline, a forecast report or a running endpoint. The Company delivers each against the measure of done named in the plan, and the client reviews it against that same measure. Acceptance is the moment a stage is judged to meet what was promised, and it should be an honest handshake, not a rubber stamp.
When a delivered stage falls short of a named measure, the Company fixes it as part of the same price rather than charging again for its own miss. Repeated disagreement about whether a measure was met is resolved by returning to the written words of the plan, which both sides agreed were the ruler.
Scope rarely stays frozen once real data arrives, and the bench expects an honest conversation when the world moves. A small refinement that stays inside the original measure is absorbed at no extra cost. A true change of shape, such as a new fleet size, a new decision type or a different output, is priced as its own small plan so both sides agree on the new effort.
Change requests are logged in writing with a note of what the old scope skipped, so nobody later discovers that a cheaper quote covered less than they imagined. Keeping the log short on surprises and long on clarity suits a modelling shop whose whole value rests on being precise about what a plan does and does not include.
Data a client brings to the bench stays that client data. The Company acts as the careful keeper of it for the project, does not claim ownership of it, and returns or deletes it within the agreed period unless a legal hold or a client instruction says otherwise. Depersonalized lessons may be shared, but raw client records never cross to another client.
At the end of an engagement the client may ask for a clean copy of the records the Company holds on its behalf, and the Company provides that export in a useable form. After the agreed retention period the Company removes project records from its active workspaces and keeps only what the written agreement or the law insists must remain.
How the Company collects, uses and protects information is covered by the separate Privacy Policy that sits one page away from these terms. The two documents are meant to be read together, and no clause here is intended to weaken a promise the Privacy Policy makes about care.
For a client engagement the working confidentiality is governed by the written agreement, which may go further than the public Privacy Policy allows. Where the documents differ about what may be done with a record, the more protective rule wins, because the Company would rather surprise a client with safety than with exposure.
The Company warrants that it has the skill to perform the work and will carry it out with reasonable care and diligence, as a careful engineer in the same field would. Delivered models are warranted to behave as described in the plan for the inputs and assumptions the plan names. Nothing more is promised, and nothing is promised forever across a changed world.
On the client side, the warranty is that the information given about the operation is honest and current at the time it is given. A model is only as good as the world its inputs describe; where the client withholds a known hard rule or sends a stale feed, the resulting gaps are not fairly the fault of the derivation.
To the fullest extent the law allows, neither party is liable to the other for indirect, special, incidental or consequential loss, including lost profit, lost revenue, lost data or interruption of business, arising from this agreement. Each side runs its own operation and keeps its own risk, which is the honest shape of a professional services relationship.
Where liability does attach, each side total liability is limited to the fees paid under the specific engagement during the twelve months before the claim. This cap never excuses a wilful wrong or a breach of confidentiality carried out in bad faith. The Company would rather a fair small cap stand clearly than a huge open obligation be argued over for months.
The bench may use third party solvers, cloud compute and mapping or estimation data to do its work. Such tools carry their own terms, and the Company passes on any genuine condition those vendors impose on the data the client sends, in plain words, before the work relies on it.
Where a delivered product calls a third party service on the client own network, the client stays responsible for its own accounts and their limits under those vendor terms. The Company helps wire the integration, checks the keys are handled safely, and flags vendor licenses that a client should renew, but it does not silently assume licensing burden that belongs elsewhere.
Confidential information means the records, plans, strategies and internal facts each side learns from the other that a reasonable person would understand to be private. Both parties keep such information secret, use it only for the engagement, and disclose it only to people who need it to perform their part.
The duty survives the end of the agreement. After a client compares two suppliers, it does not then carry one supplier sheet to another as if it were free, and the bench does not reuse a client layout for a rival. At the close of work each side returns or destroys the confidential records of the other on request, keeping only what law or an audit duty requires.
The public website is served as available on ordinary hosting, with no promised uptime figure beyond a fair effort to keep it reachable during standard hours. Production solvers the Company runs for a client under a separate service agreement carry that agreement specified availability, monitored and reported rather than quietly assumed.
Support hours run Monday to Friday across the office day in the Mountain time zone, matching the bench hours the contact page shows. A live production model under a support agreement receives a faster response lane for failures that stop the client operation, while model improvements arrive on the plan agreed with the client rather than by sudden surprise.
These terms apply from your first visit and continue while you use the site or hold a live engagement. A client may end a project on the notice its written plan allows; the Company may end a project if a client materially breaks these terms and does not fix the break after notice.
On termination the client pays for work genuinely done to that point, the Company hands over the paid deliverables that exist, and both sides return confidential records as section sixteen describes. Ending well matters to the bench, because many of its best clients are the ones who left a prior supplier on fair terms and went looking for someone clearer.
These terms and any engagement built on them are governed by the laws of the State of Utah in the United States, where YI ALGORITHMS LLC is registered and maintains its bench. Where a client law would otherwise apply, the parties agree that Utah law governs the reading of these words so that one clear rule book runs the whole relationship.
This choice does not strip a consumer of the mandatory protections that apply where they live, if any clause here would otherwise collide with a protection the law will not let a contract remove. The Company keeps that reminder so the governing clause is read in its honest, limited sense and not stretched to bully a smaller party.
The best resolution is a calm conversation before anything escalates. If a disagreement rises, the party that notices it writes to the other in plain words, and the two sides spend up to thirty days trying to settle it directly. Most modelling disputes are misunderstandings about what a measure of done meant, and those clear up fast once the original words are put side by side.
Where a dispute cannot be settled directly, the parties first try mediation with a neutral acceptable to both. If mediation does not close the gap, the dispute proceeds to the courts of competent jurisdiction in the State of Utah. Both sides waive a jury where the law allows, preferring a reasoned decision to a lottery.
Questions, notices and dispute letters to the Company go to note@yialgorithms.hair and are answered during bench hours. Formal written notices may be posted to YI ALGORITHMS LLC, 4277 W Watchmen Way, Herriman - 84096-2759, United States (US), and are treated as received when a reply confirms them.
The phone line for the bench is +12408395358. Because an agreement over the phone is hard to prove and easy to misremember, payment and scope changes are confirmed in writing even when a conversation first opens them. That habit of writing things down is the plainest summary of these terms and of how the bench likes to work.