Privacy Policy
Last updated: November 2026
Who we are
LeadShield.ai is built and operated by Autonoma, 66 Paul Street, London, EC2A 4NA ("we", "us"). Card statements show AUTONOMA.
What we process, and why
Account data (your name, company if you give one, email, hashed password): to operate your account, send service emails and provide support. Kept while your account exists. If you sign in with Google, Google tells us your name and email address and confirms the address is yours. We don't receive your Google password or anything else in your Google account.
Form Check (the free scanner at /tools/form-check): the web address you enter and what the scan found on that page, such as which form tools and spam protections it uses. We fetch that one page from our server, as a visitor's browser would, identified as LeadShield Form Check. The result is kept at a private link for 90 days, then deleted. If you scan a site and then create an account, we keep the site's name on your account so the dashboard can help you connect it.
Free checkers (the spam message, disposable email and fake lead checkers): what you paste is checked and not stored. The spam message checker sends it to Google's Gemini API for that one check.
Screened lead data (form values our customers submit for validation — typically email, name, company, phone, message — plus IP address, user agent and a browser-side hashed device fingerprint): processed in real time to produce a risk verdict, then retained on a rolling window of 90 days by default before automatic deletion, so customers can review their dashboard history. Retention is configurable, including immediate deletion after scoring.
Security screen and lead facts (every plan): links found in a lead's name, company or message, and whether its text contains instructions aimed at AI tools, are stored with the lead as flags. So is a short set of facts worked out without AI: the website from the email's domain, the lead's time zone (from the phone number or, for website leads, from our network provider's location header) and the best first channel. All of it follows the lead's retention. A watchlist you set up is account data.
Lead Brief and Business Profile (Pro, Agency and the first 14 days): for a valid lead with a message, the lead's name, company and message, with your Business Profile, are sent to Google's Gemini API (the same AI provider listed below) to produce a short brief and a reply draft. The brief is stored with the lead and deleted with it. Your Business Profile is account data. LeadShield never sends a reply on your behalf.
Hot-lead alerts (if you switch them on): a Hot lead's name, contact details and brief are sent to the Slack, Microsoft Teams or Discord channel you choose, and by email to you if you ask, at your direction.
Exit Rescue (only on sites whose owner switches it on): a reminder shown in the visitor's own browser when they go to leave a form they've started. It checks only whether the form's fields are filled in, never what they say, stores nothing on the visitor's device and sends us nothing. If the visitor then submits the form, the lead is screened as above and marked as sent after the reminder.
CRM contact data (only if you connect your CRM through the LeadShield.ai app): when a contact is added to a connected CRM account, we receive its name, email, phone, company, website and lead source, screen it like any other lead, and write a tag and a note back to that contact in your CRM. We store the access tokens for your CRM encrypted, use them only for those actions, and delete them when you disconnect or uninstall the app. Screened contacts follow the same retention as other lead data.
Lead report data (only if you create a report from the free audit): your email address, the agency and client names you type, the totals and reasons from that audit, and a cost per lead if you entered one. We use these to show the report, send you its link and, at most once, ask how it went. That note lets you join our newsletter, which only happens if you choose to. They are deleted after 90 days, though if you unsubscribe we keep your email address so that we don't write to you again. The uploaded list itself is checked in memory and never stored. Anyone with a report's link can open it. We count opens without recording who opened it, and to leave out your own we keep a one-way hash of your IP address, not the address itself.
Contact form messages (if you write to us through the contact page): your name, email address, subject and message, and the result of LeadShield's own check of it. We keep them so we can reply and follow up, and delete them after 12 months.
Billing data: handled entirely by Stripe. We store only Stripe's customer/subscription identifiers — never card details.
Backups: backups of our database are kept for up to 30 days. Copies stored away from our main server are encrypted with a key only we hold. Data deleted from LeadShield therefore also leaves our backups within 30 days.
Our role
For lead data screened on our customers' websites, forms and connected tools, Autonoma acts as a processor on the customer's behalf; the customer remains the controller of their visitors' data. For account and billing data, and for messages sent to us through the contact page, Autonoma is the controller.
Third parties we rely on
- Our hosting providers — the server LeadShield runs on, and a separate server that holds its encrypted backups
- Stripe — payment processing
- Google (Gemini API) — AI analysis of ambiguous lead content, the Lead Brief and of text pasted into the free spam message checker, processed transiently
- Google (Sign in with Google) — only if you choose to sign in with Google
- AbuseIPDB — IP reputation lookups (IP address only)
- Our email delivery provider — transactional and lifecycle email
- Google Analytics — website statistics, loaded only after cookie consent
Your rights
You can request access to, correction of, or deletion of your personal data, and unsubscribe from non-essential email via the link in any message. UK/EU visitors also have the right to complain to their supervisory authority (in the UK, the ICO).
Security
All traffic is TLS-encrypted, passwords are stored hashed, API keys can be rotated instantly, and lead data is purged automatically per the retention schedule. See Security for detail.
Contact
Privacy questions or requests: leadshield.ai/contact.