Legal

Terms of Service

The licence to use what comes back, what may and may not be resold, the uses that are prohibited, why no match rate is warranted, and how paid recurring subscriptions are separate from usage metering.
Tenhaw LTD, registered in England and Wales, company 12735685Last updated hello@entitybind.com
Self-serviceCreate your workspace online and verify your email to start matching company records. Free starts with 300 credits and no card. Paid monthly plans are available in workspace Billing; VAT is added where applicable. Usage is tracked without automatic overage charges. Trust and security
Clauses
1. Who we are, and what these terms cover2. What the service is, and the scope it will not go outside3. Access, credentials and accounts4. Your data, and what you permit us to do with it5. What we do not warrant, starting with the match rate6. Confidence, abstention and the decision that is yours7. The licence you get to use the results8. Resale, and the open-licensed subset9. Uses that are prohibited10. Credits, and how a call is counted11. Rate limits, quotas and depth12. Billing and payment13. Availability, and the absence of a service level14. Changes to the service and to these terms15. Suspension, termination and getting your data out16. Confidentiality and publicity17. Liability, stated plainly18. Governing law, and how to reach us

Contents

18 clauses. Each has its own link, so you can send a colleague the one clause they asked about.

  1. 1Who we are, and what these terms cover
  2. 2What the service is, and the scope it will not go outside
  3. 3Access, credentials and accounts
  4. 4Your data, and what you permit us to do with it
  5. 5What we do not warrant, starting with the match rate
  6. 6Confidence, abstention and the decision that is yours
  7. 7The licence you get to use the results
  8. 8Resale, and the open-licensed subset
  9. 9Uses that are prohibited
  10. 10Credits, and how a call is counted
  11. 11Rate limits, quotas and depth
  12. 12Billing and payment
  13. 13Availability, and the absence of a service level
  14. 14Changes to the service and to these terms
  15. 15Suspension, termination and getting your data out
  16. 16Confidentiality and publicity
  17. 17Liability, stated plainly
  18. 18Governing law, and how to reach us

1. Who we are, and what these terms cover

Entity Bind is a product of Tenhaw LTD ("we", "us"), a company registered in England and Wales, company number 12735685, VAT GB388977014, of London, England. Entity Bind has no legal personality of its own, so the party you contract with is Tenhaw LTD. These terms govern use of this website, use of the Entity Bind API and MCP server on a deployment we operate, and any evaluation, preview run or sprint we perform on a file you send us. Where you have signed a separate order form, engagement scope or agreement with us, that signed document takes precedence over anything here on the points it covers, and these terms fill the rest.

2. What the service is, and the scope it will not go outside

Entity Bind resolves company and organisation identity. One record in, one resolved company record out, with citations, a calibrated confidence score and a receipt that reopens at a URL, or an honest abstention with a ranked shortlist when the evidence will not carry a match. Entity Bind resolves companies and organisations only. It does not resolve people, vessels, bank-account ownership, sanctions exposure, emissions or geolocation, and its results may not be used for eligibility decisions about individuals, including employment, credit and tenancy. It is also not a sanctions or adverse-media screening tool, not a credit reference agency, and not a substitute for any regulated check you are obliged to perform yourself. If you already run a licensed company-data feed or a master data management platform, run Entity Bind alongside it. It is the independent decision and evidence layer: it tests, repairs and governs the matches those systems propose, and it will contradict them with a citation when they are wrong.

3. Access, credentials and accounts

You create your Entity Bind workspace online and verify your email, against a named tenant; as the workspace owner you create and revoke your own API keys in it, and OAuth clients are registered by us. A key carries exactly one scope, and the scopes are separate rather than layered: a resolve credential reaches one tenant's data plane and can provision nothing, and an admin credential reaches the provisioning surface and no customer data at all. You are responsible for keeping credentials secret, for the acts of anyone or anything you give one to — including an agent connected over the MCP server — and for telling us promptly if one is exposed, at which point we can revoke it with immediate effect rather than at the next expiry. The Free plan has a hard no-egress depth cap. Every workspace opens on it, and paid plans activate after confirmed Stripe subscription payment.

4. Your data, and what you permit us to do with it

