Privacy policy

This page explains what DataScoop collects about you and why. It is written to be read, not skimmed past.

What we collect

Your email address, when you request an API key, so we can issue and manage the key. Payment details are collected and stored by Stripe, our payment processor; we never see your card number. Stripe shares with us the email and the amount paid so we can deliver what you bought. Server logs (IP address, requested URL, time) are kept briefly for security and reliability.

When you start checkout, we retain the originating DataScoop page and its area where available, your selected dataset and filters, and any short campaign labels with the checkout and purchase record. This helps us understand which pages lead to useful purchases. Page and area context stays in DataScoop's database; Stripe receives an opaque checkout reference. We do not retain an external referrer URL or add browser tracking storage for this context.

Optional signup purpose. When you create an account, you can choose spreadsheet downloads, API use, connecting an AI assistant, or just exploring. You can leave the answer blank. We save a chosen answer on your account and with relevant checkout and purchase records. We use it to show useful next steps and group service-use counts. Authenticated API and MCP activity can use the answer already saved on your account; we do not infer an answer from the client you use or fill in past activity.

The account interface uses a strictly necessary, HttpOnly session cookie containing an opaque random token. The server stores only its hash, linked to your account, and expires it after 30 days. The cookie authenticates your account; we do not send it to Google Analytics or store it in service counters.

Optional download feedback

After a paid CSV download, you can choose to tell us what you need the list for. We save your chosen category and the time you answered with the purchase record to help us improve our lists. We do not ask for free text or another email address, add browser tracking, or send your answer to Google. You can skip the question and still download your file. The answer stays with the purchase record unless you ask us to delete it.

Service counters

We keep daily grouped counts of account creation, API and MCP results, displayed explorer previews, offers supplied or visible, checkout attempts and outcomes, and requested, completed or failed sample and included downloads. Groups use the dataset, website or API/MCP channel, part of the service, product, outcome and optional declared purpose. Existing explorer counts also use market, guide and entry type. Result sizes are grouped as no matches, 1-25 rows or more than 25 rows. An unanswered purpose stays unknown.

These counters add no cookies or visitor identifiers. Counter records contain no email addresses, API keys, account or session IDs, payment identifiers, IP addresses, request headers or filter values. They are processed by DataScoop and are not sent to Google. The account cookie is used for authentication; it is not a new tracking identifier for these totals. Repeated actions can count more than once, and API or agent activity can be automated. Counts do not identify unique people or connect their actions into a browsing history. A completed download means the server finished sending the file; it does not confirm that someone saved or used it.

Optional analytics

If you choose Accept analytics, public marketing pages load Google Analytics 4 and send page visits and non-personal events such as problem-page and dataset-link clicks. Those events may include the dataset, market and problem page involved, but not filter values, payment details, API keys or checkout identifiers. Query strings are removed from page locations, referrers and link URLs before they are sent. Advertising storage, signals and personalisation are disabled.

Google is the analytics recipient and processor. Its systems and subprocessors may process analytics data outside the UK under its transfer safeguards; see Google's privacy policy. User-level event retention is controlled in DataScoop's Google Analytics property rather than by this website code.

Google Analytics is not loaded on the explorer, signup, login, account or export-delivery pages because those pages accept or display credentials or payment capabilities. Purchases, refunds and subscriptions are measured through server-side Stripe verification and signed webhooks instead. If you reject analytics, the Google Analytics script is not loaded and queued public-page events are discarded.

We store your accept or reject choice in your browser so we can respect it. Use the Analytics settings button on a public page to change that choice. Withdrawing consent stops future analytics loading and removes DataScoop's Google Analytics cookies from this browser.

Why we collect it

To provide the service you asked for (issuing keys, delivering downloads, running subscriptions), to prevent abuse, and to comply with tax and accounting law. Our legal bases for those activities are contract and legitimate interests. We use consent for optional analytics.

Public records in our datasets

The datasets on this site contain official public records about businesses, premises and permits. Fields marked personal in our dataset definitions, such as registered-manager names, are excluded from public downloads, API responses and pages. Published business phone numbers may be included. Business names and addresses can identify sole traders or home-based businesses; we cannot reliably distinguish these from other business records. Each dataset's field list shows what is included.

Your rights

You can ask us what we hold about you, ask us to correct or delete it, or object to processing, by emailing hello@datascoop.io. You can also complain to your data protection authority (in the UK, the ICO).

Retention

Account emails are kept while your key or subscription is active and for as long as tax law requires afterwards. Logs are kept for a short period and then deleted. Analytics retention is controlled in the DataScoop Google Analytics property; rejecting or later withdrawing consent stops future analytics collection from this browser.

Last updated 2026-10-21.