1. Agreement to These Terms
These terms of service form an agreement between you and INCA POTATO LLC, the company that owns and runs this website and that offers system integration and software work under the terrace badge shown at the top of the page. By accessing incapotato.buzz, by browsing its terraces, by sending a message through its watch hut form, or by asking us to quote for work, you accept these terms and agree to be bound by them.
If you use this website or these services on behalf of a company, a partnership, a government office, or any other body, the words you and your extend to that body as well as to the person clicking. You promise that you have the authority to bind that body to this agreement, and that body shares the promises you make here.
If you do not agree with any line below, the honest course is to close the page and not to use the services. Nothing in these terms is compulsory reading against your will; a hillside walk remains a choice. When you stay, the agreement is live, and we both carry it.
2. Who We Are
INCA POTATO LLC is a limited liability company organised and operating under the laws of the State of Utah, United States of America. Our principal street line and postal line is 11444 S 150 E, Draper - 84020-9481, United States (US). Our electronic mail line is ask@incapotato.buzz and our telephone line is +17302070421.
The graphical identity and code of this website were cultivated by the developer IncaPotato, who works within the walls of the Company. Every promise that INCA POTATO LLC makes in these terms, the developer keeps as part of the same team. The Company stands behind the work, the invoices, and the warranties set out below.
Where these terms use the words we, us, or our, they mean the Company and its people. Where they use the words you or your, they mean the person reading or the organisation that person represents. Where the text names both the client and the Company, the two together are called the parties.
3. Using This Website
We grant you a personal, non exclusive, revocable permission to visit this website and to read, download, and print the pages for your own lawful purposes. The permission does not include scraping the site wholesale, reselling its text, running automated harvests of its content, or building another product on the back of our copy without a written licence.
The website is a doorway to our services rather than a machine that performs them. Reading a terrace page does not create an employment, agency, or partnership relation between you and us, and it does not promise that any particular service is right for you until a real conversation has taken place.
We work to keep the site up and honest, but we do not promise that it is free from error, that it never falls, or that a page shown today will look exactly the same in five seasons. The site is provided as it stands at the moment you visit, subject to the warranty limits set out later in these terms.
4. Acceptable Conduct
You agree to use this website and our services for fair ends only. You will not try to damage the hillside: no probing for holes, no flooding a terrace with requests, no attempts to read another visitor mail, and no software that causes the slope to slip under weight it was not built to carry.
You will not post anything through our forms that is unlawful, defamatory, obscene, or that carries malicious code. You will not use our channels to send spam or to impersonate another person or an office that is not yours. A watch hut is a small room; a flood of nonsense is not welcomed there.
You will not resell, mirror, or frame the content of this website in a way that misleads visitors into thinking a third party owns it. If you want to quote a short passage with credit, do so; if you want to rebuild the hill for your own shop, ask first for a written word.
5. Intellectual Property
The authors of this website hold, or lawfully use, every right in the content that renders on its pages. That includes the text, the terrace design, the colour scheme, the written field prose, the drawn stair glyph, the layout, and the code that drives the forms. Copyright, trade mark, and design rights live on this hillside as surely as they live in any workshop.
INCAPOTATO and INCA POTATO LLC are the marks under which the Company trades. You may not use either mark, or the terrace badge, to suggest that you or any outside party are us, or that we endorse your products, unless we have given a written licence to do so.
Work we deliver to you under a signed project has its ownership agreed in that project statement. Where a statement is silent, a sensible default is that we grant you a licence to use the deliverable for the purpose we built it, while we keep the underlying tools, libraries, and reusable methods we developed before or beside your terrace.
6. How We Engage for Work
A conversation on this website does not by itself start a project. Work begins when two honest events happen: you accept a written scope that names the deliverable and the price, and the Company accepts that scope by signature, by sending a statement, or by starting the work you expressly approved. We prefer a simple one page statement over a monument of clauses.
Each project statement names the terrace we will climb, the walls we will raise, the channel we will grade, the schedule we aim for, and the fee in plain currency figures. Where these terms and a written statement conflict, the statement wins for the project it governs, because it was written for that ground alone.
We work with clients across the United States and, where practical, beyond it. A call with you, or a visit to your site, is part of many projects, and any travel or third party cost is named before it is owed rather than surprised on an invoice.
7. Scope and Change Control
The scope is the agreed edge of the field. We build to that edge and we do not quietly step past it, because a wall that wanders is a wall nobody paid for. If, during the work, new ideas surface, we welcome them as leads for a change note rather than as silent additions to the price.
A change note is a small written agreement that sets out the new work, the effect on the schedule, and any adjustment to the fee. Neither side is obliged to accept a change. You may refuse a change that swells the budget, and we may refuse a change that would shear the quality of the whole terrace.
Where a requested change makes earlier work obsolete, the cost of that earlier work is settled fairly in the change note. We do not charge you twice for the same stone; we account for what actually had to be re-cut because the field was redrawn mid season.
8. Fees and Payment
Fees are set out in the project statement in clear figures so you can read them in the light of day. Unless a statement says otherwise, sums are due in United States dollars, by bank transfer or by a payment card we accept, and they are payable without set off or counterclaim.
Many of our engagements use a simple rhythm: a starting payment that secures the terrace, then further payments as described in the statement as each wall is witnessed. A smaller piece of work, such as a single audit or a one day read of a field, is often settled on completion with a single invoice.
If a payment falls late, we may pause work on the terrace until the account is level, and we may add a late fee at a fair rate that the statement names or that the law allows. We never surprise you with a charge that was not written; a surprise is a bad crop in any season.
9. Taxes
Quoted fees are exclusive of taxes unless a line says they are inclusive. Where a levy applies, such as a United States sales or use tax, a State of Utah levy, or a value added tax in a country that uses one, you agree to pay or reimburse the amount that the law lays on the service.
We each carry the taxes of our own pocket. The Company pays the taxes on its own earnings and its own staff, and you pay the taxes that the law puts on your side of the transaction. Where the law asks us to collect a tax from you, we collect it and pass it to the authority, and we give you a receipt that shows the line.
Tax rules change and can cross into double counting. If you believe a levy was wrongly added, send us the supporting paper and we will review the line with you honestly, adjusting where the law allows and explaining clearly where it does not.
10. Schedules and Delivery
Every statement carries a schedule, and we treat that schedule as a promise we intend to keep. We build in a margin for the ordinary snags of software work, but we do not use that margin as a licence to drift. If we see a risk to a date, we tell you early rather than late.
Delivery of code or a design often happens by an electronic handover: a repository, a package, a document bundle, or a set of credentials that place the work in your hands. On delivery we give you a pointer to confirm receipt, and the clock for your review should start then.
A schedule can slip for reasons on your side, such as a late decision or missing access. Where that happens we note the delay openly and we carry the remaining work on a revised date that we agree together, without turning the honest note into a blame poster.
11. What We Need From You
A terrace is built in partnership, and the partnership needs a few things from you to thrive. We need a named contact with the authority to make decisions and answer questions promptly, because round trips in a project are measured in days, not in hopes.
We need honest access to the systems that matter to the work, or access to someone who can describe them truly where courtesies do not allow direct keys. We need your review of each interim deliverable within the window we agree, so a misstep is caught while it is still cheap to mend.
If you withhold a decision, an approval, or an access that the work needs, the schedule moves by the days you held it, and we are not accountable for a slip that your hold caused. We do not say this to lean on you; a shared hill moves faster when both hands pull.
12. Quality and Acceptance
We build to a decent professional standard, meaning the work behaves as the agreed scope says it should, through the ordinary use and under the ordinary load its own field produces. We test what can be tested, we review code as a craft, and we hold a design review so a wall is checked before it is trusted under water.
When a deliverable is ready, you receive it for acceptance. Acceptance means you have looked at the work against the scope and you find it fits, or you have had a fair and stated window to look and raised nothing. A reasonable window for acceptance is set in the statement or, failing that, is fourteen days.
If a defect appears during your acceptance window, we fix it without drama and without a separate fee, so long as the defect is a real gap between the delivered work and the agreed scope rather than a new wish born after the wall was built. New wishes are change notes, as an earlier section describes.
13. Warranties and Disclaimers
We warrant to you that we will perform the work in a workmanlike manner, with reasonable skill and care, and that the deliverable we hand over will, for a period that the statement names or that a sensible default of ninety days gives, match the agreed scope under the intended use.
Beyond those promises, the law often lets a provider disclaim the quieter warranties, and we make that disclaimer plainly. Unless a statement says otherwise, the site and the services are given to you as is, without any warranty of fitness for a purpose you never told us about, and without a promise that the code is perfect for every machine ever made.
A custom software build interacts with your own systems, data, and users, which we do not wholly control. After acceptance and after any warranty period, we are glad to keep helping under a support line, but the warranty edge and the well of ongoing support are two different fields, and we keep their stones apart.
14. Limits on Liability
To the extent that the law allows, the total liability of INCA POTATO LLC for any claim that arises out of these terms or out of a signed project is capped at the amount you actually paid us for the piece of work that gave rise to the claim, or a fair portion of that amount, whichever the statement sensibly sets.
Neither side is liable to the other for indirect, incidental, or consequential loss, such as lost profit, lost goodwill, lost data recovery, or interruption to a business that rides on the deliverable, unless a written statement expressly says otherwise in bold and clear words.
These limits do not apply to a harm the law will not let us cap, such as cases of willful misconduct, fraud, or a duty that is yours by operation of law. We do not ask you to sign away more than the law permits; we ask only for a fair edge, so a small engagement does not carry an unmeasured cliff above it.
15. Confidentiality
During a project, both sides learn truths the other would rather keep out of the town square: your business figures, our methods, your roadmap, our fees. Each side agrees to keep the confidential information of the other secret, to use it only for the project, and to show it only to people who need it and are bound to the same secrecy.
Confidential information does not include a truth that is public of its own accord, that you knew before we met, that you gain lawfully from a third party, or that you are ordered to disclose by a court. If a court orders disclosure, you give the other side notice so it can guard what it can.
We often share the plain name of a terrace we have tended as a reference, but we do not publish your sensitive figures without your written consent. We welcome you telling the world about the work; we only ask that we both read the fine print before the flag is waved.
16. Data and Security Duty
You keep ownership of the data that your own systems hold, and the work we deliver does not take that title from you. Where data crosses our hands for a service, we treat it under the confidentiality duty above and under the terms of any signed project that names a data handling rule.
We will apply reasonable security to any data we process for you, and we will route any claim that touches personal information toward the privacy policy published on this website, which describes our duties as clearly as any separate sheet could.
You are responsible for the lawfulness of the data you feed us and for the conduct of your own users. If you load a system with content that breaches a law or a third party right, that fault is yours, and you agree to carry the ordinary consequence rather than to hand the problem to our wall alone.
17. Termination
Either party may end a signed project by the terms of its own statement, or, where the statement is silent, on written notice with a fair working through of the work already done and an honest settlement of the fees that the done work has earned.
Either party may end this website agreement at any time by simple notice, and the general terms then stop applying to future visits, though the sections that guard ownership, confidentiality, liability, and law continue to guard the ground already crossed.
We may end a project at once if you fail to pay a due sum after a written warning, if you breach a material duty and do not mend it within a stated window, or if your conduct makes honest work impossible. Ending is not spite; it is the terrace equivalent of closing a channel that floods the field.
18. Suspension of Service
Where we host or maintain a running service for you, we may suspend it temporarily to protect the slope: for urgent security patches, for a fault that endangers other clients, or when we are ordered to by law. A temporary suspension is announced as far ahead as good sense allows.
Scheduled maintenance, such as a planned quiet window for a backup or a platform upgrade, is chosen for the least harm to your work and is announced in good time so you can plan around it. A terrace may rest by night, but it does not vanish while you are trying to harvest.
If a running service must be suspended for a long reason on your side, such as an unpaid overdue balance or a breach, we explain the path back to green so you are not left guessing how to reopen your own field.
19. Third Party Tools
A modern build stands on the work of others: a cloud platform, a hosted database, a code library, a messaging service. When we use a third party tool in your work, we choose reputable ones, but we pass on to you the justice and limits of that provider, and we tell you which tool a deliverable leans on.
Some third party tooling has its own terms of use that bind you directly as its user, such as a cloud account you open in your own name. We will point you at those terms where they matter, and we ask you to read them, because a licence we cannot give you is a licence only its owner can grant.
We do not secretly swap one provider for another to save a coin at the cost of your trust. If a supporting tool matters to your availability or your price, we name it and we give you a say in the choice before the wall is cast.
20. Our Product and Service Standards
INCA POTATO LLC does not sell every kind of software under the sun. This Company specialises in computer integrated systems design for operators in the United States: enterprise systems integration, custom software architecture, and cloud infrastructure design, together with the support work of legacy modernisation, data pipeline engineering, and IT service management platforms.
We measure a product against the standard that the terrace it serves truly needs. A hospice scheduling screen and a logistics ledger can both wear the word software, yet they ask the walls questions of a very different weight, and we do not pretend one answer fits both fields.
Because our craft is rather a roof than a bolt, we take pride in the plainness of our handover. You should emerge from an engagement able to run the terrace without a daily call to us, with documents that a new engineer can read in a year and still follow the water.
21. Export Rules
Software and the services around it can sit inside export rules that the United States and other governments set. You agree to use this website and any deliverable in line with those rules, and not to send a deliverable, a licence, or source to a place or a person that a governing restriction forbids.
We do not ship services to a user under a United States sanction that bars it, and we will ask for the plain detail we need to satisfy ourselves on the rare day a client origin is unclear. Honesty about your home field is an early stone of trust.
If an export rule stands between us and a piece of work, we stop rather than bend, and we say why. A good wall can wait a season for permission; a cracked gate gives trouble in every season that follows.
22. Governing Law
These terms and the work they govern are read by the law of the State of Utah, United States of America, without giving force to any rule that would turn the choice to another court. Utah has a mature body of commercial law, and it is a home the Company knows well enough to stand before fairly.
The federal law of the United States also reaches the parts of this work that touch copyright, trade marks, and internet conduct, and it applies alongside State of Utah law where the two meet. Where a State of Utah rule and a federal rule disagree, the higher court of the two speaks louder for the matter it owns.
Choosing Utah law does not pull you into any court you could not otherwise reach; we simply ask that disputes find one steady address rather than being fought in half a dozen places chosen for advantage on a given week.
23. Dispute Resolution
Our first preference is that a dispute never reaches a courtroom at all. Before either party files a claim, that party will give the other a written note of the issue and a fair window, usually thirty days, to resolve it by a straight conversation over a call or a meeting.
If a dispute survives that window, the parties may agree to bind it to a confidential mediation before a neutral the two of them choose, sharing the cost of the mediator in equal halves. Mediation is not a trap; it is a parked bench where two farmers look at the same crack in the wall before deciding who brings the mortar.
Where a dispute must go to court, the parties consent to the exclusive jurisdiction and venue of the state or federal courts that serve the State of Utah, and each party carries its own costs unless the court awards them to a prevailing side under the law. A claim of any kind arising from this site or a signed project must be started within two years of the event that gave rise to it, or it is barred.
24. Force Majeure
Neither party is in breach for a failure to perform that a cause outside its reasonable control brings on, so long as the cause is real and the failure is not of the party own making. Such causes include severe weather, a declared epidemic, a general power loss, a war or riot, a strike beyond the party own staff, and a failure of a public network that neither side owns.
Where such a cause strikes, the party affected will tell the other as soon as it can and will take reasonable steps to soften the harm, such as moving a working terrace to a safe room or finding a lawful alternate channel for the water.
If the cause runs on beyond a fair season, either party may end the affected project by written notice with a fair settlement of the work already done, so that neither side is chained to a hill that will not wake.
25. Entire Agreement
These terms, the privacy policy published on this website, and any signed project statement together hold the whole of the agreement between you and us about the matters they cover. They replace any earlier talk, note, or draft that conflicts with them, and no side may point to a promise that lives only in a spoken corridor.
If a court finds one line of these terms unenforceable, the rest of the terrace stands, because a single loose stone need not bring down the entire wall. The unenforceable line is trimmed to the smallest edge the law will hold, and the remaining terms carry on in full force.
A failure to press a right on one day is not a giving up of that right for every later day. Our silence should never be read as a quiet surrender of a term that matters to the health of the slope.
26. How to Reach Us
All notices about these terms, about a project, or about a request for work should reach the Company by one of the roads that always works. Electronic mail to ask@incapotato.buzz reaches a real bay, and a written letter to INCA POTATO LLC, 11444 S 150 E, Draper - 84020-9481, United States (US) reaches the bench in good time.
You may also telephone us at +17302070421, Monday to Friday, 9am to 5pm Mountain Time. If you are closed off the hours, leave a clear message with a return line and we will call you back within one working day, because a wall is not truly finished while a voice is left unanswered on its far side.
This page, like the hill itself, was built and is tended by the developer IncaPotato working for INCA POTATO LLC. Should a point of these terms ever read as fight to you rather than as fence, write to us and we will hear you out in the same plain voice that wrote the words, because agreement is a terrace each side plants and waters together.
Thank you for reading to the final stone. We look forward to climbing the slope with you, and to raising a terrace that holds its wall in the season and the storm to come.