You keep everything you send. You grant us a non-exclusive licence to process it for one purpose, which is answering the question you asked: normalising it, retrieving candidates, scoring, and where the record escalates, sending the populated fields of that record to a model provider for adjudication or research, as described in our privacy notice. We do not use your submissions to train models, we do not sell them, and we do not enrich a third party's dataset with them. You confirm that you are entitled to send us what you send, which matters most for the free-text context field and the extra map: those reach a model verbatim, and a CRM column mapped into extra carries whatever that column holds. We write nothing back into your systems, and there is no writeback connector to enable later.

5. What we do not warrant, starting with the match rate

We will provide the service with reasonable skill and care. We do not warrant a resolution rate, a match rate or an accuracy figure for your data, and no figure published on this site should be read as one. Every published number is a measurement over a named internal fixture, with its denominator, its interval and its caveat attached — the blended 95.75% is a blend across six input shapes whose value is set by the mix of shapes in the fixture rather than by the engine, and the same code resolves the identifier tier in full and the truncated-name tier in well under two thirds. Those fixtures are ours; they are not a customer holdout and not independent external validation. What your file does is an empirical question that a preview run answers and a contract cannot.

6. Confidence, abstention and the decision that is yours

A resolution is evidence for a decision, not the decision. The service will not bind a match below 0.90 confidence — that floor is a software invariant enforced on the online, batch and replay paths, so a sub-floor accepted match is unrepresentable rather than merely discouraged — and it abstains instead, returning a shortlist, a typed reason and a review id. An abstention is a correct answer and is not a service failure. Confidence reflects the evidence available for a recorded population and is not a guarantee for an individual answer. Confidence bounds depend on the recorded evidence population; there is no universal score for every match. Read match_confidence_basis and the evidence. A 0.99 filter can return some v8 adjudicated matches while excluding valid identifier matches, so validate its coverage cost on your own inputs. Where a resolution informs an action with consequences for a third party — a payment, an onboarding, a contract, a merge into a master record — you remain responsible for the action, and for any human review your own obligations require.

7. The licence you get to use the results

Subject to these terms, you may use the resolved records, confidence scores, citations, decision receipts and audit-pack files we return, for your own business purposes, indefinitely and without further payment, including after you stop using the service. That licence is perpetual on purpose: a decision receipt is an audit artefact, and one that expired with a subscription would be worthless the moment it mattered. You may share results inside your group of companies and with your professional advisers. You may not present them as your own independent verification of a company's identity to a third party who is relying on that verification, without saying where they came from.

8. Resale, and the open-licensed subset

Redistribution of facts to third parties is a separate right, and it is limited in two ways at once. It is available only on the Scale plan, and within that plan only for facts whose licence permits it. Every fact carries a licence tier, the persistence layer refuses to store a pass-through fact before any write happens, and each field's provenance publishes whether the underlying licence permits resale, so the boundary is checkable field by field rather than asserted tier by tier. In practice the resale-safe subset is the open-licensed one: Companies House under the Open Government Licence, GLEIF, SEC EDGAR, SIRENE and our own cited web observations. Licensed facts may be stored and used within the supplying contract without acquiring resale rights. Pass-through facts may be returned for permitted use but cannot be warehoused by this service. Nothing in this clause grants a right the underlying register does not, and where a register's own conditions require attribution, they pass through to you.

9. Uses that are prohibited

You may not use the service, or anything it returns, to make or inform an eligibility decision about an individual, including employment, credit, insurance, tenancy or access to a service. You may not use it to identify, profile, locate or screen a person, to build or enrich a people or contact database, or as a substitute for sanctions, politically-exposed-person or adverse-media screening. You may not attempt to reconstruct a bulk copy of any register through the API, share or resell access to your credentials, present the service to your own customers as your own product without our written agreement, or use it to build a competing entity resolution service. And you may not use it in a manner that breaches the conditions of the registers behind it, which are published on our coverage page.

10. Credits, and how a call is counted

Usage is counted in credits, on one rule, and the same module that quotes the price in the response writes the ledger row and serves the public pricing endpoint, so the number on the pricing page, the number in your usage block and the number recorded against you cannot drift apart. 1 credit: a decision reached by the deterministic or probabilistic stage. CPU only, no egress. 5 credits: a decision that needed LLM adjudication or agentic research. 0 credits: an abstention, at any stage, including the ones that spent the most getting there. 0 credits: a byte-identical replay. Per tenant, per exact content, and with no expiry. 0 credits: an input that normalised to no identifying signal. There was nothing to answer. Every response carries the usage block that records the count, and the reference endpoints publish the rate and the limits applying to your own key, so the arithmetic can be checked rather than believed.

