Terms and conditions

Published by KLAIM LIMITED on 5 October 2026. This page is the company’s own statement for this website. It is not a substitute for advice on a particular engagement.

Status of these terms

These terms and conditions are the commercial terms published by KLAIM LIMITED for work commissioned through or discussed from the website at https://klaimlimited.business. The company publishes the address 9 Corbets Tey Road, Upminster, RM14 2AP, United Kingdom, the telephone number +44 7520 619384, and the email address help@klaimlimited.business. This version is dated 5 October 2026.

They apply when a business asks KLAIM LIMITED to carry out custom software programming, computer systems design, cloud or web hosting, web architecture, data processing and analytics, digital advertising or MarTech work, public relations platform work, digital marketing technology, AdTech or media systems work, enterprise API integration, IT consulting, or system maintenance and support. They also apply to a written scope that says these terms govern it.

They are not a substitute for a statement of work. A scope can narrow, sequence, or price the work. If a signed scope expressly changes a clause here, the scope wins for that engagement. If it is silent, these terms fill the gap. The website terms of service govern browsing the site. The privacy policy and cookie policy govern personal data and cookies on the site. A mandatory rule of law prevails over any clause.

The company does not publish a company registration number, a director list, a VAT number, or a set of business hours on the website. Nothing in these terms invents those details. Formal notices use the address and email that are published, unless a scope names a different project contact.

The parties

KLAIM LIMITED is the supplier in these terms. The client is the business that commissions the work, named in the scope or, if no scope has yet been signed, the business that the enquiry identifies and that the company then agrees to work with. A person who writes from a personal inbox but describes an employer’s system is expected to have authority. If they do not, the company may pause until authority is confirmed.

These terms do not create a partnership, a joint venture, or an employment relationship. The company is an independent supplier. It may use employees or contractors. The website does not publish a headcount, and these terms do not promise a named team.

A client may not transfer the benefit of a scope to another organisation without written agreement, except that a successor to the client’s business may take it on if it accepts these terms and the scope in writing. The company may use subcontractors for parts of the work but remains responsible for work it has agreed to perform, subject to the liability clause.

Third-party platforms, cloud accounts, advertising accounts, and software licences that the client already holds are not parties to these terms. Their own contracts remain their own. The company does not become a party to a vendor’s terms merely because it configures something inside the client’s account.

Definitions

A scope, or statement of work, is a written description of a particular engagement: what will be done, what will not, what the client will provide, the timetable if one is agreed, and the fees. An email that both sides treat as the brief can be a scope if it is clear enough to perform. A slide without an acceptance is not.

Deliverables are the things the scope says will be handed over: code, configuration, a design record, a hosted environment, a data pipeline, an integration, a written recommendation, or support during a stated period. A conversation is not a deliverable unless the scope says the output is a document.

Client materials are anything the client supplies: access, accounts, copy, data, brand files, existing code, credentials, and decisions. Background material is what each party already owned before the engagement. A third-party service is a product or platform neither party wrote, such as a cloud host, an advertising system, or an email tool.

A business day is a day other than a Saturday, a Sunday, or a public holiday in England and Wales. Times are UK times unless a scope says otherwise. Writing includes email to the addresses the parties use for the engagement.

Personal data has the meaning given in UK data-protection law. A processor and a controller have those meanings too. These terms use them only when an engagement actually involves personal data. They do not assume that every piece of software contains it.

Enquiries are not contracts

A message sent through the website, or an email to help@klaimlimited.business, is an enquiry. It does not oblige the company to propose, to start work, or to reserve time. The company may decline an enquiry, ask for a clearer brief, or say that the work sits outside what it offers.

The confirmation page on the website means only that the server accepted the message for email delivery. It is not an acknowledgement of a project. If the mail function refuses the message, the website says so. The sender should not assume the company has read a message that the site said was not sent.

Estimates given in a first reply are invitations to discuss a scope. They are not a fixed price unless the writing says the price is fixed and the client accepts it. A range is a range. A ceiling is a ceiling only if it is written as one.

The company does not begin chargeable work on the strength of a website visit. Chargeable work starts when a scope says it starts, or when the client asks the company in writing to begin a defined task and the company agrees in writing to begin it.

Proposals

A proposal sets out the company’s understanding of the problem, the work it would do, the assumptions, and the commercial basis. It may be an email or a longer document. It stays open for the period it states, or for twenty business days if it states none. After that the company may withdraw or reprice it, because the availability of people and the state of the client’s systems can change.

A proposal is not a warranty that a third-party platform will behave as its marketing suggests. Where the work depends on a vendor, the proposal will say so. The client is responsible for its own contracts with those vendors unless the scope says the company will contract in its own name, which is not the default.

The client should correct a misunderstanding in a proposal before accepting it. Acceptance of a proposal that restates the brief is acceptance of that restatement. A later claim that the brief was different will be read against what was accepted.

Proposals are given for the client that asked. They are not transferable quotations for an unnamed group of companies. A sister company that wants the same work needs its own acceptance, because access, data, and liability follow the legal entity.

How a contract is formed

A contract is formed when the client accepts a proposal or scope in writing, or when both sides sign a scope, or when the company starts the work described in a scope at the client’s written request. The date of the contract is the date of that acceptance or start. These terms are incorporated by that acceptance even if the email does not paste them, provided the scope or the proposal pointed to them or the work was requested through the website that publishes them.

If the client issues a purchase order, the order is administrative unless the parties agree that its terms replace these terms. Pre-printed purchase-order terms that conflict with these terms do not apply just because an order number was supplied. An order number is useful for invoicing. It is not a silent rewrite.

The company may require a written scope before it starts, and it may refuse to start on an oral brief. Where it does start on a short written instruction, that instruction plus these terms is the contract for that instruction only.

Each scope is a separate contract unless it says it amends an existing one. Ending one scope does not end another, except where the client’s failure to pay or a termination for cause is expressed to cover all open scopes.

Order of documents

If documents conflict, they apply in this order: a mandatory rule of law; a data-processing arrangement that the law requires and that the parties have signed, on questions of personal data; the scope, on the description, price, and timetable of that engagement; these terms; the proposal, on any point the scope did not cover; the website terms of service, on use of the public site only.

A later written change that both sides accept prevails over an earlier scope on the point it changes. It does not revive a clause that was deliberately left out. Silence in a later email is not acceptance of a new price.

Headings are for reading. They do not change the meaning of a clause. Examples are illustrations, not extra obligations. A list of services on the website is a description of what can be commissioned, not a list of work included in every contract.

Custom software programming

Custom software programming means designing and writing software for a stated business process. The scope should name the users, the main jobs the software must do, the systems it must speak to, and the environment it will run in. The company writes to that description. It does not undertake to reproduce an unnamed competitor’s product.

