Where our data comes from

Who is responsible

The Dug Media Ltd (Private Limited Company de droit chypriote) publishes ELDB and is the data controller. See the legal notice.

Who uses this data

Our customers are businesses. They contact the stores, not us. Under our terms of sale, they agree not to resell the data and to respect your right to object. Read the terms of sale.

How we find stores

We start from public lists of domain names: AFNIC open data for .fr domains, public lists of domains and stores, public certificate logs and public web archives. We then check that the site really is an online store.

What our crawler reads on the site

Only public pages, with no account and no form:

• the robots.txt file, before any other page;
• the home page;
• the contact page;
• the legal notice page, or its equivalent in the store's country;
• the sitemaps;
• on Shopify: /meta.json, /products.json, /policies/legal-notice and /policies/contact-information;
• on WooCommerce: the public "Store API";
• on Magento: the public REST product API, for a single product (the total count);
• the public catalog, up to 5,000 products.

How to recognise and block it: our crawler page.

Public Google listings

For each store, we read its public Google Business listing, if there is one: name, categories, rating, number of reviews, address, phone, opening hours, map position. It is read again about every 90 days.

Traffic figures

Traffic and keyword estimates come from a third-party SEO tool. They were collected until October 2026 and are no longer updated. They describe the site, not people.

Chrome audience

Every month, we match stores against Google's Chrome UX Report popularity ranking, by country. A store ranked "top 50,000" in France is one of the 50,000 sites most visited by Chrome users in France. A store missing from the ranking is not on it, most often because its audience is too small. This data comes from the Chrome UX Report (Google), under the CC BY-SA 4.0 license; the audience field is shared under the same license. Ranks matched to stores and grouped by country by us.

DNS signals

We read the public DNS records of each store (MX, TXT, DMARC), just as any mail server does. From them we work out its email provider, its email sending tools and the tools that verified its domain. We never contact its servers and we keep no verification token.

Public tracking IDs

We read the public tracking and ad codes (Google Ads, Meta, TikTok…) that each store leaves in its home page and in its public Google Tag Manager container, just as any visitor's browser does. They let you find the other stores that share the same code. We never log in anywhere and we read no private data.

Company officers and named emails

We read company officers from the public company registries (the national business register in France, the commercial register in Switzerland) and from the store's legal notice page. In Belgium, we keep only company data from the BCE: Belgian officers come only from the store's own site. For each officer, we look for their work email on the site, or we work it out from the domain's address format and check it with the mail server, without ever sending a message. We keep no birth date, no nationality and no home address.

Our customers' enrichment results

A customer can enrich a store's decision makers with their own Apollo, FullEnrich, Kaspr or Dropcontact account. These results are not ELDB data: they stay with that customer, and no other customer sees them.

Postal reference lists

To check postcodes and town names, we use these public lists:

• France: La Poste's "Base officielle des codes postaux", and INSEE municipality names through geo.api.gouv.fr. Licence Ouverte v2.0 (Etalab).
• Belgium: SPF BOSA's "BeST Address". CC BY 4.0 licence.
• Switzerland and Liechtenstein: swisstopo's official directory of towns. © swisstopo.

What we keep for each contact

For an email, a phone number or an address read on the site, we keep:

• the value;
• the address of the page where we read it;
• the date we read it.

We also note the email's type: generic (contact@, info@…), personal (firstname@…) or unknown.

What our customers get

• The contact email, with its type, the page it was read on and the date. A personal email is therefore provided, labelled as such.
• A customer can ask for generic emails only.
• An address removed by its owner is never provided.
• Company officers: first name, last name, role and source. Their work email comes with its status: found on the site, checked with the mail server, or only worked out. A customer who asks for generic emails only receives no officer email.

For how long

• After 11 months, the store is checked again. A contact still published gets a new date.
• After 12 months without being seen again, a contact is no longer provided to our customers.
• After 13 months, it is erased from the database by a monthly cleanup.

These rules cover the emails, phone number and address read on the store's site, and the company officers and their emails.

Remove your data

You can remove your email address, or your whole store. The removal takes effect as soon as you confirm it through the link sent by email. For a store, the data is erased 30 days later. Remove my store.

Block our crawler

Our crawler respects robots.txt. It follows the "User-agent: ecommerce-data-enrich" and "User-agent: ecommerce-data-scan" groups, or else the "User-agent: *" group. See our crawler page.

A question? hello@ecommerce-leads-database.com