selldata.uk

Privacy

Updated Sources UK company guides · How we make money

selldata.uk is published by Ingenious Digital LLC, which is the controller of the personal data described on this page. We count visits, and we record clicks on our Apply buttons and the answers you give to the eligibility check. Our own code sets no cookies. We do not sell personal data.

This page covers selldata.uk only. When you click Apply, our own address records the click and sends you on to the buyer’s site. What you enter there is handled under that site’s privacy policy, so read it before you share company details there. Our disclosure explains how we are paid.

Visits and page speed

We use Cloudflare Web Analytics to count visits and measure page speed. Cloudflare says the service uses no cookies or other storage on your device and does not fingerprint visitors. We use the figures to see which pages are read and to improve the site. Our lawful basis is legitimate interests (Article 6(1)(f) of the UK GDPR): understanding how the site is used.

Apply clicks

When you click an Apply button, the click goes through our own address and on to the buyer’s site. For each click we keep the time, the page and button, your country, whether the visit looks like a bot, and how you reached the site as one broad class. Cloudflare works out the country from your IP address. The class is a short label such as google, chatgpt or direct. We also keep the first page you landed on and, when there is one, the lead token of the check you completed, which links the click to that check. We do not keep your IP address, a hash of it or the address of the page you came from, so nothing in a click record identifies you.

We use these records to see which pages and buttons lead to registrations and to check our counts against the buyer’s referral dashboard. Our lawful basis is legitimate interests: knowing which of our guides help readers.

The eligibility check

The eligibility check asks for your company’s headcount band, status, location and, if you choose, the kinds of records it holds. Every answer is a choice from a list, and nothing is uploaded. For each check we keep the time, your answers, your result, the decision page and the first landing path (without its query or fragment), your country, the broad class above, a random lead token and, for a result saved with JavaScript, a random key that prevents duplicate saves of that result. As with clicks, we keep no IP address or hash of one, so nothing in a check record identifies you.

We use the answers to show your result and to see what kinds of companies use the check. Our lawful basis is legitimate interests. The result comes from fixed rules and has no legal or similarly significant effect on you. It is preliminary, and the buyer decides who qualifies.

The check does not ask for your email address.

Who receives your information

Cloudflare hosts the site, so it handles your IP address and the details of each page request. It also runs our database and the analytics for us. We share your information with no one else. We do not pass your answers to the buyer. Your browser sends the buyer’s site our referral link, as it would for any link.

Outside the UK

Cloudflare may process information outside the UK, including in the United States. We ask it to keep our database in eastern North America. Its data processing terms say that transfers out of the UK rely on the EU standard contractual clauses with the UK Addendum, and recognise the UK-US extension of the EU-US Data Privacy Framework. They also set out the safeguards.

How long we keep it

We keep each Apply click, and each eligibility check submission, for 90 days from the day it was recorded. After that we remove or anonymise it: we add it to a daily total and delete the record. The removal runs once a day, so a record can stay up to a day past its limit. A click total holds the day, the page, the button, the partner, whether the visit looks like a bot and the broad class for how you reached the site, plus a count. A check total holds the day, the page, the result, the headcount, status and location answers and the same broad class, plus a count. Neither holds a country, an email address, a lead token, a result key, a first landing path or a record number.

We also count save acknowledgements from the server and save outcomes observed by the page, separately. These counters hold only the day, site, source (server or page), saved or failed outcome and count; they contain no visitor fields and are deleted after 90 days. Deletion-run totals contain no visitor fields and are kept indefinitely. They count attempts, while completed checks are answer submissions; email-only follow-ups are separate. Entry context is added to the internal page link you follow when you interact with it, without cookies or browser storage. An arrival from outside the site starts its own context. The random result key stays in page memory and is sent only with the save; the lead token on the result URL and Apply link refers only to that check.

Cloudflare keeps point-in-time backups of our database, which it calls Time Travel, for the last 30 days. A record we remove can stay in a backup for up to 30 days after we remove it. See Cloudflare’s Time Travel documentation.

Cookies and similar technologies

Our measurement code sets no cookies and uses no browser storage; after an internal hop, the page address carries the broad entry class and first landing path. It does read how you reached the site, from the referring site and any campaign tag in the address, to work out the broad class above, and it adds that context to the internal page link you follow when you interact with it, including Apply and check links. The Cloudflare Web Analytics script measures visits and page speed, and its documentation says it reads the browser’s Performance API. We use both only to count and understand how the site is used, and Cloudflare is the only other party that receives the results. To avoid being counted, block the Cloudflare script in your browser. The route finder keeps your answers in the page and sends them nowhere.

Your right to object

You can object at any time to our use of your information. Our click and check records hold nothing that identifies you, so we cannot pick out yours. To stop Cloudflare Web Analytics counting your visits, block its script in your browser. Write to privacy@selldata.uk with any question or objection, or phone us on the number below.

Your other rights

You can ask us for a copy of your information, to correct it, to delete it or to restrict how we use it, though our records will usually hold nothing we can link to you. Write to privacy@selldata.uk or phone us on the number below to use any of these rights. We answer within one month. The phone number is in North America, so from the UK dial +1 first.

Complaints

You can complain to us about how we handle your information by writing to privacy@selldata.uk or by phone. We will acknowledge a complaint within 30 days, look into it without undue delay and tell you the outcome. You can also complain to the Information Commission, the UK data protection regulator, which is also known as the ICO, at ico.org.uk/make-a-complaint.

Whether you have to give us this

No law or contract requires you to give us any of it. You can read every guide without using the check.

Next steps

Read about this site for how we check information, and our disclosure for how we are paid.

Contact: Ingenious Digital LLC, privacy@selldata.uk, (954) 834-3426

Sources

  1. Cloudflare: Web Analytics
  2. Cloudflare Web Analytics: About
  3. Cloudflare: Customer Data Processing Addendum (read 3 November 2026)
  4. Cloudflare D1: Time Travel (read 3 November 2026)