Unless the scope says otherwise, the work includes the code and the configuration needed to meet the agreed description, a reasonable handover so the client can operate what was built, and the correction of defects that are reported in line with the acceptance clause. It does not include content writing, a redesign of the client’s brand, legal advice, or a penetration test, unless those items are written into the scope.

The client’s existing systems are assumed to behave as the client describes. If they do not, the change needed to cope with the difference is additional work. The company will say so when it sees the difference, rather than quietly absorbing an unbounded investigation.

Source code is handed over in the form the scope describes. If the scope is silent, the company hands over the source it wrote for the client’s deliverable, excluding its own pre-existing tools and excluding third-party components that cannot legally be handed over except under their own licences. A binary-only delivery happens only if the scope says so.

The company does not promise a particular programming language unless the scope names one. It will choose an approach that fits the brief and will say what it chose. A request to switch language after the work has started is a change.

Demos and capability sequences on the website are not specifications. A client who wants the visual or technical character of a demonstration must say so in the scope. Even then, the demonstration is an illustration of a kind of work, not a template that will be copied feature for feature.

What software work does not include

Unless the scope says so, software work does not include a guarantee of a business outcome, a sales figure, a saving, or a ranking. It does not include training of the client’s whole organisation. A short handover for the people who will run the system can be agreed. A rolling training programme is a separate scope.

It does not include buying licences in the company’s name, paying the client’s cloud bill, or funding advertising spend. Those costs sit with the account that owns them. If the company is asked to incur a pass-through cost, it will do so only against a written agreement on the amount and the timing of reimbursement.

It does not include monitoring the software after acceptance, except during an agreed warranty period for defects, or under a maintenance scope. A system that is left running without a support arrangement is the client’s to operate.

It does not include making the software comply with a law that the client did not mention and that is specific to the client’s regulated activity, unless the scope identifies that law. The client knows its sector. The company will follow a compliance requirement that is written into the brief. It will not invent a regulatory status for the client.

Computer systems design

Computer systems design is the work of deciding the structure before, or instead of, a build. The deliverable is a record: components, interfaces, environments, and the line between what is built, what is bought, and what is left alone. The record is written for the client’s operation, not as a generic textbook.

A design engagement ends when the record described in the scope is delivered. It does not by itself authorise the company to build the system. A later build needs its own scope, which may refer to the design. If the client changes the operation after the design is delivered, the design is not automatically wrong. Updating it is further work.

The company will base the design on the materials and access the client provides. Gaps will be marked as assumptions. An assumption that turns out to be false is a change, not a defect in the draughtsmanship, unless the company ignored information the client had already given.

Design work does not include a promise that a named vendor will accept the design, or that a future hire of the client will prefer it. It is a technical position the client can use to commission a build, including a build by someone else. If someone else builds it, the company’s responsibility ends at the design it delivered, not at the other party’s implementation.

Drawings, diagrams, and written decisions are the work. Rough notes in a working session are not a second, contradictory deliverable. The document the scope names is the one that counts.

Cloud and web hosting infrastructure

Hosting work covers where a site, application, or service runs, how it is reached, and how environments are separated. The scope should say whether the company is advising, configuring the client’s accounts, or operating an environment. Those are different responsibilities. Advice does not put the company in charge of the client’s cloud bill. Operation requires access and a defined period.

The website does not publish an availability percentage. These terms do not create one. If a scope states a target, that target is the only one. If it does not, the company will use reasonable care in the work it has agreed, and the client accepts that networks and suppliers fail. A target, where it exists, is measured as the scope says, excluding time lost to client-caused outages, scheduled maintenance that was notified, and failures of a vendor the client contracted.

The client owns its accounts unless the scope says an account is opened in the company’s name. Accounts in the client’s name should be billed to the client. Credentials are client materials. The company will not lock a client out of its own account as a way of resolving a dispute, except that it may suspend work it hosts where the suspension clause allows.

Backups are included only if the scope says so, and then only in the form and frequency stated. A backup that was never specified is not an implied archive. Restoring from a backup is part of the hosting work only when the scope includes restores, or when the company caused the loss inside an environment it had agreed to operate.

The company does not move a client onto a particular cloud because the website mentions infrastructure. The choice of provider, region, and rough scale belongs in the scope. A recommendation is not a reseller appointment. The company does not publish a partner badge on the website, and these terms do not create one.

Web architecture

Web architecture is the structure of a site or application: the parts, the content paths, and the boundary with marketing or advertising tools. It can be a design record, a build, or both, depending on the scope. It is distinct from a campaign. A campaign may use the site. It does not redefine the site’s structure unless the scope says the structure is being changed to carry the campaign.

The client is responsible for the lawfulness of the content it asks to be published. The company will implement the structure and the templates. It will not invent product claims, prices, or customer stories. If the client supplies text, the company may rely on it. Obvious placeholder text should not be left in a production site, and the company will not treat leftover placeholder copy as the client’s approved claim.

Domains and certificates are client assets unless the scope says otherwise. The client should control the registrar account. The company may be given technical access. That access is not ownership. On termination, the company will not withhold a domain that the client owns.

A public website the company builds for a client is not the same thing as klaimlimited.business. Cookies, analytics, and forms on a client site must be specified. The company’s own cookie policy does not automatically become the client’s cookie policy. If the client wants the company to draft that policy, the scope must say so, and the draft will be the client’s document to approve.

Data processing and analytics

Data processing and analytics means making records usable: pipelines, storage layout, transformation, and the reporting the scope names. The client decides which questions matter. The company builds or configures the path that answers those questions from the sources the client identifies.

The client is responsible for having a lawful basis to provide the records. The company will not accept a dump of special-category data, cardholder data, or children’s data as a sample attachment to a first email. A proper transfer, with the roles written down, comes first.

Figures that come out of a pipeline are only as good as the sources and the rules. The company will implement the rules in the scope. It does not warrant that the client’s source system recorded the world correctly. A dispute about a business result is not a defect if the pipeline followed the agreed rules.

The website’s portfolio does not report analytics outcomes. A client must not expect a case-study percentage. None is offered. Success for this work is that the agreed outputs are produced and can be explained.

Models, if any are in scope, are specified. The company does not slip a predictive model into a reporting engagement. Training a model on the client’s data requires a scope that talks about the data, the purpose, and the limits. It is not included in a generic analytics phrase.

Retention of the client’s records inside a pipeline follows the client’s instruction. The company will not keep a private copy for its own research. Copies made only to perform the work are deleted or returned when the scope ends, except for a copy the company must keep to defend a claim or to meet a legal duty, and except for residual copies in ordinary backups that age out on the backup cycle.

