Terms of Service

1. Acceptance of These Terms

By accessing or using this website, by completing the pilgrim register form on the contact page, by responding to our emails or by instructing us to begin work, you accept these Terms of Service. If you do not agree with any part of them you should not use the website and you should not engage us for work.

When you use this website on behalf of any organisation, partnership or company you confirm that you have the authority to bind that group to these terms. If you lack that authority you may browse the public pages, but you should not commit the group to an agreement or to a paid engagement.

You also confirm that you are at least eighteen years old or of the age of majority in your region when you accept these terms on your own behalf. These pages may be read quietly by anyone of any age, but the act of instructing work is reserved to those who can legally make a binding promise.

2. Our Business and the Parties

The operator of this website is NEBULAR BRANDS, LLC, hereafter simply the Company or the We. The visitor, reader, operator or organisation agreeing to these terms is referred to as you or the Client. When the two together we may speak of the Parties.

The Company delivers its work through the service line Nakama Systems & Design, which is developed and managed by the developer known as NebulaBrand. For clarity, every reference in these terms to the services, to the team or to the developer is a reference to work carried out under the control and responsibility of the Company.

3. The Services We Offer

The Company offers computer integrated systems design for operators based in the United States. Within that broad field we provide enterprise systems integration, joining existing platforms so they share information cleanly; custom software architecture, designing the shape of new applications before code is written; and cloud infrastructure design, structuring the hosting so an operation stays reliable and safe.

We also undertake legacy system modernisation, carrying older programs forward onto sound foundations; data pipeline engineering, moving and shaping data so decisions can be made on good evidence; and IT service management platforms, setting up the tools a team uses to run its own technology well. The full set of services is described on the services page.

Each service follows a similar but honest pattern. We listen to understand the real world of an operation before any tool is chosen. We design with the future in mind so that a solution does not expire the day after it is planted. We build in visible stages so the Client always knows where a project stands. And we remain near at hand to help an operation keep running well after delivery, because a system that works on paper and fails in practice helps no one.

4. No Legal, Financial, Medical or Security Advice

Our pages describe technical work. Nothing on this website is legal advice, financial advice, medical advice, or a guarantee of absolute security. Every engagement is unique, and any estimate we give is based only on what you shared with us at the time.

If your project touches a regulated matter such as healthcare records, payments, government filings or contracts of high value, we will point you to professionals who can advise you properly. We will be glad to build the technical part, but responsibility for the separate professional opinion stays with the advisor who gives it. Where a note at first glance concerns us but truly concerns another adviser, we will say so plainly rather than quietly hold a message we cannot serve. A clear and honest first reply is the quickest kindness we can offer any visitor, whether or not that visitor ever becomes a Client.

5. Accuracy of Information You Provide

When you send us a message, a brief or any material about your operation, you agree to describe it honestly. You warrant that the information you share is accurate to the best of your knowledge, that you own it or have a right to share it, and that it does not break any obligation you owe to another person.

If you later discover that something you sent was wrong or out of date, you agree to tell us as soon as you can. Our scoping and our estimates rely on what you tell us, and a false beginning can lead a project astray in ways that help no one.

6. Enquiries and the Pilgrim Register

The contact page carries a pilgrim register form for your name, email, subject and message. By sending that message you ask us to consider your enquiry and reply to you. Sending an enquiry does not create a binding contract for services. A contract begins only when both Parties sign a written proposal or otherwise exchange clear acceptance of a scope and a price.

We treat every enquiry with discretion. We ask that you keep messages professional and that you do not include passwords, secret keys or sensitive personal data in a general enquiry. For deep confidential detail a secure channel will be opened once an engagement is agreed.

7. Proposals, Scopes and the Written Agreement

Before any paid work begins we prepare a written proposal. That proposal names the services, the deliverables, the schedule, the fees and the assumptions on which the work stands. Only when you accept that proposal in writing do we treat an engagement as agreed.

We recommend a scope of work that records in plain language what is included and what is left for a later stage. Where the scope leaves a decision open, the decision will be made by the Client in reasonable good faith or, failing that, by the Company in a way that protects the shared goal of a sound result.

A written agreement also guards against a drifting memory. Weeks into a busy project a note on a phone can stand for something larger than it ever was, so having the real scope on paper lets both Parties look back with confidence rather than argue over a faded guess.

8. Fees, Invoicing and Payment

Fees for each engagement are stated in the proposal before work starts. We invoice at the milestones named in the proposal. Payment is due within the period shown on the invoice unless the proposal says otherwise. Late payment may pause active work while we wait for settlement.

All fees are stated in United States dollars unless the proposal clearly says otherwise. Where a payment is missed we may charge a reasonable late fee permitted by law. We do not hide charges. If a legitimate extra appears and no agreement covers it, we will raise the matter openly before invoicing. Each invoice names the work it pays for so that a reader can see what a sum covers rather than facing a mystery charge at the foot of a sheet.

9. Access to Accounts and Systems

To deliver a project we may need access to certain accounts, repositories, servers and tools belonging to the Client. You agree to provide that access in good time and to keep it available for the working hours the project needs. You agree to let us know the moment any credential we were given should no longer be used.

