Security

How we handle your data

Plain answers, not badge soup.

🔐 Encryption in transit

All traffic — website, dashboard, API and snippet — is encrypted with TLS. No exceptions.

💳 Payments never touch us

Billing runs entirely on Stripe's certified infrastructure (PCI DSS Level 1). We never see or store card numbers.

🗓️ Rolling data retention

Screened lead data is automatically deleted after 90 days by default. Agency plans set their own window in the dashboard — any number of days, down to zero, where lead details are cleared at the next nightly sweep.

🔑 Scoped API keys

Keys can be regenerated instantly from your dashboard; old keys die immediately. We alert you by email on every key change.

🕵️ Privacy-first fingerprinting

Device fingerprints are hashed in the visitor's browser before they reach us. No third-party tracking CDNs are loaded on your site.

📼 Fail-open architecture

If LeadShield is unreachable your forms submit normally. Our availability can never block your business.

🧯 Safe for your AI tools

Form fields are an open door into the AI assistants businesses now attach to their CRMs. On every plan, LeadShield flags known prompt-injection patterns (in several languages, including text hidden in invisible characters) and risky links, and on Pro and Agency your webhook carries a cleaned copy of each message for any AI step. It flags; it can't promise to stop every attempt, so keep a person in the loop wherever an AI tool can act on a lead.

📶 Live service status

UptimeRobot checks LeadShield's API around the clock and publishes the result, with its uptime history, on our public status page: stats.uptimerobot.com/fK5aATzZdh. If something is wrong, it shows there.

Who we rely on

These companies process data for LeadShield, each only for the job listed:

CompanyWhat forWhat it receives
HetznerThe server LeadShield runs onEverything LeadShield stores
HostingerOff-site backupsEncrypted copies only, which it can't open
CloudflareNetwork, DNS and bot checks on our own sign-up and contact formsTraffic to leadshield.ai
Google (Gemini API)AI analysis of lead content, on Pro, Agency and in your first 14 days, the Lead Brief, the free spam message checker, and the site's chat assistantThe lead's name, company, email, phone and message, for that one check, plus your Business Profile for a Brief; text pasted into the spam message checker; what you type into the chat
Google (Sign in with Google)Signing in, only if you choose itNothing from us. Google tells us your name and email address
AbuseIPDBIP reputationThe visitor's IP address only
BrevoAccount and service emailsYour email address and the email's contents
StripePaymentsBilling details; we never see card numbers
Google AnalyticsStatistics about visits to leadshield.aiOnly for visitors who accept cookies

What happened on 6 October 2026

On 6 October 2026 an automated attack used the sign-up form on leadshield.ai to create 257,087 fake accounts in 23 hours. Each sign-up sent a verification email, so our domain mailed those emails to addresses the attacker chose, with a link typed into the name field. In the same incident our public chat assistant was used as a free AI model, and one of our AI keys was used outside LeadShield.

What we changed:

We've left out anything that would help someone repeat it. Questions about it are welcome through the contact page.

Who's behind it

LeadShield.ai is built and operated by Autonoma, 66 Paul Street, London, EC2A 4NA. Card statements show AUTONOMA.

Security question or something to report? Contact us — security reports get same-day attention.

LeadShield AssistantTypically replies in seconds
×
Hi! Ask me anything about blocking fake leads, pricing, or setup.