Digital advertising and MarTech

Digital advertising and MarTech work deals with the tools behind campaigns: audiences, creative handling, schedules, and the handoff into media systems. The scope should name the platforms the client already uses and whether the company is configuring them, building something they do not provide, or writing the brief for a later build.

The company does not buy media unless the scope says so and the money is agreed. A technical integration is not an obligation to spend the client’s budget. Recommendations about a channel are opinions based on the brief. They are not a promise of reach, return, or a particular cost per result.

Creative assets belong to the client or its licensors. The company will not supply a library of stock imagery as part of a technology scope unless the scope buys that production. The photographs on klaimlimited.business are the company’s site imagery. They are not a creative pack for clients.

Audience data is the client’s to justify. The company will implement the transfers and structures the scope describes. It will not upload a list that the client cannot explain. If a platform suspends an account for the client’s content or its audience practices, that suspension is the client’s problem with the platform, except where the company caused it by departing from the client’s lawful instruction.

Measurement tags and pixels on a client property are specified, not assumed. The company’s own site does not run advertising pixels. A client site can, if the scope and the client’s own notices allow it. The company will not add a pixel that the scope did not name.

Public relations platforms

Public relations platform work treats the activity as software and workflow: records of contacts, approvals, assets, and the path from a draft to a statement the client chooses to release. The company can build or integrate that system. It does not promise that a journalist, a platform, or the public will carry the statement.

The client is the publisher of its own statements. The company is not the client’s spokesperson unless a separate written appointment says so, and no such appointment is implied by a software scope. Drafting a press statement is not included in a platform build unless the scope adds it.

Contact lists loaded into a platform must be lawful for the client to use. The company will provide the fields and the workflow. It will not scrape addresses to fill the list. A request to collect addresses by deceiving the people involved will be refused.

Approvals configured in the tool are only as strong as the people who use them. The company is not liable for a statement that a client user approved and released. It is liable for a workflow that does not implement the approval rule the scope actually described, subject to the liability clause.

Digital marketing technology

Digital marketing technology connects content, channels, and measurement. The scope names the channels and the records. It does not name a market result, and these terms do not add one. A tool that shows a number is not a strategy. The company will not describe a dashboard as a substitute for the client’s own decisions.

Content calendars, if they are in scope, are operational tools. The client supplies or approves the claims. The company will not invent offers, discounts, or testimonials. A field for a testimonial is not a licence to fabricate one.

Where marketing technology shares data with advertising or analytics systems, the scope should say which system is the source. The company will build the handoff. It will not reconcile two vendors’ competing definitions of a conversion except by a rule the client agrees. If the vendors disagree, the rule decides, not a later argument about which vendor was “right”.

The client’s brand guidelines, where they exist and are supplied, will be followed for the templates in scope. A guideline that arrives after the templates are built is a change. The company is not obliged to police the client’s later edits.

Enterprise API integration

API integration connects systems so that an agreed set of events or records can move. The scope should name the source, the destination, the fields, the direction, and what happens when a call fails. Without that, the company will not guess at a silent retry policy or at a field mapping that changes the meaning of a record.

Third-party interfaces change. The company is not responsible for a vendor’s breaking change after acceptance, except under a maintenance scope that includes watching that interface. During the build, the company will work to the interface as documented at the time of the scope, and will say when the documentation and the live interface disagree.

Credentials for APIs are client materials. They should be issued with the least access the work needs. The client should be able to revoke them. The company will not embed a personal password in source that is handed over. Secrets belong in the mechanism the scope describes.

An integration is accepted against the agreed cases, not against every future record the client might send. A new field, a new country, or a new partner is a change. Volume assumptions matter. A design for a stated volume is not a design for a hundred times that volume. Scaling beyond the assumption is further work, which the company will flag rather than pretend was included.

The company does not warrant that a counterparty will keep its API available. The client’s contract with that counterparty is the place for that promise. The company’s work is the connection it agreed to build, tested as the scope describes.

AdTech and media systems

AdTech and media systems are the serving, logging, and accounting layer for digital media: how an impression, a click, or a creative decision is recorded and passed on. The scope identifies which events matter and which systems must see them. The company does not undertake to maximise spend or to minimise it. Those are commercial decisions.

Logs are kept for the period the scope states. If it is silent, the company will not invent a multi-year archive. Media logs can be large. Storage cost sits where the scope puts it, usually with the client’s account. A request to keep everything forever is a different system.

Fraud filters, brand-safety lists, and frequency caps are included only when specified. A default setting in a vendor product is the vendor’s default, not the company’s promise. The client should decide the policy. The company can implement a policy it is given.

The company will not configure a system to misrepresent inventory, to hide where ads ran, or to fabricate delivery numbers. A request to do so will be refused. The engagement can be ended for that kind of instruction under the termination clause, without the company being in breach.

Reconciliation between a media system and a finance system is in scope only if the scope names both and the rules. A difference that comes from the client’s own rate card, applied as agreed, is not a defect.

IT consulting and strategy

Consulting is a written technical position: what to build, what to leave, what to host, and in what order. The deliverable is the document or workshop output the scope names. It is advice. It is not a build, and it is not a promise that the client’s board will agree.

The company will use reasonable skill and care in the advice, based on the information given and on the time allowed. It does not warrant that the advice is the only possible plan, or that a later supplier will price the plan as the client hopes. Decisions remain the client’s.

Consulting time is often the product. A scope may be a number of days or a fixed document. Unused days are not a cash reserve. They expire as the scope says, or three months after the start if the scope is silent, because advice goes stale.

The company is not the client’s insurer and not its lawyer. A technical recommendation may have legal consequences. The client should take its own advice on contracts, regulation, and employment. The company will not hold itself out as giving that advice.

Notes of a workshop are a record of what was discussed, not a second opinion that overrides the written deliverable. If the notes and the deliverable differ, the deliverable governs.

System maintenance and support

Maintenance and support apply only when a scope says they do. There is no standing retainer created by a build. A build includes correction of defects on the acceptance terms. Ongoing watching, patching, and small changes are a separate arrangement.

A support scope should say the hours, the channel, what is included, and what is a chargeable change. The website does not publish a service level, and these terms do not imply a response time. If a scope states a target response, it is a target for starting work, not a promise that every fault will be finished in that time. Faults caused by the client’s users, by a vendor, or by a change the client made outside the arrangement are not the company’s defects.

The client keeps a contact who can approve a change and who can provide access. Support does not include sitting inside an account the client has locked. If access is removed, the clock on any target pauses.

