Legal

Privacy

Leadgible builds lead-qualification funnels that other businesses embed on their own websites. That puts us in two different positions at once - we hold our customers' account data, and we handle the answers their visitors give them - and this page keeps the two apart, because the rules that govern them are different.

In effect from 2026-10-06. It is written to be checked: every factual claim below is held against the code or the specification that makes it true, by a test that runs before this page can be published.

Who is responsible for what

For the account you open with us - your name, your email address, your sign-in credentials, and your billing status - we decide what happens to it, so we are the controller and this policy governs it.

For the answers your funnels collect, you decide what is asked, who it is shared with and how long it is kept. You are the controller and we are your processor: we act on your instructions and we do not use your leads for our own purposes, sell them, or train anything on them.

What we hold

Your account. Your name, your email address, your sign-in credentials, the organisation and workspaces you belong to, and your plan and payment status.

The leads your funnels collect. Every answer a respondent gives, including free text written in their own words. A lead may carry a name, email, phone and company. We also record how the visit reached you: an IP address subject to the setting below, an approximate country, region, city and timezone, campaign parameters, the referring page, the landing page, the device and browser, and how long each step took.

What we work out from it. A score, the band it falls in, and the sentence explaining why.

Calls, once the voice agent ships. Call audio is discarded at session end; only the transcript is kept.

Where it is held

The primary database is in North America. Answers, extractions and transcripts are stored in object storage, not the database. If you or your respondents are in the United Kingdom or the European Economic Area, that means personal data is transferred to the United States. Standard Contractual Clauses cover the primary datastore, not only the sub-processor list. We say it that way round on purpose: it is a wider commitment than a list of vendors, and it is the one the location of our database actually requires.

IP addresses

An IP address is personal data, so it is a setting rather than an assumption. IP capture has three modes. You can capture it in full, capture it with the last part zeroed, or not capture it at all. The default is anonymised. Masking happens before the row is written, not on read. A funnel set to anonymise never holds a complete address to begin with.

If you report a form

Every funnel carries a link for reporting it to us. A report comes to us and not to the business whose form it was, and for it we are the controller. A report keeps the reason you chose, anything you wrote, and your IP address with its last part removed. We ask for no name and no email address, so we cannot reply to a report, and the page asks you not to put your own details in what you write. We keep a report as our own record of what was reported and what we did about it, and nothing deletes one on a schedule yet.

A bot-mitigation challenge runs on the page a form is reported from, and a report is not accepted without it. It is the challenge described under What we put on a device, and it is there so that reports come from people. A limit on how many reports one address may send is keyed by that IP address and lasts ten minutes.

What we put on a device

The embed stores a partial answer set in the respondent's browser so they can resume. It is not a cookie, it is not readable by any other site, it is never sent to us as an identifier, and clearing the browser's site data removes it.

The dashboard sets one first-party cookie so that you stay signed in. This site ships no JavaScript, so it cannot track anyone. There is no analytics script on it and no tag manager - which is checkable rather than promised, because the page you are reading contains no script tag at all. Nor does it load anything from a third party - its typeface included, which this site and the dashboard serve themselves - and its security policy lets a browser load from no other address.

A bot-mitigation challenge runs on the funnel pages we host. It is there to keep automated submissions out of your funnels. The challenge is invisible and runs in the background, and Cloudflare's Turnstile Privacy Addendum applies to it. Read it here - it is the only outbound link on this page, and it is here because Cloudflare requires it of an invisible challenge rather than because we chose to add one.

The challenge does not cover a funnel embedded on a customer's own website; rate limiting, an origin allowlist and a hidden field protect that instead. We would rather write that down than let the sentence above be read wider than it is true: a challenge is registered for the hostnames we own, and there is no wildcard that could cover every website a customer might paste the snippet on.

How long we keep it

Your plan sets how far back your leads are kept:

• Free - 30 days
• Starter - 6 months
• Pro - 2 years
• Scale - Unlimited
• Agency - Unlimited

Every completed lead is stamped at capture with the date its retention period ends.

Who else touches it

The companies we rely on to run the service - what each one is given, why, and whether it is in use today - are listed on our sub-processors page, with the date of every change. We email the Owner of every organisation at least 30 days before a new sub-processor is engaged.

AI, and what it is shown

A model reads the submissions your funnels collect: Cloudflare Workers AI, through Cloudflare's AI Gateway, once a submission is complete. Contact fields are stripped from model prompts unless opted in per field. And a funnel that uses AI analysis says so to the person filling it in. Any other model provider is reached only through a key you connect yourself.

The scoring itself is not an AI decision. Rules you write turn facts into a score, so the same answers always produce the same result, and the reason is shown rather than inferred.

Keys you store with us

If you connect your own provider, its key is encrypted before it is stored. Customer credentials are held under envelope encryption. A stored credential is never returned by any route. The interface shows you the last few characters and offers to replace it. There is no endpoint that will hand a stored key back, and one cannot be added without removing the check that forbids it.

Your rights

You can ask for a copy of what we hold about you, ask us to correct it, ask us to delete it, object to how we are using it, or complain to your data protection authority. Write to us at the address below and we will act on a verified request without undue delay.

Self-serve export and erasure are not built yet, so a request today is carried out by a person. If you are asking about answers you gave to someone else's funnel, see the note at the top of this page - they decide, and we will put you in touch.

How it is protected

Data belonging to one customer is separated from every other by the query layer itself rather than by a filter each page remembers to apply. Everything that leaves the system - an API response, a notification, an export, a delivery to your CRM - passes through one function that strips what must not leave, so a new feature cannot leak by forgetting.

If something goes wrong

If personal data we hold is exposed, we will tell the customers affected without undue delay, and in any event within 48 hours of becoming aware of it. The notice goes to your organisation's Owner. It says what we know and what we are doing, and more follows as we learn it, so that you can meet your own obligations to the people in your data.

Changes

This page is published from the same source as the product it describes, and it carries the date the current version took effect. When something material changes we will change this page and move that date.

Contact

Ariel Retes, trading as Leadgible
Davao City, Philippines
privacy@leadgible.com