11. Rate limits, quotas and depth

Every plan carries a rate limit and a monthly credit allowance, published on the pricing page and per-caller through the reference endpoint, and requests over the limit are refused with a rate-limit response and the headers describing when to retry rather than queued indefinitely. A deep resolution — one that reaches adjudication or agentic research — is separately capped, both per plan and by a concurrency limit, because it is the stage that spends money at a model provider. You can cap what any individual record is allowed to cost by setting a depth on the request, and the probabilistic cap is a hard no-egress mode enforced in code: a record capped there reaches no model provider and no registry.

12. Billing and payment

Free needs no card. Paid subscriptions are available through Stripe Checkout in workspace Billing, where you review the recurring price, applicable VAT and payment terms before purchasing. Paid plan access follows confirmed payment. Usage is metered separately and does not trigger automatic usage or overage charges. Nothing in this clause obliges us to keep the published prices unchanged, and nothing in it charges you for anything without your prior agreement.

13. Availability, and the absence of a service level

There is no uptime commitment, no status page and no performance guarantee, and this clause exists so that nobody infers one from the rest of the document. The request deadline and the deep-resolution allowance are arithmetic safety ceilings that stop a single request stacking timeouts, not latency measurements and not a service level. Backups are a nightly database dump with restores tested quarterly, giving a 24-hour recovery point objective and a four-hour recovery time objective; those are bootstrap objectives accepted deliberately by a small operator rather than enterprise ones. If your continuity standard sets tighter numbers, raise it on the first call rather than after signature.

14. Changes to the service and to these terms

We develop the product continuously and may change how a stage works, add or remove a register, or change a model or a prompt version. Two commitments constrain that. A change to the adjudication model or prompt is recalibrated before it ships and fails closed to abstention rather than quietly moving the confidence a caller is relying on. And we will not remove a published API endpoint, change a response field's meaning or reduce a plan's allowance without reasonable notice to the people using it. We will change these terms when the commercial position changes; the date at the top of this page is generated from the last time the words changed, and a change that affects an existing customer is notified directly.

15. Suspension, termination and getting your data out

Either of us may stop at any time, and neither of us has to give a reason. We may suspend access immediately where a credential is compromised, where use breaches clause 9, or where a call pattern threatens the service for other tenants, and we will tell you why. On termination your export path is the same one that is available throughout: the export endpoint streams every golden record in your tenant with its provenance, and the record and decision endpoints redeem the receipts behind them. Exercise it before you go. We will keep what remains for no longer than the retention windows in the privacy notice, and we will erase it sooner on request, subject to the limits that clause states about the audit trail.

16. Confidentiality and publicity

Each of us will keep the other's confidential information confidential, use it only to provide or receive the service, and protect it with no less care than we apply to our own. Those obligations survive termination. We will not name you as a customer, publish a case study, quote you or use your logo without your prior written consent, and consent to one of those is not consent to the others. Nothing in this clause prevents either of us disclosing information where the law requires it, provided we tell the other first where we lawfully can.

17. Liability, stated plainly

Neither of us excludes liability for death or personal injury caused by negligence, for fraud, or for anything that cannot lawfully be excluded. Subject to that, neither of us is liable to the other for indirect or consequential loss, loss of profit, loss of goodwill or loss of anticipated savings, and our total aggregate liability is capped at the fees you have paid us in the twelve months before the claim. For a customer using only Free, that fee-based figure is nil; a customer who needs a different cap must agree it in writing before relying on the service. We would rather have that conversation than let a reader assume otherwise.

18. Governing law, and how to reach us

These terms, and any dispute arising out of them or out of use of the service, are governed by the laws of England and Wales, and the courts of England and Wales have exclusive jurisdiction. For anything in this document, for an order form, or to ask what we can and cannot agree to, email hello@entitybind.com. For a security or data protection review, security@entitybind.com and privacy@entitybind.com are the faster routes.

Related documents

For anything in this document, for an order form, or to ask what we can agree to, email hello@entitybind.com.

the ask

Sending this to legal or procurement?

Bring the clauses your team wants moved. We will tell you which ones are negotiable, which are load-bearing — the scope limit and the eligibility prohibition are load-bearing — and where the honest answer is that the paperwork you are asking for has not been written yet.

Talk to usPlans and prices

For a guided review of your file, explore the Merge Safety Sprint →