Patching of third-party components is included only for the components and the cadence the scope names. A major upgrade that changes behaviour is a project, not a patch, unless the scope defines it as included. The company will not apply an untested major upgrade on a production system as if it were routine.

Support can be ended on the notice the scope gives, or on thirty days’ written notice if the scope is silent. Ending support does not erase the client’s licence in deliverables already paid for. It does end the company’s obligation to watch the system.

The client’s materials and access

The client will supply the materials and access the scope needs, in time for the timetable. That includes decisions. A delayed decision delays the work. The company will say what it is waiting for. It is not obliged to invent a decision and then rebuild when the client disagrees.

Materials must be lawful for the client to supply and for the company to use for the engagement. The client warrants that it has the rights and the notices it needs. The company may rely on that warranty. If a third party claims that a client material infringes, the client is responsible for that claim, and the company may pause the part of the work that depends on the material.

Access should be individual where the system allows it, and removable. Shared passwords are a last resort and should be changed when the engagement ends. The client will tell the company when a person on its side leaves, if that person had sponsored access.

The company will use client materials only for the engagement, for a legal duty, or to defend a claim. It will not use the client’s data to train a general model for other customers. A portfolio reference is allowed only under the publicity clause, which requires permission before a client is named.

Client responsibilities

The client will name a person who can answer questions and accept deliverables. Conflicting instructions from two people on the client’s side are a problem the client must resolve. The company may wait, and the timetable moves.

The client will keep its own backups of materials it cares about, unless the scope puts a defined backup on the company. Sending a file to the company is not, by itself, an instruction to archive it forever.

The client will not ask the company to do anything unlawful, to mislead a platform, or to hide a material fact from a vendor whose terms the client has accepted. The company may refuse that instruction and will not be in breach for the refusal.

The client is responsible for the use of deliverables after acceptance, including the lawfulness of content, audiences, and later configuration changes made by its own people. A change the client makes can take a deliverable outside the acceptance tests. The company will help unpick that only under a support scope or a new piece of work.

The client will pay the fees as the fees clause describes. A dispute about one invoice line does not entitle the client to withhold unrelated fees that are not genuinely disputed.

Third-party services

Work often depends on third-party services: hosts, libraries, advertising platforms, email tools, and payment or identity products the client uses. Those services have their own terms, availability, and prices. The company is not the vendor. A vendor’s outage, price change, or deprecation is not a breach by the company, provided the company did not ignore a constraint the scope had already recorded.

Open-source components are third-party materials. They are supplied under their own licences. The company will not strip those licences. The client’s use of them must follow the licences. The company will say when a component’s licence is awkward for the client’s intended distribution, if it knows at the time of selection. It will not perform a legal audit of every transitive dependency unless the scope pays for that review.

The company may recommend a service. A recommendation is not a warranty of the vendor’s future, its security, or its jurisdiction. The client decides whether to open the account. Where the company opens an account because the scope says so, it will do so on the client’s instruction and will hand over control as the scope describes.

App stores, browsers, and advertising exchanges can reject or delay a submission. The company will make the submission the scope includes, and will correct a defect that is the company’s. A rejection for the client’s content, its legal status, or a policy the vendor applies unevenly is not a defect in the build.

Changes

Either side may ask for a change. A change that affects price, timetable, or scope is agreed in writing before the company is obliged to do it. The company may give a short impact note. The client’s written acceptance of that note amends the scope.

The company is not obliged to start a change that has not been accepted, even if a meeting felt positive. It may, if it chooses, do a small clarification that does not move the price. That choice is not a waiver of the need for written changes in general.

If the client asks the company to wait, the timetable shifts by the waiting time and by the time needed to restart. People are not kept idle free of charge. A hold longer than fifteen business days lets the company replan, and a hold longer than thirty business days lets the company pause the engagement and invoice for work done.

A change in law that makes the agreed approach unlawful is a change the parties will discuss. The company will not continue an unlawful approach. The cost of a lawful alternative is agreed, or the affected work ends without either side being in breach for the ending itself.

Acceptance

The scope should say how deliverables are accepted. If it does not, the client has ten business days after delivery to give a written list of defects measured against the scope. A defect is a failure to meet a stated requirement, not a new idea. The company will correct confirmed defects in a reasonable time. If the client does not send a list in the ten days, the deliverable is accepted. If the client uses the deliverable in production, it is accepted, except for defects it has already reported in time.

Acceptance is not withheld for a cosmetic preference that was not in the scope, or for a third-party failure, or for a client material that was wrong. Those can be new work. They are not a reason to refuse the fees for the work that met the brief.

Tests use the cases in the scope or, if none are listed, cases that a reasonable reader of the scope would expect for the main paths. The company is not obliged to test every combination the client thinks of after seeing the result. Additional cases can be added as a change.

A design record is accepted when it covers the questions the scope asked, with assumptions marked. It is not rejected because the client later prefers a different architecture. That preference is a new design task.

Support work is accepted by the period existing, not by a single sign-off, unless the scope defines releases inside the support period. Each release inside a support period follows the same defect rule unless the scope shortens it.

Fees

Fees are what the scope states: a fixed fee, a daily or hourly rate, or a mix. A fixed fee covers the scope as accepted, not later changes. A rate is charged for time spent on the engagement, including reasonable investigation that the scope implied. The company will not pad time. The client will not treat every hour of thinking as optional.

If a scope gives a rate and an estimate, the estimate is a forecast. The company will tell the client when it expects to pass the estimate. Passing it without a warning, where the company could reasonably have warned, entitles the client to stop further work. It does not erase the time already spent at the agreed rate.

Fees are in pounds sterling unless the scope says another currency. The website does not publish a rate card. A rate mentioned in an old email is not a standing rate for a new scope.

The company may invoice monthly for time-based work, or at the milestones a fixed fee names. If a fixed fee names no milestones, it may invoice half at the start and half on acceptance, unless the scope says otherwise. A start payment is a payment for reserving the work, not a deposit the client can reinterpret as optional.

Unpaid fees that are not genuinely disputed may be charged interest under the Late Payment of Commercial Debts (Interest) Act 1998, including the statutory compensation the Act allows. The company may also pause work. Pausing is not a termination. The timetable moves by the length of the pause.

Invoices and payment

Invoices are payable within fourteen days unless the scope says a different period. Payment is by bank transfer to the account the invoice names. The company does not ask to be paid in cash, in cryptocurrency, or to a personal account. A request that looks like that is not from the company’s published channels and should be checked by writing to help@klaimlimited.business.

The client will say promptly if an invoice does not match the scope. A genuine dispute is confined to the disputed amount. The rest is paid. A dispute raised for the first time months later, about work that was accepted, is not a genuine dispute about that invoice. It may be a warranty point, which is a different conversation.

