Terms

1. Scope

What these terms cover — the website, the RFQ process and any engagement they lead to — and what they do not.

These terms apply to your use of datapink.net, operated by Datapink LLC, Ukraine, Vinnytsia, and to any request for quote you send us through it.

Using the site means you accept these terms. If you do not accept them, do not use the site.

These terms do not by themselves create an engagement. Work is done under a separate written agreement between us and the customer. Where that agreement and these terms say different things about the same subject, the agreement decides.

Nothing on this site is an offer capable of acceptance, a quotation, or advice you should act on without your own assessment. We may change the site, and these terms, at any time; the version in force is the one published here, with its date and version number at the top of the page.

2. Services and deliverables

How a service or dataset is described, and where its definitive scope lives — the agreed Dataset Specification, not this page.

The service and dataset pages on this site describe what we do in general terms. They are descriptive, not contractual, and they do not commit us to any particular scope, method, format or result on your project.

What we will actually deliver to you is set out in the agreed Dataset Specification for that project, together with the agreement it sits under. Where the site and the Specification differ, the Specification governs.

We may use subcontractors for parts of the work. Where we do, we remain responsible to the customer for that work under the agreement.

3. Dataset Specification and acceptance

How a Dataset Specification is agreed, how delivered data is checked against it, and what acceptance means.

Each project starts with a Dataset Specification agreed in writing by both parties. It records the scope, the sources and the source policy, the languages and domain, the schema and formats, the quality criteria and how they are measured, the provenance and lineage fields, and what is excluded.

Delivered data is checked against that Specification and against the acceptance criteria it states. The results of those checks are delivered with the data.

After delivery, the customer has the review period agreed in the Specification to check the delivery against those criteria and to raise, in writing, anything that does not meet them. Where something does not meet the agreed criteria, we correct or replace the affected part. Acceptance means the delivery meets the criteria in the Specification, and nothing more than that.

A change to scope, criteria or format after the Specification is agreed is a change to the Specification, agreed in writing, with its effect on timing and price stated at the same time.

4. Intellectual property and licences

What rights are granted in delivered data and materials, and what stays with Datapink or with the original source.

The site itself — its text, diagrams, layout and code — belongs to us. You may read it, quote it with attribution and link to it; you may not republish it as your own or use it to train a model without our written permission.

Rights in a delivered dataset are granted in the agreement and the Specification for that project, and only there. Nothing on this page grants a licence to any dataset.

Our own methods, tooling, pipelines, schemas, configuration and know-how remain ours, including where they were used or improved on your project. Material you give us stays yours.

Where a dataset is built from third-party sources, the rights in the underlying material remain with whoever holds them. What we can pass to you is limited by what those rights, and any licence we hold, allow. The rights position for each source is recorded in the source registry delivered with the release, and we do not represent that a dataset is free of third-party rights.

5. Confidentiality

How project information, source lists and unreleased deliverables are protected on both sides.

Each party keeps the other's confidential information confidential, uses it only for the project, and shares it internally only with the people who need it for that project and who are under equivalent obligations.

Project information, source lists and registries, specifications, unreleased deliverables and pricing are confidential on both sides.

This does not cover information that is already public without a breach, that a party already had, that a party develops independently, or that has to be disclosed by law or by a court — and in that last case the disclosing party tells the other where it is permitted to do so.

Do not send confidential material or private source URLs through the forms on this site. Use the agreed confidential route once one is in place.

6. Liability

How liability is allocated and limited between the parties for work under these terms.

The site is provided as it is. We take care that it is accurate, but we do not promise that it is free of error or always available.

Data acquired from external sources reflects those sources. We do not accept liability for what a source contained, for a decision you take on the basis of a dataset, or for the behaviour of a model trained on one.

Neither party is liable to the other for indirect or consequential loss, for loss of profit, revenue, goodwill or anticipated savings, or for loss or corruption of data on the other party's own systems.

Our total liability arising out of a project is limited to the amount stated in the agreement for that project. Where the agreement states no such amount, it is limited to the fees paid for the work in question.

Nothing here excludes liability that cannot be excluded by law, including liability for fraud or for death or personal injury caused by negligence.

7. Termination

How an engagement can be ended by either party, and what happens to data and payment already in progress.

Either party may end an engagement on the notice stated in the agreement for that project. Either party may end it immediately in writing if the other is in material breach and has not put the breach right within a reasonable period after being told about it.

On termination, we stop work, and the customer pays for work carried out and commitments properly made up to that point.

Work in progress is handed over in the state it has reached, in the agreed formats, so far as the licence position for the underlying sources allows it to be handed over at all.

Each party returns or deletes the other's confidential information on request, except for copies it has to keep for its own records or by law. Confidentiality, intellectual property, liability and governing law survive termination.

8. Governing law

Which jurisdiction's law applies and where a dispute under these terms is heard.

These terms are governed by the law of the country in which Datapink LLC is established — Ukraine, Vinnytsia — and the courts there hear any dispute arising out of them.

A project agreement may state a different governing law and forum. Where it does, that choice applies to that project.

Before starting proceedings, each party will raise the matter in writing with the other and try in good faith to settle it.

Questions about these terms go to our Legal Team at [email protected].