Who runs this
Vetted Leads is run by LEKKIFY LIMITED, at vettedleads.app. That company decides what this product collects, how long it is kept and who it reaches, which in data protection language makes it the controller of that data.
Two routes reach us. If you are a business and you want out, the removal page writes the message and needs no account. For anything else, the contact page has a button for each address.
Two sets of data
About a business
The website address comes from Certificate Transparency logs, which are public, append only, and where a certificate has to appear before a browser will trust it. The rest is read off the site itself, the same way a browser reads it: what the business calls itself, what it does, what the site runs on, how to reach it, and what its pages carry. The default contact is a role address such as info@ or hello@, and at most three addresses are stored for one business.
Some of it is not copied from the site at all but worked out from it, including the country and the checks behind the gap list. The data sources page says which is which, field by field.
We hold it on a legitimate interest: reaching a business that has published a way to be reached, for work it might want. The data sources page gives the basis field by field and the two pages are meant to agree, so read that one as the detail behind this paragraph.
One caveat, stated rather than buried.
For a one person business the trading name can be a person's name and a linked profile can be a personal one. The database treats those as business data because that is what they are on the site they came from. If that is you and you would rather not be listed, removal covers all of it in the same request.
What we will not do
The things this product will not do are listed on the data sources page, beside the fields each one applies to, because that is where somebody checking us is already reading. They are not repeated here in different words, which is how two pages start disagreeing.
About you
You sign in with a Google account and there is no other way in. Google hands us the email address on that account, the name on it, the link to your Google profile picture, and a stable id we use to tell your account apart from anybody else's. Nothing asks Google for more than that basic profile, so nothing here can open your mailbox or your files. The picture is never fetched either: the circle on your account page is the first letter of your name, drawn by your own browser. Signing you in is what that account is for here. The email address is also where we send your receipts and the notices before a plan renews or ends, and a short daily email saying how many new businesses went live and where. If you leave a checkout unfinished, we send up to three reminders about it. The daily email is on until you press Unsubscribe in it or turn it off on your account page, and the reminders stop when you press Stop these reminders in one; the receipts and notices are about your account and payments, so they have no switch. The payment page is handed your email address too, so the provider's own receipt reaches you. None of it is used for advertising, none of it is sold, and it reaches nobody beyond the companies that help run this product, which are described below.
There is no password on this product. No field for one, no column holding one, and no reset to attack.
So nobody can try signing in over and over, we count sign in attempts from each network, and each use of a Google sign in, for about two days. We keep a scrambled code, never the network address or the sign in itself.
How long we keep it
A contact address carries the date it has to go, written on the day it is first found. Crawling the same site again does not push that date out. A job runs nightly, and on the date it deletes the address here and blanks it out of the copy in any account that had unlocked it. Our archive of older records loses the address the same way, the next time it is cleaned out.
What we hold, how long it stays, and what happens when the clock runs out
| What | How long | What happens then |
|---|---|---|
| A role address such as info@ or hello@ | How long24 months from the day it was found | What happens thenPurged here, and blanked out of any account that unlocked it |
| The address of a named person | How long12 months from the day it was found | What happens thenThe same deletion, and the same blanking |
| The business record: website, trade, country, town | How longNo clock | What happens thenA removal request takes it out of the feed, out of every export, out of any account that had unlocked it, and out of our archive the next time it is cleaned out. The website address is then kept on a do not collect list for good, which is what stops the next crawl finding the site again |
| Your account, if you signed in | How longUntil you delete it | What happens thenDelete it yourself from the account page, at any time. It goes at once, with what hangs off it: the contacts you unlocked, the balance, the saved searches, the drafts and the writer profile |
| When an account is deleted: its email, the name and id of its Google account, its billing country, when it was opened and deleted and how, its payments, and how many contacts it unlocked and drafts it wrote, and when | How long5 years from the deletion, then deleted | What happens thenKept to help prevent and investigate fraud, such as a stolen card used to pay us. It holds counts and dates, never the businesses you unlocked. Only we can read it, only to answer a court, the police or a payment provider looking into fraud, and we record every time we read it |
| A one-way fingerprint of the account you sign in with and of its email, and a random id this site keeps in your browser | How longThe fingerprints for good. The browser id's copy with us for 14 days | What happens thenUsed only so the free contacts are given once per person. A fingerprint is not your email or your account, only a way to recognise the same one coming back, and it stays after the account is deleted, which is what stops the free contacts being given twice. The browser id holds nothing about you and tells us only that one browser started several accounts |
The record that you unlocked a contact is kept after the address inside it has gone, because it is the proof you already paid for that one and must never be charged for it twice. Export exists so you can keep your own copy of a list past the clock.
Who else sees it
A few companies help run this product: the ones that host the site, run the server that finds new businesses and store the data, Google for sign in, the AI models that check websites and write drafts, the payment providers, one that tells us when something on the site breaks, and one that counts how the site is used. Each gets only what its part of the job needs. Some of them are in other countries, so what they handle can be processed outside the country you live in. The company behind the model that checks websites may use what that model is sent to improve its own products. It is only ever sent part of a business's website, with any email address or phone number taken out first, and never anything about you. Your browser also asks Google for the site's typefaces on every page load, so Google sees that request and the IP address it came from. Until you sign in, it also loads Google's sign in script, so Google can offer to sign you in with the account already open in that browser, and Google sees that request as well. Nothing about you is sold, and the site runs no advertising code. When something on the site breaks, a report of what failed and where goes to the service that tells us, without your IP address, your cookies or anything you typed. To see which pages and features get used, the site counts visits and records them with every word and every field hidden, and the pages that show your contacts, payments, account and drafts are never recorded. Once you sign in, your visits are tied to your account by a random id, never by your name or email address.
How your account is protected
Cookies
Four kinds of cookie, and no others. The sign in library's keep you signed in: a long session is split into numbered parts, and short lived ones are written while a sign in is in progress. One of ours, named vl_device, set when you press sign in: a random id with nothing about you in it, kept for a year, so the free contacts are given once per person rather than once per account. And one that Google's sign in script sets, named g_state, on any page where it loads, kept for six months: it notes when you last closed Google's offer to sign you in, so the offer waits before it comes back, and it holds a random id for your visit that the script can send back to Google. And one our usage analytics sets on every page, named ph_ followed by a key and _posthog, kept for a year: a random id for your browser, so the same visitor is counted once. We set no advertising cookie, and there is no cookie banner.
Your rights
You are a business and you want out
One email from an address at that website, with no account and no reason given. The address it arrives from is the whole check, which is why the request has to come from the business rather than from anybody who dislikes it. Every address we hold for you is deleted, the social links are emptied, the entry leaves the feed and every export, and the copy inside anybody's account is blanked. What is kept is the website address itself, on a do not collect list with no end date, because that list is the only thing that stops the next crawl finding the site again.
You want to know what is held about a business
The data sources page lists every field we collect with where it came from, and the list is the same for every business in the product. The town and the state are on it too. They come only from an address the business publishes in its own markup, which is why most rows carry neither.
Something about your business is wrong
The entry is a snapshot of one fetch, taken on the day we read the site, and nothing here is scheduled to read it again. So correcting your own site does not correct what is held here. Parts of the row were never copied from you in the first place: the country is our reading of details such as your web address and phone number, and the gap list and the score are ours. Two routes are open to you. Removal takes the whole entry out and holds through every future run, because the domain goes onto a do not collect list that the next crawl checks itself against. Both routes are a person acting on your email, and the difference between them is durability rather than effort. If you would rather the entry stayed and was corrected, ask through the contact page and one person edits the row by hand, which is the only way it can happen and which a later crawl of that domain can overwrite.
You are a customer and you want your own data gone
All three are a button you can press. The writer profile clears from the Remove button on the writer profile page, which the account page links to. A saved search deletes from the saved page. The whole account deletes from the account page, at once. Two things stay when it goes: the record of each payment, and the short record kept for 5 years for fraud cases, both listed under How long we keep it.
You want a copy of what is held about you, or you want to object
Ask through the contact page. For a copy, the removal page also has a button that writes the email for you. Nothing answers it on its own, so it is somebody doing it by hand.
Last updated 12 October 2026.