The website does not state whether VAT is charged. If VAT applies, invoices will say so and the client will pay it. If the company is not registered, invoices will not invent a VAT number. The client is responsible for any withholding that its own country requires, and will gross up if a withholding would otherwise reduce the fee, unless the scope deals with tax differently.

Expenses are charged only if the scope allows them, or if the client agrees a particular expense in advance. Ordinary connectivity and ordinary software the company already uses are not expenses. Travel is not assumed. The Upminster address is not a promise that every meeting happens there.

Intellectual property the parties already own

Each party keeps its background material. The client keeps its brand, its content, its data, and its existing systems. The company keeps its pre-existing tools, libraries it wrote for reuse, and its general know-how. Seeing the client’s system does not transfer it. Seeing the company’s method does not transfer the method.

The company’s website, logo, and the photographs published on klaimlimited.business stay the company’s. A client engagement does not assign them. A client may not use those photographs as its own advertising.

Feedback the client gives about a deliverable may be used by the company to improve its general approach. It will not be used in a way that publishes the client’s confidential information. An idea that is simply a requirement of the client’s business stays the client’s requirement, not a patent the company claims.

Third-party materials stay under their licences. Neither party assigns the other’s supplier contracts.

Intellectual property in deliverables

When the client has paid the fees for a deliverable, the company assigns to the client the intellectual property rights it owns in that deliverable and that were created specifically for the client under the scope, except for background material and except for third-party components. The assignment takes effect on payment, not on delivery. Until payment, the company grants only a revocable licence to evaluate the deliverable for acceptance.

If a fee for a deliverable is unpaid, the company may suspend the licence and may withhold the handover of source that has not yet been given. It will not delete the client’s own materials. It will not hold the client’s domain hostage.

Background material that is embedded in a deliverable is licensed, not assigned. The licence is non-exclusive, and it lasts for as long as the client needs it to use the deliverable for its own business. It may not be used to set the company up as a product for resale, and it may not be separated and sold as a tool, unless the scope says otherwise.

The company may keep a copy of a deliverable for its records, for support it has agreed to give, and to know what it handed over. That copy is not a right to resell the client’s product.

Moral rights are not asserted against the client’s ordinary use of a deliverable, to the extent the company can waive them. The company may still be identified as the maker in its own records.

If open-source terms require a particular notice or a reciprocal licence, those terms govern that component. The assignment in this clause cannot override them. The company will not agree a scope that requires it to pretend an open-source component is proprietary.

Confidentiality

Each party will keep the other’s confidential information confidential and will use it only for the engagement. Confidential information is information that is marked as such, or that a reasonable person would treat as confidential, including unreleased product plans, credentials, pricing, and personal data. It is not information that is public through no fault of the receiver, that the receiver already knew without a duty, that a third party gives without a duty of secrecy, or that is independently developed.

A party may share confidential information with people who need it for the engagement and who are bound by a similar duty, and with professional advisers, and when the law requires. A legal requirement, where it can lawfully be said, will be notified to the other party so that they can seek a protective order if they wish.

The duty lasts for three years after the engagement ends, and for as long as the information remains a trade secret if it is one. Personal data is governed by the data-protection clause and by the law, which may require a different period.

The website is public. Nothing the company has already published on klaimlimited.business is the client’s confidential information. A client must not send confidential files by an insecure channel and then complain that the channel was public. The contact form is an ordinary email path. Highly sensitive material needs a channel the parties agree.

The company may describe the fact that it does the kinds of work listed on the website. It may not name the client or describe the client’s confidential system without permission. The portfolio on the website does not name clients, and these terms do not authorise a change to that practice for a particular client unless the client agrees in writing.

Personal data in an engagement

If the company processes personal data on the client’s behalf, the client is the controller and the company is the processor, unless the scope says a different split for a defined part of the work. The parties will sign a processing arrangement that meets Article 28 of the UK GDPR before that processing starts, or will include those terms in the scope. These commercial terms do not pretend to be that arrangement on their own.

Until that arrangement exists, the company will not be asked to host or transform the personal data. An enquiry may contain the sender’s own business contact details. Those are handled under the website privacy policy, not as a client database.

The client will not instruct the company to process personal data in a way that breaks UK data-protection law. The company will tell the client if an instruction looks unlawful, and may stop that part of the work. The client deals with requests from data subjects about its own records, and will not send those requests to the company as if the company were the controller, except where the company is in fact a controller for a stated activity.

If the company is a controller for its own enquiry records, its own invoices, and its own website, it handles those as the privacy policy and the law require. The client does not control those records.

International transfers of client personal data will be dealt with in the processing arrangement, not invented here. The company will not move a client’s production data to a new country as a convenience.

A personal-data breach affecting data the company processes for the client will be notified to the client without undue delay after the company becomes aware of it, with the information the company has. The client decides on notices to regulators and to individuals where the client is the controller. The company will help with information that is reasonably in its hands, as the processing arrangement provides.

The website does not name a data-protection officer. Engagement notices about privacy go to the project contact and to help@klaimlimited.business.

Security of the work

The company will use reasonable care, given the nature of the engagement, to avoid introducing known malicious code into deliverables and to keep credentials it holds from casual exposure. Reasonable care is not a certification. The website does not claim a particular security accreditation, and these terms do not add one.

The client will keep its accounts protected, including multi-factor authentication where the platform offers it for administrative access. A breach that starts in a client account the company was not engaged to secure is not a defect in a deliverable.

Security testing is a separate scope. A build includes ordinary care. It does not include a paid attack exercise, a bug-bounty programme, or a promise that no vulnerability exists. If a vulnerability is found in the company’s own deliverable within the defect period, and it is a failure against the scope or against ordinary care, the company will correct it. A vulnerability in a third-party component is handled by the maintenance rules if maintenance is in force, and otherwise by a new piece of work.

The client will not run a test that degrades a production system without agreeing the window. The company will not either. A load test is specified, not improvised.

Neither party will store production passwords in a ticket or in the website contact form. Secrets follow the mechanism the scope names.

Acceptable use of systems the company operates

Where the company operates an environment for the client, the client will not use it for unlawful content, for attacks on other systems, for unsolicited bulk email that breaks the law, or for material that a reasonable host would remove. The company may suspend that environment if it reasonably believes the use breaks this clause or puts the company’s own suppliers at risk. It will tell the client and will restore the environment when the cause is gone, unless the law forbids the restoration.

The client’s users are the client’s responsibility. A user who shares a credential has acted for the client. The company may refuse a user it reasonably believes is abusing access.

Resource limits stated in a scope are real. A sudden load that threatens the environment may be throttled to keep it up. Throttling is a protective step, not a silent change of specification. A lasting increase in load is a change.