Where we act on behalf of a Client, our access is limited to what the project reasonably requires. Any access we hold that is no longer needed will be revoked at the end of the engagement or sooner if you ask us to close it down.

10. Delivery, Testing and Acceptance

We aim to deliver each stage on the schedule set in the proposal. A deliverable is treated as accepted when the Client confirms it works for the purpose described, or after a reasonable review window passes without the Client raising a written fault, whichever comes first.

Testing is an honest collaboration, because the people who live with a system every day see faults that a builder cannot easily imagine. We test what we build, and we rely on the Client to test the result in the real setting of its own operation. Neither Party expects the other to see every edge case instantly, so the review window exists exactly to give both sides a fair chance to look carefully.

11. Changes During an Engagement

Projects sometimes change course as people learn more. When the Client asks for a clear change of scope we will treat it fairly: we will note what it replaces, describe any effect it has on schedule or price, and continue only after the Client agrees.

A small adjustment made during normal delivery, such as a better label or a corrected field, is absorbed by the team. A large change that rearranges the architecture is a new scope, and it is priced and scheduled on its own. This keeps every engagement honest and avoids surprise at the end of a project.

12. Ownership of Deliverables

Upon full payment, ownership of the finished deliverable produced for the Client passes to the Client. That means the specific code, configuration, documents and designs we created for that engagement become the property of the Client, ready for the Client to run and maintain.

We keep the right to reuse our general knowledge, our patterns and our standard methods that are not unique to the Client. Nothing in an engagement hands over our internal tools, our pre-existing libraries or the skills of our people, none of which leave the building when a project concludes.

13. Intellectual Property We Retain

All content made publicly available on this website, including the written copy, the visual identity, the drawing of the gatehouse, the station illustrations and the overall presentation of the shrine-approach theme, belongs to the Company. Together with the marks of our service line they may not be copied for a competing purpose without our written permission.

Open source code that we include in a project remains under its own licence, and we honour the terms that came with it. Where we include third-party material we pass on whatever credit its licence asks us to give.

14. Confidentiality

Both Parties agree to keep confidential any non-public information they receive from the other, whether that is a plan, a figure, a credential, a working image or a message marked or understood as private. Each Party will protect the other secret with the same care it uses for its own.

Confidentiality does not block the Company from describing a completed engagement at a general level, for example by naming the type of work and the region served, without exposing the Client secrets. Where the Client prefers complete silence about a project, it only needs to say so and we will honour that wish.

15. Warranty and Limits of Liability

We warrant that the work we deliver is carried out with reasonable skill and care and that it works for the agreed purpose. We do not warrant that any software is entirely free of faults, because no serious engineer makes that promise about anything built by people.

To the fullest extent allowed by law, the total liability of the Company for any claim connected to this website or to an engagement will not exceed the fees the Client paid to the Company for that specific engagement. By choosing the lowest ever fee as the ceiling we keep the figure predictable for both sides.

16. Disclaimer of Indirect Damage

Neither Party will be liable to the other for indirect, incidental, special or consequential damage, including lost profit, lost revenue, lost data or interruption of business, arising out of an engagement or out of the use of this website, even where the Party has been warned that such damage might occur.

This limit is balanced: it protects the Company from enormous claims built on a small fee, and it protects the Client by keeping the engagement affordable in the first place. Nothing in this section limits liability that a court will not allow a party to waive, such as liability for fraud or for injury caused by negligence. When doubt ever exists about how a clause should be read, we prefer the reading that keeps the promise fair to both Parties.

17. Suspension and Cancellation

Either Party may end an engagement on written notice where the other Party breaks a material term and does not repair the breach within a reasonable period after being asked. We may suspend active work if a payment is significantly overdue and unresolved.

When an engagement ends, the Client pays for the work completed up to the date of ending, and the Company hands over the finished parts of the deliverable that were paid for. Neither side owes the other a penalty for ending a project that is no longer serving its purpose.

18. Governing Law and Disputes

These Terms of Service and any dispute connected to them are governed by the laws of the State of Utah and, where the subject allows, of the United States. The Parties submit to the exclusive courts of Utah for any dispute that cannot be settled amicably.

Before either side begins court proceedings the Parties agree to attempt a good-faith resolution, normally through written dialogue or a single facilitated conversation. Most disagreements between careful people resolve at that first calm table; the courts remain as a last, formal resort.

19. Changes to These Terms

We may revise these Terms of Service from time to time. When a future version becomes necessary we will update the date at the top of this page. Continued use of the website or of an ongoing engagement after the change takes effect counts as acceptance of the revised terms.

For a current engagement, the version in force when the proposal was accepted governs that project. Reading this page from time to time keeps you informed, and a specific question about a clause is always welcome by email to help@nakama.lat.

20. Contact and Address Block

Questions, written requests and notices under these terms should be sent from our home page, posted to the registered address or emailed to help@nakama.lat. You may also telephone us at +16165805386 during published hours.

For the avoidance of doubt the full company name and address are: