Legal

Privacy policy

What personal data we collect, why, who we share it with, how long we keep it, and your rights.

Version 1.1 · effective 2026-11-06

This policy explains what personal data ModelData Exchange (we, us) collects through modeldataexchange.com and the platform behind it, why, who we share it with, how long we keep it, and the rights you have. It applies to website visitors, people who contact us, and the people who use buyer, data partner and staff accounts.

1. Who we are

ModelData Exchange operates modeldataexchange.com and is responsible for the personal data described here (the data fiduciary under India's Digital Personal Data Protection Act, 2023, and the controller under the EU and UK General Data Protection Regulation, where they apply). For anything about your personal data, or a grievance about how we handle it, email hello@modeldataexchange.com with "Privacy" in the subject. We'll reply within 30 days.

2. What we collect

  • What you send us in forms: your name, work email, company and role, and what you write about the data you need, the data you own, or your question.
  • Account details: your name, email, organisation, the role you hold in it, contact phone, password (stored only as a one-way hash), and your sign-in history, including the devices you signed in from.
  • Billing details: your organisation's billing name, address, tax or VAT number, billing email and purchase-order references.
  • For data partners: legal name and country, tax details, and bank details for payouts. Bank and tax details are stored encrypted, and only finance staff can view them.
  • Repository access: the GitHub or GitLab usernames you give access to licensed data, and, for data partners, the details of the repository connection you authorise.
  • Signatures: for agreements you sign on the platform, your name, title, the signature you draw or type, the time, and a fingerprint of the signed text.
  • Technical data: a salted hash of your IP address (never the address itself in our records) for abuse prevention, your browser's user agent, and server logs. Error reports, when enabled, have cookies, tokens and passwords removed before they are sent.

We don't ask for sensitive personal data. Please don't send it to us, or data or source code by email or in forms.

3. Why we use it

  • Answering your enquiry: replying, following up, and turning a request into a tracked buyer request. Basis: your consent, given in the form.
  • Running your account: signing in, security checks, notifications and emails about your account. Basis: you give us these details to use the platform (a legitimate use under the DPDP Act; performing our contract under the GDPR).
  • Deals and payments: proposals, agreements, invoices, payments and supplier payouts. Basis: the contract you asked for, and legal obligations (tax and accounting).
  • Rights and safety: reviewing who owns submitted data, and handling rights complaints and security reports. Basis: legal obligations and, under the GDPR, our legitimate interest in keeping licences lawful.
  • Protecting the platform: rate limits, bot filtering and audit logs. Basis: preventing fraud and abuse, a legitimate use under the DPDP Act and a legitimate interest under the GDPR.

Where we rely on your consent, you can withdraw it at any time by emailing us; this doesn't affect what we did before, and we'll then stop, unless the law or a contract requires us to keep the data.

We don't sell personal data, and we don't use it for advertising.

4. Who we share it with

  • Service providers that run the platform for us, under contracts that limit them to our instructions: hosting and database, private file storage, email delivery (Resend), payments (Stripe), error monitoring (Sentry, when enabled) and font delivery (Google Fonts).
  • Stripe receives card and identity details directly when you pay by card or set up Stripe payouts. They never pass through our systems.
  • GitHub or GitLab, when you connect a repository or are given read-only access to licensed data.
  • The other side of a deal, only as far as the deal needs it. Data partners never see who the buyer is; buyers see the dataset, not the data partner's personal data.
  • Authorities, when the law requires it.

Some of these providers process data outside your country, including in the United States. Where the law requires it, we rely on safeguards such as the European Commission's standard contractual clauses.

5. How long we keep it

  • Enquiries that don't become a deal: 24 months after the last activity, then deleted.
  • Enquiries that became a request: 24 months after the last activity, then contact details are anonymised.
  • Rejected dataset submissions: 12 months after the decision, then deleted with their files.
  • Rights evidence and decisions: the life of any licence, plus 7 years.
  • Contracts, invoices, payments and payouts: 8 years (tax and accounting).
  • Audit log: 1 year in the database, 7 years in total in archived storage.
  • Your account: while it is open. When an account is closed, your personal details are deleted or anonymised within 30 days, except what the records above require us to keep.
  • Signed agreements and their signing records: as long as the contract they belong to (8 years after it ends).
  • Buyer requests and support cases: with the deal or case they belong to; contact details follow the enquiry rules above.
  • Sessions, sign-in links and invitations: deleted 30 days after they stop being usable.

A daily job applies these periods automatically. Money and rights records are kept for their legal periods.

6. Your rights

You can ask us to give you a summary of the personal data we hold about you, correct or complete it, delete it (where we don't have to keep it), or stop using it for a purpose you consented to. Where the GDPR applies, you can also object to processing based on legitimate interests and ask for your data in a portable format. Under India's DPDP Act you can also nominate someone to exercise your rights if you die or become unable to.

Email hello@modeldataexchange.com. We'll reply within 30 days. If you aren't satisfied with our answer, you can complain to the Data Protection Board of India, or to your local data protection authority in the EU or UK.

7. Security

We protect personal data with encryption in transit, encryption of bank and tax details at rest, role-based access, mandatory multi-factor authentication for staff, private file storage, and an append-only audit log. See our Security page for details and for how to report a vulnerability. If a breach affects your personal data, we'll tell you and the authorities as the law requires.

8. Children

The platform is for businesses. It isn't directed at children, and we don't knowingly collect children's personal data.

9. Changes

We'll post any change to this policy here with a new effective date, and tell account holders by email about significant changes.