The company does not monitor the client’s content for defamation or for regulatory claims. It is not the publisher of the client’s site. It will act on a legally binding notice that actually applies to material it hosts, and it will tell the client unless the notice forbids that.

No standing service level

Readers of the website sometimes look for an uptime figure. There is not one on the site, and these terms do not create a general one. Availability, response, and restore targets exist only inside a scope that writes them down, with the exclusions that scope states.

Where a scope is silent, the company’s duty is reasonable skill and care in the tasks it accepted, not a result measured in nines. The client should not plan a launch on an assumption the papers do not contain.

Service credits, if a scope provides them, are the client’s sole financial remedy for the miss they cover, without limiting liability that the law does not allow to be limited. If a scope has no credits, there are no credits. The liability clause is the financial framework instead.

Scheduled maintenance of an environment the company operates will be notified when the company can reasonably do so. Emergency work to protect the environment may happen first and be explained after. Maintenance of the public website klaimlimited.business is not maintenance of a client system.

Warranties

The company warrants that it will perform the work with reasonable skill and care, that it has the right to enter the contract, and that the deliverables it assigns will not, to its knowledge, knowingly include code it does not have the right to provide. It warrants that it will correct defects reported under the acceptance clause.

The client warrants that it has the authority to commission the work, that its materials are lawful, and that its instructions will not require the company to break the law or a third party’s rights. It warrants that the business contact details it gives are ones it is allowed to use.

Except for the warranties in this clause and any that the law will not allow to be excluded, the work and the site are provided without other warranties, including any implied warranty of fitness for a purpose the scope did not state. A purpose that matters must be written down. An unstated purpose is not a warranty.

The company does not warrant uninterrupted or error-free operation of third-party services, and it does not warrant a commercial outcome. Demonstrations on the website are not warranties.

Liability

Nothing in these terms excludes or limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for any other liability that cannot be excluded under the law of England and Wales.

Subject to that, neither party is liable to the other for loss of profit, loss of revenue, loss of anticipated savings, loss of goodwill, or for indirect or consequential loss, whether or not it was advised of the possibility. A lost advertising spend because a platform changed its rules is in that category unless the company caused it by departing from the scope.

Subject to the first paragraph of this clause, each party’s total liability arising out of a scope, whether in contract, tort, or otherwise, is limited to the fees paid under that scope in the three months before the claim arose, or to the fees paid under that scope in total if less has been paid. If no fee has been paid and the claim is the company’s, the limit is the fees that were due for the work actually done. This cap is per scope, not a single cap across unrelated engagements, unless a scope says several scopes share one cap.

The cap does not apply to the client’s obligation to pay fees, to the client’s responsibility for its own materials, or to a breach of the clause that forbids a party to misuse the other’s background material by reselling it. Those are not the kind of loss the cap is meant to socialise.

The company is not liable for a loss that the client could have avoided by using ordinary care, by keeping the backup the scope assigned to the client, or by not running an unagreed test on production. The client is not liable for a loss the company could have avoided by following the scope.

A claim must be brought within twelve months of the party knowing the facts that give rise to it, except where the law requires a longer period. This does not shorten a period the law forbids shortening.

The allocations in this clause are reflected in the fees. A client that wants a higher cap can ask for one in the scope, and the fee may change. A higher cap is not implied by the importance of the system.

Suspension

The company may suspend work if a fee that is not genuinely disputed is overdue, if the client’s instruction would be unlawful, if access is unsafe, or if the client’s use of an operated environment breaks the acceptable-use clause. It will say why, unless the law or a supplier’s emergency forbids a prior notice, in which case it will say why as soon as it can.

Suspension pauses the timetable and any support targets. It does not delete the client’s data as a first step. Data in an environment the company operates is handled on termination or on a written instruction, not as a surprise during a short suspension.

The client may suspend a new phase if it disagrees with a change note, by saying so in writing. Work already done remains payable. A suspension is not a way to keep a team on hold without the hold rules in the changes clause.

Either party may lift the suspension when the cause is cured. The company may replan the restart. A suspension that lasts more than thirty business days gives either party the right to end the affected scope on written notice, without that ending being a breach by the party who gives the notice, provided the party giving notice is not itself the cause of the suspension.

Term

These terms apply to an engagement from the date the contract is formed until the scope is finished, terminated, or expired. A support scope lasts for the period it states and renews only if it says it renews. Silence is not a renewal.

Clauses that by their nature should survive do survive: payment for work done, intellectual property, confidentiality, data protection duties that still apply, liability, and the parts of termination that deal with handover.

The website’s publication of these terms continues until the company replaces them. A new version applies to new engagements. An existing scope keeps the version that applied when it was formed, unless both sides adopt the new version in writing.

Termination

Either party may end a scope for convenience on thirty days’ written notice, unless the scope names a different notice or says it cannot be ended for convenience before a milestone. A fixed-fee scope ended for convenience is paid for the work done and for costs the company cannot unwind, which the company will itemise. It is not paid for work it will not do, and it is not asked to hand over unfinished work except as the termination consequences describe.

Either party may end a scope immediately by written notice if the other party materially breaches it and does not cure the breach within fourteen days of a notice that describes the breach, or immediately if the breach cannot be cured. Non-payment of an undisputed fee is a material breach.

Either party may end if the other becomes insolvent, makes an arrangement with creditors, or stops trading. The company may end if the client asks it to do something unlawful and will not withdraw the instruction.

Ending a scope does not by itself end a different scope that is being performed properly. Ending for non-payment may be stated to cover all scopes, and if the notice says that, it does.

Termination is not the only remedy. A party may still claim for work done or for a loss that the liability clause allows.

Consequences of termination

On ending, the client pays for work done up to the end and for accepted deliverables. The company stops using the client’s credentials and, on request, confirms that it has removed them from its own stores, allowing for backups that age out.

The company will hand over client materials and paid-for deliverables that are in a handover state, within a reasonable time, provided undisputed fees are paid. Work that was not paid for and not finished is not a deliverable the client can demand in source form, except that the client may take back its own materials that were embedded in it.

A design that was paid for is handed over even if the client has decided not to build it. A design that was not paid for remains the company’s, and the client’s materials inside the working file are returned.

Support ends at the end date. The company is not on call the day after. A short, paid handover can be agreed so the client’s next supplier can ask questions. That handover is a small scope of its own if it is more than a single reasonable session.

Clauses about confidentiality and about the client’s data continue. The company will delete or return personal data it processed as a processor, as the processing arrangement says, and will keep only what the law or a legal claim requires.

