# How to handle questions about data security and privacy
> Learn how to answer GDPR and security questions on LinkedIn without stalling your deal. Move technical discussions to email with a professional process.
- HTML: https://getkinlead.com/respond-to-prospect-asking-about-security
- Markdown: https://getkinlead.com/respond-to-prospect-asking-about-security.md

**Short answer:** Don't explain your technical stack in a LinkedIn chat. Give a brief, confident confirmation that you meet industry standards and move the detailed conversation to email where you can share formal documentation.

## Recognize the signal

Not every privacy question is the same. Some are polite ways to end a chat, while others show the prospect is actually trying to buy. If you can tell the difference, you can prioritize your time.

A generic question about whether your tool is legal is often a brush-off. But when a prospect asks about specific certifications or data residency, they're usually checking if you can pass their internal procurement or legal review.

This is a strong buying signal. It means they like the product and are now looking for reasons why their company cannot buy it. They are doing the work of pre-selling your tool inside their organization.

Pay attention to who is asking. If a junior person asks a vague question, they might just be curious. If a manager or director asks about SOC2 or GDPR, they are likely involved in the purchase decision.

Timing matters too. If the question comes early in the conversation, before they have seen value, it might be a genuine concern. If it comes after a demo or a pricing discussion, it's almost always a buying signal.

If you get a brush-off question, don't argue. A simple 'happy to share our security overview if it helps' is enough. If they are not interested, they will ignore it. If they are, they will ask for the document.

**The brush-off**

- Is this even legal?
- Do you follow privacy laws?
- I'm worried about data.

**The buying signal**

- Where is your data hosted?
- Do you have a SOC2 report I can review?
- How do you handle GDPR data processing agreements?

## The first response

Your first response should project confidence. Don't get bogged down in a technical debate inside a LinkedIn message. Long paragraphs of jargon look defensive and are hard to read on mobile.

Keep it short. Confirm you meet the standards and offer a formal document. This moves the conversation from a casual chat to a professional business exchange.

Offering a whitepaper or PDF gives you a natural reason to ask for their professional email, which helps move the lead further down your funnel.

Avoid saying 'we are fully compliant' if you are not. If you are still working on a certification, say so and explain your timeline. Prospects respect honesty more than a vague claim.

Don't send attachments in LinkedIn messages. The platform may block them, and it looks unprofessional. Save the file sharing for email.

Match their tone. If they write a short message, reply with a short message. If they write a detailed question, you can write a slightly longer reply, but still keep it under four sentences.

- **them:** This looks interesting, but how do you handle GDPR compliance? We're pretty strict about it here.
- **you:** We take security seriously and are fully compliant with GDPR. I have a detailed security whitepaper that covers our data encryption and residency policies. Should I send that over to your email?
- **them:** Yes please, send it to sarah.jones@acme-corp.com

## Moving the conversation to email

Once you have the email, stop talking about security on LinkedIn. The inbox is for relationship building and scheduling, not for auditing your server architecture.

Email lets you attach official documents and loop in the right people. If it's a high-value account, bring in your technical team early so the prospect feels supported.

If they hesitate to give an email, offer to send a calendar invite for a short call instead. Some prospects prefer to talk through their concerns before sharing documents.

Keep the LinkedIn thread open for quick follow-ups, but move the detailed answers to email.

If they ask for a call instead of email, take the call. Some people need to hear a voice before they trust a document. Use the call to get their email and send the document right after.

Use a scheduling link to make the call easy. Something like 'here is my calendar if you want to talk through the details' works better than asking them to suggest times.

1. **Request the professional email.** Ask for the address where they prefer to receive formal documentation.
2. **Send the documentation immediately.** Email the PDF or security whitepaper within an hour of the request to keep the momentum.
3. **Loop in technical leadership.** CC your technical founder or security lead if the account is a high priority.
4. **Schedule a follow-up.** Set a brief call to answer specific questions their legal or IT team has after reviewing the document.

## What to include in your security doc

You don't need a 50-page manual. A professional document that answers common IT questions is enough. A simple PDF titled Security Overview usually works for the first stage.

Write it in plain language but include the technical terms a security officer expects. Focus on how you protect the data and how you handle it when a customer leaves.

Include a contact name and email for follow-up questions. This makes the document feel owned by a real person, not a generic legal template.

Update the document every quarter. Certifications expire and hosting providers change.

Include a sample data processing agreement (DPA) if you have one. Many European prospects will ask for it, and having it ready speeds up their legal review.

| | Topic | What to explain |
| --- | --- | --- |
| Data encryption | Explain how data is encrypted at rest and in transit. |
| Access control | Describe who in your company has access to customer data and how that access is managed. |
| Compliance | List certifications like GDPR, SOC2, or HIPAA that your organization maintains. |
| Data deletion | Explain the process for how a customer can request their data be deleted from your systems. |
| Incident response | Explain how you detect and respond to a data breach, and how you notify customers. |

## Handling the call with their legal or IT team

If the prospect wants a call with their legal or IT team, prepare a short agenda. Ask them to send questions in advance so you can bring the right answers.

On the call, don't try to be the expert on everything. Bring your technical lead or security officer. Your job is to facilitate and keep the conversation moving toward next steps.

Record the call if everyone agrees, or take notes. Send a summary email after the call with links to the documents you discussed.

If you don't know an answer, say you will follow up within 24 hours. Then do it.

Follow up within 24 hours even if you don't have all the answers. Send what you have and a clear date for the rest. Silence makes prospects nervous.

Keep the call to 30 minutes. Legal and IT teams are busy. A focused call with clear next steps is better than a long one that covers everything.

> Never guess about a certification or a security practice. A wrong answer in a legal call can kill the deal and damage your reputation.

```
Subject: Security questions from our call

Hi [Name],

Thanks for the call today. Here are the documents we discussed:

- Security overview (attached)
- Data processing agreement (attached)
- Our hosting provider's compliance page: [link]

I'll follow up on [specific question] by [date].

Best,
[Your name]
```

## Doing this with Kinlead

If you use Kinlead for outbound, you can answer questions about how your LinkedIn outreach is handled. Kinlead connects to LinkedIn through Unipile, a third-party provider, so it never stores your LinkedIn password.

Outreach sends at a human pace with a maximum of one action every 5 minutes, staying within the daily limits you set. You can review and edit queued messages on the Actions page before they send.

You can read more about [LinkedIn account safety](/features/linkedin-account-safety).

## Common mistakes that stall the deal

Even with a good process, small mistakes can slow things down.

- Trying to answer every technical question yourself instead of bringing in an expert.
- Sending a generic PDF that doesn't address the specific certification they asked about.
- Forgetting to follow up after the call, so the prospect has to chase you.
- Promising a certification you don't have, which will come out during their legal review.

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [LinkedIn account safety](https://getkinlead.com/features/linkedin-account-safety.md)
- [How to transition from networking to a sales call](https://getkinlead.com/how-to-transition-from-networking-to-sales-call.md)

## Common questions

**Should I send my full security audit to every prospect?**

No. Send a high-level security whitepaper first. Only share full audits or SOC2 reports after a non-disclosure agreement is signed.

**What if I don't have a formal security whitepaper yet?**

Create a simple one-page PDF that lists your data hosting provider and basic encryption methods. It's better to have a clean document than to answer questions in a chat.

**How do I handle a prospect who insists on a security call before a demo?**

Agree to the call but keep it short. Bring your technical lead and use the call to find exactly what their legal team needs to see in your documentation.

**What if the prospect asks for a certification we don't have?**

Be honest about your timeline. Explain what you are working toward and offer alternative evidence, like a penetration test summary or a detailed security overview.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
