Privacy
How we handle business contact data.
Last updated 18 October 2026
In short
- We hold the work details of people at companies (name, role, work email, work phone), taken from what companies publish themselves and from official business registers.
- We use them to build lists of likely buyers for companies that sell to businesses, and to contact businesses about LeadVault ourselves.
- We do not buy contact data from data brokers.
- To stop: reply “no thanks” to any email from us, or write to akseli@leadvault.eu. Your address goes on our suppression list, which our email system checks before every email it sends.
Who is responsible
The controller of the data described here is:
- Business
- Synlig Media, which runs LeadVault
- CVR
- DK 44784416
- Location
- Copenhagen, Denmark
- Contact
- akseli@leadvault.eu · +358 44 596 4003 (Akseli Mattila)
There is no separate data protection officer. Akseli Mattila answers these requests himself.
What we collect, and from where
About people, in their work role
- Name and job title
- Work email address
- Work phone number, where the company publishes one
- The company the person works for
- Where we found these details (the company website, often the exact page, or the register entry)
- A link to a public professional profile, in the few cases where we found one
About companies
Public company data: registered name and number, address, industry, size, founding year, filed annual accounts (such as revenue), the website and what it says the company does, and public notices such as registry changes and public contract awards.
Where it comes from
- Companies’ own websites: team, contact and about pages, and their press releases.
- Official business registers and public filings in each country, including annual accounts and the people a register lists for a company.
- Public notices, such as registry change feeds and public procurement awards.
We do not buy contact data from data brokers or contact-data aggregators.
Addresses we work out, and how we check them
Sometimes a company publishes a person’s name and role but not their email. We may then work out the likely address from the format the company uses (for example firstname.lastname@company.com). Our records note which addresses were worked out this way, and we only deliver one after the company’s mail server has accepted it.
To check whether an address can receive mail, we ask the company’s mail server. This does not send you an email.
Why we use it, and on what legal basis
- Lists for our customers. We build lists of companies likely to buy a customer’s product, with the people whose role makes them relevant. Our customers are companies that sell to other businesses.
- Our own outreach. We email businesses about LeadVault. These emails include a short free sample of a few companies, with the names and roles of people there, so the recipient can judge the quality of a list.
The legal basis is legitimate interest (Article 6(1)(f) of the GDPR): our interest, and our customers’ interest, in contacting businesses about products relevant to the work of the person contacted. We hold only work details in a business role, keep where each detail came from, and stop as soon as someone objects.
We make no automated decisions about people that have legal or similarly significant effects on them.
How long we keep it
We have not yet set a fixed period after which records are deleted automatically. This is what we do today:
- We keep a person’s work details while they are part of the company data we build lists from.
- If you ask us to delete your details, we delete your record from our database and keep only a suppression entry (below). Lists already delivered to customers are held by those customers.
- If you object or opt out, we keep only what we need to recognise you (your email address, and your name and company where needed) on a suppression list, so our email system does not contact you again. We keep that entry for as long as we operate, because deleting it would undo your opt-out.
- Database backups are kept for 7 days, so a deleted record is gone from the backups within about a week.
When we set a fixed retention period, it will be written here.
How to opt out or object
Either of these is enough:
- Reply “no thanks” to any email from us.
- Email akseli@leadvault.eu, for example with the subject “Opt out”.
Both reach the same mailbox. We add your address to our suppression list, which our email system checks before every email it sends. If you also want to be left out of the lists we build for customers, say so and we will delete your details from our database (see “Erase” below). You do not need to give a reason.
Your rights
If we hold details about you, you can ask us to:
- Access: tell you what we hold about you and where it came from.
- Rectify: correct details that are wrong or out of date.
- Erase: delete your details.
- Object: stop using your details. Because we use them for business outreach, an objection always stops it.
- Restrict: pause our use of your details while a question about them is sorted out.
Email akseli@leadvault.eu. We answer within one month, as the GDPR requires.
Complaints
You can complain to the Danish Data Protection Agency, Datatilsynet: datatilsynet.dk, dt@datatilsynet.dk. You can also complain to the data protection authority in the country where you live or work.
What this website collects
This website (leadvault.eu) has no forms, sets no cookies, runs no scripts and no analytics, and loads nothing from other sites, including fonts.
The site is hosted by GitHub (GitHub Pages). When you open a page, your browser sends GitHub the usual technical request, including your IP address, and GitHub keeps server logs of these requests. We do not receive or see those logs. See the GitHub General Privacy Statement.
If you email or call us, we keep your message and contact details to answer you and, if you order, to deliver your list.
Before 18 October 2026 this website had a request form and a demo search, and loaded fonts from Google. Details sent through the old form are kept so we can answer and handle those requests.
Changes to this page
When we change how we handle data, we update this page and the date at the top. This version replaces the one dated 14 April 2026.