The public website is unaffected by the end of a client engagement. The client’s end does not oblige the company to take down a general description of a service. It does oblige the company to respect a promise not to name the client.

Force majeure

Neither party is in breach for a delay caused by something beyond its reasonable control, including a failure of power or networks not caused by the party, a widespread cloud failure, a change in law, a fire, a flood, an epidemic that genuinely stops the work, or industrial action that is not limited to the party’s own staff. The party will tell the other, and will reduce the effect where it reasonably can.

Inability to pay is not force majeure. A vendor’s ordinary deprecation, announced in the usual way, is a change to plan for, not force majeure, unless the notice is so short that the work cannot be redirected in time.

If the delay continues for more than sixty days, either party may end the affected scope without liability for that ending, and the consequences of termination apply to the work done.

Notices

Notices under a contract are sent by email and are effective when sent, unless the sender receives a bounce, and also if either party asks, by post to the published address for the company and to the address the client gave for the scope. The company’s email for notices is help@klaimlimited.business unless a scope names a project address. A project address may be used for day-to-day instructions. A notice of termination or of a claim should also go to help@klaimlimited.business so that it is not stuck in one person’s inbox.

A notice to the company’s website contact form is not the preferred path for a contractual notice, because the form is an enquiry tool. If it is used, it counts only when the site confirms the message was accepted for delivery.

Each party keeps its contact details current. A notice sent to the last address given is effective if the party forgot to send the new one.

Assignment and subcontracting

The client may not assign a scope without the company’s written agreement, except to a successor of substantially all of its business who accepts the scope in writing. The company may not assign a scope without the client’s written agreement, except to a successor of substantially all of the relevant business on the same terms.

The company may subcontract parts of the work. It remains responsible for those parts as if it had done them, subject to the liability clause and to the limits that apply to third-party services. A subcontractor who processes personal data for the client is a sub-processor and will be dealt with in the processing arrangement.

Nothing in these terms gives a third party a right to enforce them under the Contracts (Rights of Third Parties) Act 1999, except that a data subject’s statutory rights do not depend on that Act and are not removed by this sentence. A member of the client’s group who is not the contracting party does not get a free contract.

Entire agreement

A scope and these terms, together with a processing arrangement where one exists, are the entire agreement for that engagement. They replace earlier discussions about the same work. They do not replace a duty that arises from fraud, and they do not stop a party showing what was said when the question is what the scope meant.

The website’s general descriptions are not representations that override a scope. A client who needs a feature must see it in the scope. Reliance on a page, a demonstration, or a sales conversation that was not written into the scope is the client’s risk, except where the law does not allow that allocation.

A change to these terms for an existing engagement must be in writing. An email is writing. A thumbs-up on a message is not, unless the parties have agreed that a particular channel’s approval mechanism counts and the approval is unambiguous.

If a clause is held unenforceable, it is narrowed to the extent needed, and the rest stay. A failure to enforce is not a waiver. A waiver must be in writing to bind.

Publicity and references

The company will not name the client, quote the client, or show the client’s identifiable system in its portfolio without written permission. Permission can be refused and can be withdrawn for future use. Materials already printed cannot always be recalled, but the company will stop using them on the website within a reasonable time after a withdrawal.

The client will not say that the company endorses its product, its advertising claims, or its financial results. A factual statement that the company supplied a described piece of work is acceptable if it is accurate and if the client does not imply a result the scope did not contain.

The demonstrations already on the website are not about the client. Accepting these terms does not make them case studies of the client, and it does not make the client responsible for them.

Neither party will use the other’s logo without permission. The company’s logo on klaimlimited.business is not a badge the client may place on its own site, except for a factual credit the parties agree.

People

The company does not publish a staff list, and the client does not acquire a right to a named individual. People may change. The company will keep the work staffed with people who can do it. A request for a particular person is a preference, not a term, unless the scope names that person and says the engagement depends on them.

During an engagement and for three months after it, neither party will solicit the other’s people who worked on it to leave their employment. A response to a public advertisement is not solicitation. This clause does not stop a person exercising ordinary freedom to change jobs. It stops active targeting of the small group who did the work.

The client’s instructions go to the project contact, not around them to pressure an individual. The company’s commitments go through the same contact. A side conversation does not change the scope.

Insurance and financial standing

The website does not publish insurance limits, a turnover, or a credit rating. These terms do not invent them. A client that needs a certificate of insurance can ask. If the company holds a relevant policy it is willing to evidence, it will say so. If it does not, it will say that too. A scope may require a level of cover as a condition, and if it does, that requirement is part of the scope rather than a guess from these pages.

The company does not ask the client for a guarantee from a director unless a scope says so. The client does not ask the company’s people for personal guarantees. The contract is with the legal entity.

Nothing on the website is an invitation to invest, to lend, or to treat the company as a financial service. The work is technology and related consulting.

Export, sanctions, and unlawful instructions

Each party will comply with sanctions and export rules that apply to it. The client will not supply technical material that it is not allowed to export, and will not ask the company to deal with a person the client knows is sanctioned. The company may refuse and may end the affected work. It does not undertake to be the client’s sanctions counsel.

The website is a public marketing site. It is not an export of encryption beyond what a browser already does. A deliverable that includes cryptography is specified. The client is responsible for any filing its own distribution requires.

An instruction to deceive a platform, a regulator, or a person is void. The company will not follow it. Fees for lawful work already done remain payable. Fees for the unlawful part are not, and if they were paid they are not a windfall the company will keep for work it refused to do.

Governing law and disputes

These terms and each scope are governed by the laws of England and Wales. The courts of England and Wales have exclusive jurisdiction, except that either party may seek an interim injunction in any court that can grant one, and except that a mandatory consumer right, if one actually applies, is not removed.

The parties will try to resolve a dispute by a written exchange between people who can settle it, for ten business days after one side gives a notice of dispute, before issuing proceedings. That step is not required for an application for urgent relief, or for a claim for undisputed fees. It does not pause a limitation period that is about to expire. A party may still issue if the ten days would put the claim out of time, and will say that it has done so.

The language of the contract is English. A translation, if someone makes one, is for convenience. The English text governs.

These terms are written for businesses. If a court finds that a person dealt as a consumer, the clauses that the law does not allow against a consumer do not apply to that person, and the rest do. The person should not use a business form to hide a consumer contract.

The website is not the product

klaimlimited.business explains the company. It is not a software product the client licences. Its uptime is not a client deliverable. Its design, type, and motion are not a specification for the client’s own site unless a scope copies a stated element on purpose.

Capability demonstrations, representative scenarios, and technical approaches on the portfolio are labelled as such. They do not show a client result, because no client result is claimed. Accepting these terms does not turn them into warranties, case studies, or performance data.

