Skip to content
EasyData docs
QuickstartAPI referencePricingOpenAPISign inTalk to sales
Docs/Legal

Terms of service

The agreement behind an EasyData API key: what a credit costs, what you may do with the records, and where the liability sits.

Effective 20 September 2026 ยทPrivacy policy

On this page
  • The service
  • Your account and your keys
  • Credits, payment and tax
  • What you may not do with the records
  • Suppression requests reach you too
  • Availability and capacity
  • Suspension and termination
  • A record is what the source said
  • Warranties and liability
  • Indemnity
  • Confidentiality
  • Changes to these terms
  • Law and venue
  • The whole agreement
  • Contact

EasyData is the data enrichment API at easydata.win, together with the console and the documentation site that go with it. In this document "we", "us" and "EasyData" mean the operator of that service, reachable at [email protected], and "the service" means the API, the console and this site together.

These terms are the agreement between us and the business that holds the account. Signing in, buying credits, calling the API with a key we issued, or paying an invoice is acceptance of them. If you are agreeing for a company, you are stating that you are allowed to.

There are two ways to hold an account, and both are covered here. You can buy credits in the console and start calling straight away, or you can agree an allowance and rate limits with us by email. Where a signed order exists it sits on top of this document, and where the two disagree the order wins.

The service #

EasyData takes identifiers - profile URLs, company URLs, post URNs, a pasted Sales Navigator search URL - and returns structured records for them. Everything is a batch, including a batch of one, and there is a synchronous path that creates the same batch, drains it inside your request and costs double. What each operation costs is published on this site and in the OpenAPI specification.

We may add, change or withdraw operations. If we withdraw one you are calling, or make a breaking change to a response shape, we tell account holders at least 30 days beforehand, and your unspent credits are refundable in full if you would rather stop there - with no time limit on that particular reason.

Your account and your keys #

  • A key is a bearer credential. Anything done with it is done as you and is your responsibility, so keep it out of browsers, mobile apps and public repositories.
  • Tell us the moment a key leaks and we revoke it. You can revoke and mint keys yourself in the console at any time.
  • One account is one business. Do not resell access by handing your key to somebody else's application - buy them their own, or talk to us.
  • Keep the account email reachable. It is where the verification link, the invoice and the breaking-change notice go, and an unverified account cannot spend the default allowance.

Credits, payment and tax #

  • One credit is one request to LinkedIn. A Sales Navigator search is quoted per request, at 50, because one request there returns a hundred search stubs rather than one record. A failure is zero.
  • Credits are quoted to one decimal. What a credit costs in money is published on the pricing page and falls with the size of the order.
  • Credits are prepaid: they are invoiced, and they are added to the account once the invoice is paid. They do not expire, there is no renewal date and there is no overage charge - when they run out, requests are refused until more are added.
  • Credits and any agreed monthly allowance are invoiced in the currency and on the cycle the order names, and payable within 15 days of the invoice date.
  • Prices in an agreed order hold for its term. Published list prices can change, and a change never reaches back into credits already bought or an order already running.
  • We invoice you directly and the invoice states any tax that applies. There is no card payment in the console and nothing is charged automatically.
  • Refunds are covered by the refund policy, which forms part of this agreement.

What you may not do with the records #

The service returns information about real people, and most of this section is about them rather than about us.

  • Do not use a record to send unsolicited bulk mail or messages in breach of the law that applies to the recipient - the GDPR and the ePrivacy rules, CAN-SPAM, CASL, whichever is theirs.
  • Do not use a record to decide anything about a person's employment, credit, insurance, housing or eligibility for a benefit. This is not a consumer reporting service, it is not built to be one, and using it as one breaks the law in several countries.
  • Do not use records to discriminate on race, sex, age, religion, disability, sexual orientation or any other protected characteristic, and do not derive such a characteristic from what we return in order to.
  • Do not build a public directory, a resale database, or any product whose value is republishing our output as a dataset. Enrich your own systems with it; do not become a second copy of the source.
  • Do not use it to harass, stalk, dox or threaten anybody.
  • Do not work around rate limits, quotas or the key system - several accounts to lift one ceiling, keys spread across machines to outpace an allowance, retries designed to do the same.
  • Do not reverse engineer, resell, sublicense, or publish a benchmark of the service without asking us first.
  • Do not use the service where doing so breaks a law that applies to you, including sanctions and export control.

