Waitlist data, plainly handled.
Last updated: 28 April 2026
This page covers the current TenderLead public site: waitlist details, lightweight analytics, and the pre-launch boundary between public procurement sources and firm-provided inputs. For the scoring-input boundary, see Source quality. For site-level cookies and analytics transparency, see Cookies. For the public-site accessibility target, see Accessibility. For site terms, see Terms.
What we collect
When you request access, we collect your email address and, if you provide them, your company name and sector. We use that information to manage onboarding, decide who fits the current Intelligence access path, and shape the service around the firms showing interest.
How we use it
Waitlist data is used to run TenderLead for your firm, not to train another firm's bidding workflow. We may use it to contact you about launch timing, onboarding, and fit. We do not sell waitlist data.
Analytics and browser behaviour
The public site uses Plausible Analytics and Ahrefs Web Analytics for aggregate page measurement. Plausible also receives a small number of TenderLead conversion events, such as waitlist joins, sign-in link requests, checkout-start clicks, and post-checkout activation submissions. Google Analytics 4 may also be loaded on public pages, using measurement ID G-B7ORM3QXBZ, but only after the visitor allows analytics in the consent prompt.
That analytics setup is intended to stay privacy-first: no authenticated app tracking via GA4, no advertising audience building, and no event payloads containing form contents such as email address or company name.
Public sources and firm inputs
TenderLead is designed to combine public procurement information with firm-provided context such as your website, sectors, keywords, and past wins when you choose to provide them. We keep that boundary explicit rather than pretending every score comes from public data alone.
Your rights
You can request deletion of your data at any time by emailing hello@tenderlead.co.uk.