Datasets Marketplace Terms (ETHERANE)
Effective date: 1 August 2026 · Version 1.0
These terms govern the datasets marketplace on ETHERANE, operated by APERTURESyndicate OÜ. They apply to you whether you list a dataset for sale ("seller"), or acquire one ("buyer") — free datasets included.
These are product-specific terms. Under Section 3 of the Terms of Service they sit below the platform-wide documents: they add detail and may impose stricter rules, but where they appear to conflict with the Terms of Service, the Acceptable Use Policy, the Privacy Policy or Refunds & Cancellation, the platform-level document controls.
Read Section 4 before you rely on anything a listing claims about its contents. It is the most important part of this document and the least flattering to us.
We write these documents in good faith and keep them accurate to how the platform actually works. They have not yet been reviewed by qualified Estonian legal counsel.
1. What the marketplace is
The datasets marketplace is a venue. Sellers list data they have prepared; buyers acquire the right to use it. We provide the listing pages, the storage, the payment rail and the delivery mechanism.
We are not a party to the transaction between you and the other side beyond that. We do not create, curate, verify, clean, license or endorse the datasets on the marketplace. We are not the data controller for what is inside a dataset a seller uploads — the seller determines that content, and where it contains personal data the seller is the controller and answers for it.
Everything on the marketplace is user content for the purposes of the Terms of Service and the Acceptable Use Policy.
2. Who can use it
You need a APERTURESyndicate account and you must be at least 16 (Section 4 of the Terms of Service).
To sell, you must additionally complete payout onboarding with Stripe, which creates a connected account in your name and carries out its own identity and compliance checks. Until Stripe enables charges on your account you can create listings but you cannot sell a paid one. Stripe's terms apply to you directly in respect of that account; see Data Processing & Sub-processors.
If you are selling in the course of a business, you are responsible for your own tax and invoicing obligations arising from your sales.
3. What a seller warrants
For every dataset you list, and for as long as it remains listed, you represent and warrant that:
- You have the rights. You own the data, or you hold every licence, consent and permission needed to distribute it on the terms you have chosen — including from anyone whose work, database rights or contributions it contains.
- It contains no personal data. The dataset does not contain personal data within the meaning of the GDPR — no names, emails, phone numbers, addresses, identifiers, biometric data, or any other information relating to an identifiable person — unless you have a lawful basis for distributing it and you have stated this prominently in the listing. Never list special categories of personal data (health, biometrics, sexual life, religion, politics, trade-union membership, ethnic origin) or data about children.
- It was not obtained unlawfully. It was not scraped in breach of a service's terms, taken from a breach or leak, obtained through unauthorised access, or acquired in breach of a confidentiality obligation.
- It is what the listing says it is. The description, modality, record count, size, format and licence label are accurate and not misleading.
- It is not prohibited under Section 10.
You are solely responsible for the composition of your dataset. If you are unsure whether something in it is personal data, do not list it until you are.
4. What we check before a dataset goes live — and what we do not
We are stating this plainly because a listing page can give the opposite impression.
Nothing inspects the contents of your dataset before it is published. When you submit a dataset, an automated job converts what it can into a common format and then marks the dataset as published. That job does not open your files looking for personal data, does not run any detector, and cannot fail. There is no human review queue and no approval step.
The "PII scan" indicator is not a scan. A listing may display a passport line reading that a PII scan passed with zero entities flagged. That line is written automatically for every dataset that reaches publication, regardless of content. It reflects no examination of the data.
Therefore:
- Buyers: do not rely on that indicator, or on the "PII clean" filter, as evidence that a dataset is free of personal data. Treat it as unverified seller-side metadata. Inspect what you buy, and satisfy yourself that using it is lawful for your purpose — especially if you intend to train a model on it.
- Sellers: the indicator gives you no protection whatsoever. Your warranty in Section 3 is what you are held to, and the fact that a dataset was published tells you nothing about whether it should have been.
We are describing a limitation of what we currently run, not promising to keep it. If we build a real check, we will describe what it actually does — and this Section will change to match.
Our moderation is reactive: we act on reports, on orders from authorities, and on what we otherwise become aware of. See Section 11 and Section 11 of the Acceptable Use Policy.
5. Uploads and formats
Datasets are uploaded as files to our storage. Practical limits — the maximum size of a single file and the file types accepted — are enforced at upload and shown in the product. Some formats can be converted into a common structure automatically; anything we cannot parse is still stored and delivered as you uploaded it, without conversion.
Free sample files you mark as such, and a short preview of the parsed records, are publicly accessible without purchase and without an account. Do not mark anything as a sample that you are not willing to give away.
6. Price, our commission, and payouts
- You set the price, in EUR. A price of zero makes the dataset free; free datasets involve no payment and no commission.
- We take a commission on each paid sale — currently 10% of the sale price. It is deducted automatically at the time of the transaction, and the remainder is transferred to your connected Stripe account. If we change the rate, we will give at least 30 days' notice.
- Payouts are made by Stripe on its own schedule to the bank details you gave it. We do not hold your money, and payout timing is not something we control.
- Tax. VAT is handled at checkout according to the buyer's location. You are responsible for your own tax position on the income you receive.
7. What a buyer gets
On completing a purchase — or acquiring a free dataset — you receive a non-exclusive, non-transferable, perpetual right to download and use that dataset, on the terms of the licence label the seller selected:
| Label | What the seller is telling you |
|---|---|
| CC0 | Dedicated to the public domain; use for anything, no attribution required |
| CC-BY | Use for anything, including commercially, with attribution |
| Commercial | Licensed for commercial use, including model training, by you |
| Research | Non-commercial research use only |
These labels are declarations by the seller, not licence agreements drafted by us. No licence text is attached, and nothing technical enforces them. If the precise scope matters to you — and for model training it usually does — ask the seller before you buy, in writing.
Your rights are personal to your account. You may not resell, redistribute, sublicense or publish the dataset itself, or make it available to third parties, unless the licence label plainly allows it. Using a dataset does not transfer any ownership to you.
Delivery is by time-limited download links generated on request. You can download as many times as you like while your access is active. Keep your own copy: we do not guarantee that a dataset will remain available for download indefinitely, and Section 9 explains when it may disappear.
8. Withdrawal and refunds
Your 14-day right of withdrawal applies. A dataset purchase is a distance contract for digital content. EU law allows a trader to remove the withdrawal right for digital content delivered immediately, but only with your prior express consent and your acknowledgement that you are losing the right. Our checkout asks for neither, so you keep the full 14 days — see Section 2 of Refunds & Cancellation, which governs.
To withdraw or to ask for a refund, write to [email protected] from the email address on your account, naming the dataset and the order. Refunds are processed back to the original payment method.
What a refund does. Your access to the dataset is revoked. Files you already downloaded are, of course, on your machine — we cannot recall them, and we do not try to. Continuing to use a dataset after being refunded for it is a breach of these terms and of the seller's rights.
Fairness both ways. Because the withdrawal right survives download, systematically buying datasets, downloading them and withdrawing is abuse of the mechanism rather than use of it. We may act against an account doing so under the Acceptable Use Policy, to the extent mandatory consumer law permits.
Sellers: where a buyer withdraws or a payment is reversed, the sale is undone and the corresponding amount is not yours. Where the reason is a defect in the dataset — it is not what the listing claimed, or it turns out to contain material you had no right to distribute — the loss is yours, not the buyer's and not ours.
9. Taking a listing down
As a seller, there is currently no self-serve way to unpublish, edit or delete a listing. To withdraw one, write to [email protected] and we will do it. We are stating this because the absence of a button is easy to mistake for a policy.
We may take a dataset down where it breaches these terms, the Acceptable Use Policy or the law, where a valid notice or an authority order requires it, or where continuing to host it would expose us or others to legal risk. You receive a statement of reasons under Section 5 of DSA Notice & Action.
What a takedown does and does not do. It removes the listing from the marketplace. It does not delete copies that buyers have already downloaded, and it does not by itself revoke buyers' existing access rights. If a dataset is taken down because it contains personal data or infringing material, the honest position is that the data is already out and the remedy is with the people who hold it, not with the listing page. This is one more reason Section 3 matters.
Personal data found after publication. If you become aware that a dataset you sold or bought contains personal data, tell us at [email protected] with the subject "GDPR request". We will take the listing down and notify the other side. Sellers must stop distributing it anywhere else; buyers must delete their copies unless they have an independent lawful basis to keep them.
10. Datasets that may not be listed
You may not list:
- personal data, except as narrowly permitted by Section 3(2); never special categories, and never data about children;
- data obtained from a breach, leak, unauthorised access, or credential dump;
- data scraped in breach of a service's terms or in breach of technical protection measures;
- copyrighted works, databases or collections you do not have the right to distribute;
- content that is illegal, or whose purpose is to enable illegal activity — including datasets assembled to identify, profile or target individuals or a protected group;
- child sexual abuse material or any sexualised material involving minors, in any form, synthetic included — this ends the account immediately and is reported to the authorities (Section 2 of the Acceptable Use Policy);
- malware, exploit kits, or data whose primary use is to compromise systems; or
- anything else the Acceptable Use Policy prohibits.
11. Reporting a dataset
If a listing infringes your rights, contains personal data about you, or breaks these rules, tell us:
| What | Where |
|---|---|
| Personal data about you in a dataset | [email protected] — subject "GDPR request" |
| Copyright or database-right infringement | [email protected] — see Copyright & Takedown |
| Illegal content generally | [email protected] — subject "Illegal content" |
| Anything else | [email protected] |
We aim to acknowledge within 72 hours. What happens next, and what we do and do not offer by way of appeal, is in DSA Notice & Action.
12. Liability
Between seller and buyer. The seller is responsible for the dataset — its contents, its lawfulness, its accuracy, and the rights they claim to grant. If a dataset turns out to be misdescribed, infringing, or full of personal data, the seller answers for it. If you are a seller acting in the course of a business, you indemnify us against claims arising from a dataset you listed; this indemnity does not apply to consumers.
Our position. We provide the venue "as is". We do not warrant that any dataset is accurate, complete, lawfully sourced, free of personal data, fit for training a model, or free of third-party rights. Our liability is limited as set out in Section 15 of the Terms of Service, and nothing here excludes liability that cannot lawfully be excluded — including your statutory conformity rights as a consumer against us for the marketplace service itself.
13. Suspension, termination and changes
We may suspend or close a seller account, or revoke marketplace access, for breach of these terms or the Acceptable Use Policy, for fraud or chargeback abuse, or where the law requires it. Section 11 of the Terms of Service governs.
If you close your APERTURESyndicate account, your listings are withdrawn and your buyers' existing access is unaffected. Sales already made are not reversed, and records we must keep for accounting purposes are retained for 7 years (see Data Retention).
We may change these terms; material changes get at least 30 days' notice under Section 17 of the Terms of Service.
Contact
| Purpose | Contact |
|---|---|
| Marketplace questions, withdrawing a listing | [email protected] |
| Payments, refunds, withdrawal | [email protected] |
| Personal data in a dataset | [email protected] — subject "GDPR request" |
| Copyright | [email protected] |
We accept correspondence in English or Estonian.
APERTURESyndicate OÜ Registry code 17384111 · VAT EE102972654 Priisle tee 8, Lasnamäe linnaosa, Tallinn, Harju maakond, 13914, Estonia Company registration details
These terms are governed by the law of Estonia, with the courts of Tallinn having jurisdiction, and are subject to the GDPR, the EU Digital Services Act, and applicable Estonia and EU consumer-protection law. The English-language version is the controlling version.
Version history
- v1.0 — 2026-08-01 — Initial publication. Written against the marketplace as built, including an explicit statement that the automated personal-data check does not inspect dataset contents and that the "PII scan" indicator shown on listings is generated unconditionally.