Templates
Template: replying to how did you get my data
When someone asks how you got their details, answer plainly: name the real source, say what you hold, say why you wrote, and offer to delete it or stop. Do not dodge, and do not guess a source. Below are four replies by source, and a longer one that lists what GDPR Article 14 asks for. This is not legal advice.
Published by Sellinger AI. Numbers and settings checked on 24 October 2026 against the fact register. Report an error.
The text
Fair question, [first name]. I found your name and role on your public LinkedIn profile, and wrote because [one real reason tied to their role or a post]. All I hold is your name, job title and company. If you would like me to delete it, or to stop writing, tell me and I will do both today.
Good question, [first name]. Your name and work email are listed on [company website page], and I wrote because [reason]. I hold only that, and I do not share it. I am happy to remove it if you prefer.
Fair to ask, [first name]. Your work details came from [name of provider], a business contact database we use. I hold your name, role, company and work email. I can remove them now, and I have added you to our do not contact list so you are not contacted again.
Here is the full answer, [first name]. [Company name], [registered address], is responsible for your details. We hold your name, role, company and work email, which came from [source]. We used them to write to you about [purpose], on the basis of legitimate interest in B2B outreach. We share them with [recipients, such as our email provider], and keep them for [period]. You can object to this at any time, ask for a copy, or ask us to delete them: reply here or write to [privacy contact]. I will act on whichever you choose.
Why each line is there
| Line | Why it is there |
|---|---|
| Name the real source | A vague answer reads as hiding something, and the source is one of the things GDPR Article 14 says to tell people. |
| Say what you hold | A short list of fields shows there is little to fear and answers the real worry. |
| Give the reason you wrote | It shows the message was not random, and that you had a lawful reason to expect interest. |
| Offer deletion and stopping | Individuals have a right to object to direct marketing, and offering it first lowers the temperature. |
| Contact and period in the full notice | Article 14 also lists the controller, the purpose and legal basis, recipients and how long you keep data. |
What it measured
No data yet. Sellinger has not measured results for this exact text, so this page makes no claim about replies, meetings or revenue. Measured campaigns are in the case studies.
What the law asks: GDPR Article 14 sets out what to tell someone when you did not collect their data from them, including the source, and says to do it within a reasonable period and at the latest at the first communication with them if you are using the data to contact them. Article 14(5) lists exceptions. Recital 47 says direct marketing may be regarded as a legitimate interest, weighed against the person's reasonable expectations. Article 21 gives the person a right to object to direct marketing.
When not to use it
- When the message cites a data subject access request or a regulator. Pass it to a person and your adviser, with the deadline in the law.
- When you do not know the source. Find out first, then answer.
- When your data came from a source you cannot name or one you should not be using. Stop using it.
- When the person has already asked you to stop. Confirm the stop and do not add an explanation.
How to use it in Sellinger
When a contact replies with an opt out such as STOP or unsubscribe, in English, Bulgarian or German among other forms, the contact goes on the team's suppression list, the agent stops and the lead is closed out. A weak or unclear phrase never writes the permanent record: the agent stops and a person decides. For a request to delete data, see discarding a lead and data requests. Put the approved wording in a text article in a knowledge base collection and attach it to the persona, so the agent answers from it. If you would rather answer yourself, add a needs attention rule for this kind of reply, and the conversation is flagged for a person.
Common questions
Do I have to say where I got their details?
What if I used a database provider?
Should I delete their data if they ask?
Is a short reply enough?
Sources and method
Wording is ours. Law cited from GDPR Articles 14 and 21 and Recital 47 (gdpr-info.eu), read 25 October 2026. Not legal advice. Sellinger behaviour from the fact register.
Related: Templates hub, Reply to a complaint about outreach, GDPR legitimate interest, Suppression list, How did you get my data? How to answer.
