Where our data comes from

If your business email address is in Bookedt, you probably never gave it to us. You gave it to someone you were meeting, or it was found for us by a data provider. Either way you are entitled to know how it got here. This page covers business contact details in Bookedt, our meeting assistant.

The short version: we are not a lead database. You cannot search Bookedt for people. Every contact record exists because one of our customers had a meeting with that person, or because that person booked a meeting with them.

There are five ways, and no others:

• 1. The meeting itself. When a customer records or prepares for a meeting, we read the calendar invite — the title, and the names and email addresses of the people invited. This is the source for most of what we hold.
• 2. Someone booking a meeting. When a person books through a customer's bookedt.io link, they type their own name and email address into the form. That is the most direct source we have: the person handed it to us themselves, to get the meeting they asked for.
• 3. The customer's own CRM. If a customer connects HubSpot, Pipedrive or Close, we read the records they already have so a meeting can be matched to the right person and deal. That data is theirs; we are processing it on their behalf.
• 4. Contact enrichment, through FullEnrich. When a customer needs the business email address of someone who was on a call but not on the invite, we ask FullEnrich to look up that one named person. FullEnrich queries a series of business data providers in turn until one returns a match. We send them the person's name and their company or company domain.
  
  We use the same provider in the other direction for someone who books a meeting: we send the email address they typed in, and get back their job title and their company's industry and rough size, so the host knows who they are about to meet. We send the email address only — never the answers typed into the booking form. Either way we look a person up once, not repeatedly. We do not upload lists, and we only look up people our customer is actually meeting: someone who was on their call, or someone who booked time with them.
• 5. Working out the pattern. Once we have seen a few verified addresses at a company, we can work out the shape they use (first.last@, f.last@, and so on) and test a candidate address for a new person at that company. A guess is never stored or used unless the address verifies as real.

• We do not sell personal information, and we never have. There is no data product.
• We do not run a searchable database of people. Nobody can browse or export a list of contacts from Bookedt.
• We do not buy bulk lists and load them into the product.
• We do not look up phone numbers by default. Mobile lookup is off unless a workspace turns it on.
• We do not use your data to train AI models, and neither do our providers — see security for how that is enforced with each of them.

Bookedt does not scrape LinkedIn. It has no LinkedIn integration at all, and no part of it reads, stores or infers anything from a LinkedIn profile.

A business email address is verified before it is used — at the point a customer exports or syncs it, not months earlier. Addresses that fail verification are marked as unverified and are never synced to a CRM automatically. Where two sources disagree, the more recently updated one wins.

For business contact details we rely on legitimate interest — Article 6(1)(f) of the GDPR. The interest is straightforward: our customer met you, and needs to follow up with you in a professional capacity. We limit what we hold to business-relevant information — name, job title, employer, and work contact details — and we do not process special category data, or data about you as a private individual.

Legitimate interest is not a free pass. It is balanced against your rights, and your objection overrides it. If you tell us to stop, we stop.

If you were on a call that a Bookedt customer recorded, the transcript and summary belong to that customer, and they decide how long to keep them. We store and process them on their behalf. The recording itself we do not keep — the audio exists only long enough to produce the transcript, normally about a day, and is then deleted. Ask the customer directly if you want the transcript and summary gone — and tell us too, and we will pass the request on and remove what we can.

You can ask us what we hold about you, ask us to correct it, ask us to delete it, or object to us processing it at all. You do not need an account and you do not need to give a reason.

Use the opt-out form — it takes a moment and we action requests within one month, and usually much sooner. Or email support@bookedt.io. If you are in the EU/EEA or UK you may also complain to your local data protection authority.