You are the controller of every record from the moment we hand it over. That means a lawful basis of your own, the notice and the rights requests that come with it, and a data processing agreement with us if you want one - ask and we send it.

Suppression requests reach you too #

A person can ask us to remove their profile from the service and we honour it. When we do, that profile stops resolving for everybody, including you, and if they ask us to we forward the request on: deleting the copy you already hold is then your obligation and not ours. This is not us changing the deal mid-way. It is the same law that lets you hold the record at all.

Availability and capacity #

We work to keep the API up and we do not promise a number on this page. If your order carries an availability target or a support response time, that is where it lives and it binds us; without one, the service is provided as it stands.

Capacity is finite and shared. Rate limits and the agreed pace exist so that one customer's Tuesday does not become everybody's. We may throttle or queue work that threatens the pool, and we tell you when we do.

Suspension and termination #

  • We may suspend a key immediately if it is being used in breach of the section above, if it has leaked, or if an invoice is more than 30 days late. Except for a leak or a legal obligation, we tell you first and give you the chance to fix it.
  • Either of us may end the agreement on 30 days of written notice, and either may end it at once if the other is in material breach and has not cured it within 14 days of being told.
  • On termination your keys stop working and your data is deleted on the schedule in the privacy policy. Ask before that point and we export what you have.

A record is what the source said #

Records reflect what a public page said at the moment it was read. People edit profiles, companies rename themselves, posts are deleted, and LinkedIn changes what it publishes. We do not warrant that a record is accurate, current or complete, and a record you disagree with is not a failed request: a failure is a request that did not resolve, and those cost nothing.

Warranties and liability #

Beyond what these terms say, the service is provided as it is, and we disclaim every implied warranty the law lets us disclaim - merchantability, fitness for a particular purpose, non-infringement.

Neither of us is liable to the other for indirect, incidental, special or consequential loss, or for lost profit, revenue, goodwill or data, however it arises. Our total liability for everything connected with this agreement is capped at the fees you paid us in the twelve months before the claim.

Nothing here limits liability for death or personal injury caused by negligence, for fraud, or for anything else the law does not permit to be limited.

Indemnity #

You cover us against third-party claims arising from what you did with the records - who you contacted, what you decided, what you published - where that use broke these terms or the law. We tell you about such a claim promptly and let you run the defence.

Confidentiality #

Each of us keeps the other's non-public information to itself - your volumes and your pricing, our architecture and our rates - and uses it only for this agreement. It does not cover anything already public, independently developed, or demanded by a court.

Changes to these terms #

We may update them. A material change is emailed to account holders at least 30 days before it takes effect, and calling the API after that date is acceptance. If you would rather not accept it, tell us before the date and we refund every credit you have not spent, in full.

Law and venue #

Where your order names a governing law and a place for disputes, that is what applies. Failing one, this agreement is governed by the law of the place where we are established and a dispute goes to the courts with jurisdiction there. Neither of us is stopped from asking any court for an injunction to protect its own intellectual property or confidential information.

The whole agreement #

These terms, the privacy policy, the refund policy, the published price list and any order you have signed are the whole agreement between us and replace anything said beforehand. If one clause turns out to be unenforceable, the rest stands. Neither of us waives a right by not enforcing it once.

Contact #

Contract questions go to [email protected], commercial ones to [email protected], and anything about personal data to [email protected].

Win with EasyData
Docs homeAPI referenceQuickstartPricingOpenAPIllms.txtConsoleTalk to salesPrivacyTermsRefunds