Privacy Policy
Last updated 28 July 2026
This policy explains what personal data iLeaf Solutions collects through this website, why we collect it, who it is shared with, and what you can ask us to do about it.
Who we are
iLeaf Solutions Pvt. Ltd. (“iLeaf”, “we”) is a software and AI engineering company registered in India, with its headquarters at Phase-II, Carnival Infopark, Kochi 682042, Kerala, and offices in Austin, Texas and Stockton-on-Tees, United Kingdom.
For questions about this policy or about your personal data, contact [email protected]. That address reaches the person responsible for this policy.
We have not appointed a Data Protection Officer, and we are not required to: Article 37 makes one mandatory for public authorities, for large-scale regular and systematic monitoring, and for large-scale processing of special-category data. This site does none of those. Enquiries about your data are handled by the address above rather than routed to a title that does not exist.
What we collect when you contact us
When you submit an enquiry form, we collect the information you enter — typically your name, work email, company, country, and a description of what you need. Where the form asks about engagement type, industry, intended outcome or budget range, those answers are collected too.
Alongside your submission we automatically record:
- the page you submitted from, and the page that referred you
- your browser’s user-agent string
- an approximate country and city, read from the headers our content-delivery network attaches to your request — no separate lookup is performed and no third party is asked
- the date and time of submission
We collect this to route the enquiry to the right person, to prepare for the conversation, and to identify automated or fraudulent submissions.
Automated processing of enquiries
We want to be explicit about this, because it is not obvious. Enquiry submissions are processed by an internal AI agent that researches the organisation named in the enquiry using publicly available sources, summarises it, and emails a briefing to our sales team. The purpose is preparation, not decision-making.
No automated decision is made about you that has a legal or similarly significant effect. A person reads every enquiry and decides how to respond. If you would prefer your enquiry not be processed this way, email us directly instead of using the form and say so.
Analytics
We use website analytics, as most sites do, to understand how people find and use this site. It only runs if you accept analytics in the notice at the foot of the page — decline and none of it is loaded.
It records pages visited, how you interact with them, page performance and any errors your browser hits. Your IP address is not stored, and what you type is masked — including anything you say to Lia, which stays in the conversation. You can change your mind at any time; withdrawing consent stops it and clears what it held.
There is no advertising or retargeting of any kind on this site. The other record of your visit is the ordinary server log kept by our host, described below.
See the Cookie Policy for the single cookie this site sets.
Talking to Lia, and what she writes down
Lia is an assistant you can type to or speak to. If you speak to her, your microphone audio is streamed to a specialist model provider to be understood and answered; it is not used to train a model, and we do not keep the audio. What we do keep is the text of the conversation.
While you talk, she notes the things a colleague would need in order to be useful: your name, the company you work for, your role, an email or phone number if you give one, the country you are in, and what you said you are trying to build. She takes these only from what you actually say — nothing is inferred from your IP address, and a field she is unsure about is left empty rather than guessed at.
If a conversation shows real intent, that summary and the conversation it came from are sent to iLeaf’s own sales team by email, and to the enquiry-routing service listed below which looks up publicly available information about your organisation. The transcript goes with it because a colleague reading “we are drowning in contract reviews” in your words is better prepared than one reading a form. It is not sold, and it does not go to advertisers.
She can also fill in the requirement form for you as you talk. Nothing is sent from that form until you say so — she has to read it back and get your agreement first, or you press Send yourself. If you would rather she did not write something down, say so and she will not, and anything you type over yourself she is not permitted to change back.
Clearing the conversation in Lia deletes the stored session immediately. If you would like the summary and transcript removed after the fact, email us and we will delete them.
Who receives your data
We do not sell personal data and we do not share it for advertising. It reaches these companies only because they run part of this site or the services on it. Most of them are involved only if you take a specific action.
| Recipient | What reaches them | When |
|---|---|---|
| iLeaf.ai — the assistantRuns Lia, the assistant on this site: understanding what you type or say, and answering it. | What you type to Lia, and — if you start a voice call — your speech audio while the call is running. | Only if you open Lia and send a message or start a call. Browsing the site sends nothing. |
| iLeaf.ai — conversation memoryStores your conversation so Lia remembers it as you move between pages. | Your conversation turns with Lia, and any details you volunteer in them — for example a name or a company. | Only if you use Lia. |
| iLeaf.ai — enquiry routingPasses an enquiry to the colleague who will answer it. | The details you enter in an enquiry form — typically name, work email, company, phone, country and what you are asking about — with a summary of your Lia conversation where there is one. | Only if you submit an enquiry or ask Lia to put you in touch. |
| Zoho CRMKeeps the record of your enquiry so the person who follows up can see what you asked, and so we do not ask you the same questions twice. | The details you enter in an enquiry form — typically name, work email, company, phone, country and what you are asking about — together with the page you were on when you sent it. | Only if you submit an enquiry or ask Lia to put you in touch. |
| Email deliveryDelivers the notification email when you send us a requirement. | The contents of your submission, in the body of that email — including anything Lia wrote down for you and, where you talked to her first, the conversation that produced it. | Only if you send the requirement form. |
| Meeting schedulingRuns the scheduler behind “Book a call”. | Your name, email and the slot you choose. | Only if you book a meeting. |
| Product analyticsStandard website analytics — how people find and use this site. | Pages visited, how you interact with them, page performance and browser errors. Your IP address is not stored, and typed input is masked — including anything you say to Lia. | Only if you accept analytics in the cookie notice. Decline and the library is never loaded. |
| Website hostingServes this website to your browser. | Standard server request logs, which include your IP address, the pages you request and your browser's user-agent string. | Every visit. This is unavoidable for any hosted website. |
Some of these process data outside India and the EEA. Each is engaged under its own standard data-processing terms, which include the transfer clauses we rely on — that is what using these services entails, rather than a separate agreement negotiated per provider. If you need the specific terms for one of them for your own compliance review, ask and we will point you at the current version.
These are described by the job they do rather than by name. The services behind Lia are, in effect, how she is built, and building assistants like her is work clients come to us for — so we do not publish the list. If you are assessing us as a supplier, or you want it for your own records, ask and we will name every one of them.
Client project data
Data belonging to our clients and handled during delivery engagements is governed by the contract and any data-processing agreement with that client, not by this website policy. As a matter of standing practice, client data is never used to train public AI models, and where a client requires it we run the entire stack, models included, inside their own infrastructure.
Who we share data with
We do not sell personal data. We share it only with service providers that help us operate:
- iLeaf.ai — the assistant — Runs Lia, the assistant on this site: understanding what you type or say, and answering it.
- iLeaf.ai — conversation memory — Stores your conversation so Lia remembers it as you move between pages.
- iLeaf.ai — enquiry routing — Passes an enquiry to the colleague who will answer it.
- Zoho CRM — Keeps the record of your enquiry so the person who follows up can see what you asked, and so we do not ask you the same questions twice.
- Email delivery — Delivers the notification email when you send us a requirement.
- Meeting scheduling — Runs the scheduler behind “Book a call”.
- Product analytics — Standard website analytics — how people find and use this site.
- Website hosting — Serves this website to your browser.
We may also disclose data where legally required. That list is the complete one: it is generated from the same record the table above uses, and adding or removing a provider changes both in the same commit.
International transfers
We operate from India, the United States and the United Kingdom, so your data may be processed in any of those. Where data is transferred out of the UK or EEA we rely on the standard contractual clauses contained in each provider’s own terms — the European Commission’s SCCs, and the UK International Data Transfer Addendum where a transfer is out of the UK. We do not operate a separate transfer agreement of our own.
How long we keep it
Enquiries and the conversations attached to them are kept for 24 months from our last contact with you, then deleted. That is long enough for a project conversation to resume where it left off — which in this business is often a year or more — and short enough that we are not holding a stranger’s notes indefinitely.
The session cookie and the stored conversation behind it expire 24 hours after your last message, which is much shorter, because that record exists only so the assistant can keep its place.
Analytics data, where you have allowed it, is held by our analytics provider under their own retention schedule; withdrawing consent stops the recording and clears what your browser held. Where you ask us to delete your data and we have no legal reason to keep it, we delete it.
Your rights
Depending on where you live, you may have the right to access a copy of your personal data, correct it, delete it, restrict or object to how we use it, withdraw consent, and receive it in a portable format. To exercise any of these, email [email protected]. We will respond within the period required by the applicable law.
If you are in the UK you may complain to the Information Commissioner’s Office; in the EEA, to your local supervisory authority; in India, under the Digital Personal Data Protection Act, by writing to the address at the top of this policy marked for the attention of the Grievance Officer, or to [email protected] with “Grievance” in the subject line. We will acknowledge within the period the Act requires.
Legal basis
Where UK or EU data-protection law applies, we rely on legitimate interests to respond to business enquiries and to protect the site from abuse, consent where we ask for it explicitly, and legal obligation where we must retain records.
Security
Enquiry submissions are transmitted over HTTPS and forwarded to our internal systems from the server, so the credentials involved are never exposed in your browser. Access to enquiry data is limited to the people who need it. No transmission over the internet can be guaranteed completely secure, and we do not claim otherwise.
Children
This site is aimed at businesses and is not directed at children. We do not knowingly collect personal data from anyone under 16.
Changes
If we change this policy we will update the date at the top. Material changes affecting how we use data already collected will be communicated directly where we have a way to reach you.
