Skip to content
LeadLab Back to site
Legal

Privacy policy

This policy covers this website (aileadlab.ai) and the information you give us if you request a demo. It is written to be read, not to be survived.

Last updated: 21 September 2026.

The short version

When you request a demo, we save your details in our private owner portal so we can review and respond to your enquiry. Client portals also store account details, leads published to your organization, and progress updates or notes you submit. Authorized users in your organization and the LeadLab team can access that workspace information. Basic connection information is processed to serve the website. There are no advertising trackers. The public marketing pages and demo form do not set cookies. Signing in to a private LeadLab portal uses essential session and security cookies.

Who we are

LeadLab operates this website. Email info@aileadlab.ai. You can reach us through the demo request form.

What we collect when you request a demo

  • What you enter: your name, work email, company, a one-line description of what you sell, and which offering you are interested in. Team size, phone number and any message are optional, and we only have them if you provide them.
  • What comes with the request: your IP address is processed to apply a spam limit. We retain a keyed hash in a short-lived rate-limit record, rather than storing the raw address with your enquiry. The source is recorded as the website demo form; we do not store your full browser user-agent or full referring URL. Available referring-domain/campaign information may be attached to the enquiry, along with a link to its page view and broad device/browser categories.

Why we collect it

  • The form contents are used to reply to your enquiry and prepare for a conversation about whether LeadLab is a fit. Under GDPR this is processing necessary to take steps at your request prior to entering into a contract, and our legitimate interest in responding to business enquiries.
  • The rate-limit record helps prevent automated spam submissions and keep the service working. These records are removed by daily cleanup once they are more than one day old.

What we do not do

  • We do not sell or rent your information to anyone.
  • We do not add you to a newsletter or marketing list. Requesting a demo is not a subscription.
  • We use first-party website analytics hosted on our own server. It records public page views, referring domains, campaign tags, broad device/browser categories, and approximate city/region/country. It does not use analytics cookies or browser storage, and no visitor data is sent to an advertising network.
  • The public marketing pages do not set cookies. Our authenticated portals use essential cookies to keep you signed in and protect forms against misuse; they are not used for advertising. Your system light/dark preference is read from your operating system setting and is never recorded by us.

Where it is stored, and for how long

Submissions are stored in a database on a dedicated server we control, provided by our hosting provider Hostinger. We also send the submitted contact details and message through Google Workspace to our private team inbox to coordinate replies. Access is restricted to the people at LeadLab who respond to enquiries.

Routine HTTP access logging is disabled. The hosting provider and server may still process connection information and retain operational or security logs.

Demo request records in the LeadLab portal are automatically deleted after 24 months without an update to the record. Copies in our email accounts and shared inbox are retained separately for handling enquiries and business correspondence; they are not automatically removed by the portal cleanup. Local daily backups retain the latest 14 snapshots, so deleted records may remain in those backups until they rotate out. You can ask us to delete yours sooner and we will.

Who else sees it

Our hosting provider necessarily processes the data as part of running the server. Google processes inquiry notifications and email conversations as part of providing Google Workspace. When client billing is enabled, Stripe also processes the billing information described below. There is no third-party form service, no analytics provider, no advertising network, and no chat widget. Web fonts are served from our own server rather than a font host, specifically so that loading this page does not tell anyone else that you visited it.

Client billing

Monthly subscriptions and one-time payments use Stripe when connected. To prepare checkout, LeadLab sends Stripe the designated billing contact's email, the agreed plan name and amount, and internal identifiers that match the payment to your client workspace. For a one-time request, LeadLab sends the recipient email, payment title, amount, description and payment terms to Stripe; the recipient can use the private checkout link without a LeadLab account. Stripe collects payment details and billing addresses on its hosted pages. LeadLab does not collect or store your full card number or bank account details.

LeadLab stores your agreed plan, billing contact, processor identifiers, subscription status, and invoice amounts and links. The designated billing contact and LeadLab owners can view these billing records. Other users in the same client workspace do not receive billing access automatically. For one-time requests, LeadLab owners store the recipient name and email, payment amount, description and terms, checkout link, processor references and payment status. These requests are managed in the owner portal; anyone you share the private checkout link with can open it. Opening Stripe checkout or an invoice takes you to Stripe, which processes connection information and may use its own cookies.

Billing records remain stored after a plan is closed; they are not covered by the demo form's automatic deletion schedule. Contact your LeadLab team with billing or record-deletion questions.

Your rights

Depending on where you live, you may have the right to ask us for a copy of the information we hold about you, to correct it, to delete it, to restrict or object to how we use it, and to receive it in a portable form. If you are in the EU or UK you also have the right to complain to your data protection authority. If you are in California, you have the right to know what we collect and to ask us to delete it, and we do not sell personal information.

For a privacy request, use our demo request form and describe your request in the message field. You can also email info@aileadlab.ai.

Security

This site uses HTTPS. The web server runs as an unprivileged account with read-only access to the website files. A firewall restricts incoming connections to website traffic and SSH administration. Demo submissions are stored in our private database and shared with our authorized team through Google Workspace; both require authenticated access.

No system is perfectly secure and we will not claim otherwise. You can report a concern through our demo request form. You can also email info@aileadlab.ai.

Website analytics

We use traffic and demo-request attribution to understand which pages and campaigns are useful. Your connection address is used briefly for a local location lookup and to derive a keyed visitor estimate that changes each Pacific day. Raw IP addresses, full user-agent strings, full referrer URLs and unrelated URL parameters are not stored in analytics. Visible pages send a periodic activity update so we can estimate recent activity.

A short-lived keyed connection hash and counter also protect analytics collection against excessive requests, including from people who do not submit a form. These counters are removed by daily cleanup after one day. Detailed analytics records are removed after 90 days. If you submit a demo request, available source, campaign and approximate-location information from that page is attached to the request and follows its retention period. This does not reveal the names of people who have not submitted a form. Browser Do Not Track and Global Privacy Control signals disable this analytics collection. Blocking analytics does not prevent submitting the demo form.

Location estimates may be inaccurate, particularly with VPNs or mobile networks. IP Geolocation by DB-IP, using its locally stored Lite database.

About the LeadLab platform

This policy describes the website and client workspace information handled above, including account details, published leads, and progress updates. For questions about your service terms or the handling of business contact data on behalf of your organization, contact your LeadLab account manager.

Changes

If we change this policy we will update the date at the top. If a change materially affects information you have already given us, we will contact you about it rather than relying on you re-reading this page.

© 2026 LeadLab. All rights reserved. Privacy · Terms · Contact