The company may change the website without notice and without that change amending an existing scope. A sentence removed from a page is not removed from a contract that already incorporated an earlier document.

Links from the website to its own legal pages are part of the site. A client’s duty to read a scope includes the terms the scope incorporates. A client that accepts a scope without reading these terms is still bound, because they are published at the address the site gives and the scope or the proposal pointed to the site or to these terms.

How to read a scope against the service list

The website lists custom software programming, computer systems design, cloud and web hosting infrastructure, data processing and analytics, digital advertising and MarTech, public relations platforms, digital marketing technology, enterprise API integration, AdTech and media systems, IT consulting and strategy, web architecture and hosting, and system maintenance and support. A scope may cover one of them or several. It does not silently include the rest.

Words on the website are the ordinary meaning they have in these terms. “Support” means the maintenance clause, not a promise to be available at all hours. “Strategy” means the consulting clause, not a seat on the client’s board. “Hosting” means the hosting clause, not ownership of the client’s infrastructure. “Integration” means the API clause, not a merger of companies.

If a scope uses a word differently, the scope’s definition wins for that engagement. If it uses a word without defining it, these terms and the ordinary technical meaning apply. A metaphor in a sales conversation does not redefine a word.

The six-stage description on the services page — listen, frame, specify, build, place, remain — is a way of organising work. It is not a six-invoice obligation and not a methodology the client can audit the company against. A scope can skip a stage. “Remain” happens only when support is bought.

Handover and knowledge

Handover is the practical transfer the scope describes: where the code or configuration lives, how to access it, and what the client needs to run it. It is proportionate to the work. A small integration does not include a week of classroom teaching. A large build includes enough time that a competent person on the client’s side can operate it.

The client will make that competent person available. Handover to an empty room is not a failure by the company. The company will provide the written material the scope promised even if the meeting slips, and will rearrange one meeting that the client misses. Further missed meetings are a change or a pause.

Knowledge of the client’s business stays with the client. Knowledge of general technique stays with the company. Handover does not include an assignment of general technique beyond the licence in the intellectual-property clause.

Credentials are handed to the client’s named owner. They are not left only in a chat thread. When the company created an account, it will transfer the owner role where the platform allows, or it will give the client the materials needed to do so.

Testing environments and production

Work is done in the environment the scope names. Production changes happen in an agreed window. The company will not use production data in a casual test unless the scope, and the data-protection arrangement, allow that use. Synthetic data is preferable and will be used where it can answer the test.

The client will not point a public campaign at an environment the company has called a test. If it does, the consequences are the client’s, including load and the lawfulness of collecting real personal data on a test form.

A rollback plan is part of a production change when the change is material. The scope or the change note should say what rollback means. If it does not, the company will keep the previous version available for a reasonable return where the platform makes that possible, and will say when the platform does not.

After acceptance, production belongs to the arrangement then in force: the client’s operation, or a support scope. The company does not keep a private back door. Access that remains is the access the support scope or the handover described, and it is removable.

Content, claims, and regulated statements

The client is responsible for claims about its goods, services, prices, and performance. The company implements technical work. It does not clear advertising claims, financial promotions, or health claims. If the client is in a regulated sector, it will say so in the scope and will provide the constraints. The company will follow constraints it is given. It will not register the client with a regulator or hold itself out as the client’s compliance function.

A field that publishes a number should have an owner on the client’s side. The company will connect the field. It will not decide that a number is fair. If the company notices an obvious placeholder or a broken token, it will say so. That courtesy is not a duty to review the client’s whole catalogue.

Testimonials, reviews, and case studies on a client site are the client’s content. The company will not generate fake ones. The absence of testimonials on klaimlimited.business is deliberate. These terms do not ask the client for a testimonial. If the client offers one, the publicity clause applies, and the client must be willing for its name to be used.

Conflicts and exclusivity

The company may work for other businesses, including businesses in the client’s sector, unless a scope agrees a narrow exclusivity for a named competitor and a named period. Exclusivity is not implied. It is expensive and must be priced. The website does not offer it as a standard.

The company will not use the client’s confidential information to help another client. General skill learned on the engagement may be used elsewhere. That is the nature of a specialist practice, and it is allowed.

The client may appoint other suppliers. The company is not exclusive unless the scope says so. Where several suppliers share a system, the scope should say who may change production. The company is not liable for another supplier’s commit.

If a conflict of interest appears that confidentiality cannot manage, the company will tell the client that a conflict exists, without disclosing the other party’s secrets, and the parties will agree whether the affected work can continue.

Open-source and contribution

If the scope says a component will be published as open source, the licence and the owner of the project will be named. The client will not demand a public release of work that includes its confidential information. The company will not publish the client’s code as open source unless the scope, or a later written consent, allows the exact publication.

Contributions to an existing open-source project follow that project’s rules. The company may contribute a generic fix it owns. It will not contribute the client’s proprietary logic. A generic fix that contains no client information is background or a new company-owned fix, and the open-source licence applies to the contribution.

The client’s internal use of open-source components must follow their licences, including notice and, where the licence requires it, the availability of source for that component. The company will pass on notices it knows are required for components it selected. The client will not remove them.

Notices on the website about these terms

The current terms live at the terms-and-conditions page of klaimlimited.business. The company may correct a typographical error without changing the meaning. A change of substance is a new dated version. Engagements formed under an older version keep that version, as the term clause says.

The client should keep a copy of the scope and of the terms that applied. The company will provide the terms page as it stood if a dispute turns on wording the company still has. It is not obliged to reconstruct a page it no longer stores, beyond what ordinary records contain.

These terms are written in sentences a business reader can follow. They are still a contract. A heading that sounds gentle does not remove an obligation in the paragraph under it. A heading that sounds stern does not create an obligation the paragraph does not contain.

Contact about these terms

Questions about these terms, before or during an engagement, go to help@klaimlimited.business or to the project contact named in a scope, with a copy to that email address for anything that changes price, liability, or termination. Post may be sent to KLAIM LIMITED, 9 Corbets Tey Road, Upminster, RM14 2AP, United Kingdom. The telephone number +44 7520 619384 is for conversation. A telephone call does not amend a scope unless the amendment is afterwards written down and accepted.

The company will not ask a client to agree to terms that live only in a file the client cannot save. These terms are on a public page so they can be read before a scope is accepted. A scope that tries to incorporate unseen terms at a dead link does not incorporate them. It incorporates these published terms instead, unless the parties attach a different document to the scope itself.

Nothing in this contact clause appoints the company as the client’s agent for service of proceedings, and nothing appoints the client as the company’s. Proceedings follow the governing-law clause and the ordinary rules of the court.