Privacy

How we handle your data.

This policy applies to lygge.com, our Maya voice agent product, our off-plan assistant Sara and its demo, our business outreach, and any personal data we process on behalf of our customers. Last updated 21 October 2026.

1. About this policy

Lygge ("we", "us") builds Maya, a voice agent that answers phone calls for businesses. We act as a processor of the personal data of callers processed through Maya, and as a controller of the account and marketing data of our direct customers. The privacy notice for the Sara demo on lygge.com is section 9. The privacy notice for the business contacts we use to reach companies by email and on LinkedIn is section 10.

2. Personal data we collect

  • Caller data. When a caller speaks to Maya, we process audio recordings, transcripts, phone numbers, conversation metadata and any information the caller shares during the call. We act as a processor for this personal data. We process it on behalf of our customer, the business that deployed Maya, and on their instructions.
  • Customer data. When you sign up for Maya or request a demo, we collect your name, work email, phone number and company. We act as a controller for this personal data. Our payment processor handles billing data, and we do not store full card numbers.
  • Site analytics. With your consent, we collect anonymous usage data, including page views and session recordings, through Microsoft Clarity.
  • Marketing attribution.When you arrive from an ad, a search result or a referral, we collect the standard UTM parameters (source, medium, campaign, term and content), the click identifier from your platform of origin (Google, Meta, TikTok, Microsoft, X or LinkedIn), the referring page and the landing path. Until you submit the form, this data is held in your browser's storage. When you submit the form, it is sent with your demo request and stored against your record only. We do not share it with the originating ad platforms beyond what their pixel already collects on its own.
  • The off-plan demo (Sara). Section 9 describes the personal data we collect when you chat with or call Sara on our demo, including any notes our conversation platform stored before its memory feature was switched off, the contact form and the appointment you can book on it.
  • Business outreach. Section 10 describes the business contact details we use to contact real-estate companies, and what we record about our emails and their links.

3. How we use personal data

  • We process caller data to provide Maya to our customer, on their instructions.
  • We use call and chat transcripts and recordings to deliver the service, to follow up enquiries, and to fix and improve the service.
  • We use site analytics data to improve the user experience of the site.
  • We use marketing attribution data to measure which channels send the people we end up working with.
  • We describe the purposes for the Sara demo in section 9, and the purposes for business outreach in section 10.

4. Who receives personal data

Our service providers for AI language models, speech, email, business contact data, website delivery and analytics process personal data on our behalf. We provide the full list of our sub-processors on request. Section 9 and section 10 list the recipients of personal data for the Sara demo and for business outreach.

5. Where personal data is stored, and international transfers

  • We store conversations with our assistants, including chat transcripts, call transcripts and call recordings, on our conversation platform's server in Germany. Our operational database currently runs in Western Europe. We hold customer, enquiry and outreach records in a records database hosted in the United States.
  • We store copies of our database in Western Europe. Our conversation platform's daily backups are stored in the United Arab Emirates.
  • Our service providers for AI language models, speech, email, business contact data, website delivery and analytics may process personal data in other countries, including the United States.

6. How long we retain personal data

  • Call and chat transcripts and recordings.Our conversation platform applies no fixed retention period to them. We retain them for as long as they are needed for the purposes in section 3. We erase them when the business that deployed the assistant, or you, asks us to erase them. In that case, we delete each conversation and its recording on the platform. A copy of the conversation history, without audio, remains in the platform's daily backups for up to 35 days afterwards.
  • Conversation notes. The long-term memory feature of our conversation platform is switched off for the Sara demo. Notes stored before it was switched off may remain. We describe their retention in section 9.
  • Customer account data. After you delete your account, we retain customer account data in three stages.
    • Recovery period (day 0 to day 30). When you select "Delete account", we cancel your subscription and disable your assistant immediately, but we retain your personal data intact. If you sign up again with the same email within 30 days, we restore your account with its full history.
    • Tax retention (day 30 to year 7). We permanently erase operational data, such as phone numbers and IP addresses. We retain tax-relevant data, meaning your legal name, business name and the email used for invoicing, for the seven-year statutory period required by UAE, EU and UK business-tax law.
    • From year 7 onwards. We permanently erase all personal data. We retain only non-personal billing identifiers, such as Stripe customer IDs and the subscription event log, beyond this point.
  • Demo requests without a resulting account. We erase them after 24 months.
  • Site analytics. We aggregate site analytics data after 90 days, and we erase session recordings after 30 days.
  • Marketing attribution data. We retain it for the life of the demo request or customer record it is attached to. This means 24 months for demo requests that do not convert, and the life of the account plus 7 years for customers. We clear browser storage at the start of each new session for last-touch attribution. For first-touch attribution, it persists until you clear your cookies.
  • Backups.We keep backup copies so that we can recover from a fault. We cannot remove one person's personal data from a backup copy. A copy made before an erasure therefore still holds that personal data until we remove the copy itself. Our conversation platform's backups are removed after up to 35 days, and our database's restore history after up to 30 days. Our daily database copies have no end date yet. We have decided to limit them to 35 days, but that limit is not in place yet. If we restore a backup of the off-plan demo (section 9), we apply every erasure request made through the demo again before the demo is used again.

7. Your rights

Depending on where you are, you have the right to:

  • access a copy of the personal data we hold about you;
  • rectification of inaccurate or outdated personal data;
  • erasure of your personal data, subject to retention obligations;
  • restriction of processing, and objection to processing;
  • data portability, meaning a copy of your personal data in a portable format;
  • withdraw your consent to analytics; and
  • lodge a complaint with a supervisory authority, such as your national data protection authority.

To exercise any of these rights, write to hello@lygge.com, or use the form at lygge.com/demoand select "DPO / legal / compliance" as the subject. We aim to respond promptly. We do not require proof of identity beyond confirmation via the email address on file.

8. Security

We protect data in transit with TLS 1.3. We encrypt our database, our database backups and the conversation platform's backups at rest with AES-256. We keep audit logs of privileged actions. We store conversations as they take place, so a transcript or a recording contains whatever a caller or visitor chooses to say or type, including personal information. We retain transcripts and recordings, and they may be reviewed, as described in sections 6 and 9.

9. Privacy notice for our off-plan demo (Sara)

This section is the privacy notice for the demo at lygge.com/offplan-demo, where you can chat with or call Sara, our AI property assistant. It supplements sections 1 to 8.

Personal data we collect, and its sources

  • From you, we collect what you type or say to Sara. If you send the contact form, we also collect the form, and any appointment you book on it.
  • From your browser, we collect a random identifier that the chat stores in your browser, your browser type and your IP address. Our conversation platform links any notes it stored from your conversations, before its memory feature was switched off, to this identifier.
  • If you arrived through a link from our outreach, we also receive the code in that link. The code contains no name and no email address. It identifies the company we contacted and the business contact details we hold for it. Section 10 explains where those details come from.

Personal data we hold, and how long we retain it

  • Our conversation platform retains what you type, Sara's replies, and call recordings and call transcripts. It applies no fixed retention period. We retain them until you ask us to erase them.
  • The platform may write a summary of a chat or a call. It retains a summary for as long as the conversation.
  • Our conversation platform has a long-term memory feature, which is switched off for our demo agents. Before it was switched off, the platform stored notes from conversations, such as a visitor's name, preferences and open questions, linked to the random identifier that the browser keeps. Notes stored before the feature was switched off may remain on the platform. The agent does not use them. The platform applies no fixed retention period to these notes, and we retain them until you ask us to erase them.
  • The platform retains monitoring records of the requests sent to the AI model for 30 days, and its logs for up to 60 days.
  • We retain a record of the actions the service takes during a conversation, such as the search it runs, the filters it applies and the homes it shows. This record contains nothing you typed. We apply no fixed retention period, and we retain it until you ask us to erase it.
  • We retain the timings of a call and how it ended. This record contains no words. We apply no fixed retention period, and we retain it until you ask us to erase it.
  • We retain Sara's last reply and the temporary notes of the current conversation for 24 hours.
  • We retain the record of the homes, photos, plans and brochures you opened for 90 days, or until you ask us to erase it.
  • Separately from the platform's memory, we have our own feature that can recognise you on a later visit. To do this, your browser keeps a random identifier, and we store your first name and your last search on our servers, linked to that identifier. Our feature is currently switched off: we do not store or read this information. An erasure request deletes any such information stored before.
  • When you send the form or ask for a call-back, an automatic check reads the conversation to extract your answers. We retain the extracted answers and a hash, which is a non-reversible code, of the text the check read. This record does not contain the text itself. We retain it for 90 days, or until your enquiry is erased.
  • When you send the contact form, we retain your name, phone number and email address, your answers, a short summary and any appointment you book. An appointment is a meeting, a call or a viewing, with a date and a time in Dubai time. We also hold a copy of the enquiry email in our mailbox. We apply no fixed retention period, and we retain this data until you ask us to erase it. Our email service retains its copy for 30 days.
  • If you arrived through a link from our outreach, we record that the page was opened, that a chat was started or that a call was made. Each record carries a hashed form of your browser's random identifier and a hashed form of your IP address, which changes every day. We apply no fixed retention period. An erasure request deletes the records of your chats and calls. We retain the record that the link was opened, because it contains nothing that links it to your device.
  • When you make an erasure request, we retain a record of the request and of each action taken, which contains none of your words, for a year after the request closes. We retain your email address only while we still owe you an email about the request. We also retain an identifier of the erased enquiry, so that it is never sent again.
  • Our analytics provider collects site analytics data only if you accept analytics in the cookie banner, and never on a page opened from a link from our outreach. It retains this data for 30 days.
  • We retain backups of our conversation platform and of our own records as described in section 6.

Where we state no fixed retention period, we retain the personal data for as long as it helps us run the demo, follow up an enquiry, fix faults and improve Sara, and until you ask us to erase it.

How we use this personal data

  • We use it to run the demo and respond to you.
  • We use it to pass on your enquiry, with any appointment you booked, when you send the form or ask for it in a call. On this demo your enquiry comes to Lygge. No real agency or developer receives it.
  • We use it to fix faults and improve Sara. Authorized Lygge personnel may read conversations and listen to recordings on our conversation platform. For this review we copy nothing into other systems, and we retain only counts that quote nothing from any conversation.
  • If you arrived through a link from our outreach, we use records of your visit to understand how the companies we contacted use the demo. We hold these records internally. They show that the link was used, not what was said. We do not share your conversations with that company.
  • We use it to carry out an erasure request, and to email you about it.
  • We use IP addresses to protect the service from abuse, by limiting how many requests one IP address can make.

Who receives this personal data

  • Authorized Lygge personnel receive it, and access it behind a login.
  • Our service providers act as our sub-processors and process personal data on our behalf. They receive the following.
    • Our conversation platform and the server it runs on receive everything in the chat and the call.
    • Our AI model provider receives each message of the chat or call, to write Sara's reply.
    • Our speech providers receive the sound of a call, to convert it into text, and Sara's replies, to speak them.
    • Our website, database and backup provider receives your IP address and browser data, the records we hold that are described above, and the text of your conversation for the automatic check of an enquiry.
    • Our cloud backup storage provider receives the platform's daily backup.
    • Our records database provider receives your enquiry and, if you arrived through a link from our outreach, the company and the contact we hold.
    • Our email providers receive the enquiry emails, and the emails about an erasure request.
    • Our analytics provider receives data only with your consent.
  • We do not show one company's conversations or recordings to another company.

Erasure of your personal data

You can type or say "forget me" or "delete my data" in the chat or the call. You can also write to hello@lygge.com and tell us roughly when you chatted or called. We may ask you to confirm the request from the email address you gave us. We process a request as follows.

  • When you make a request in the chat or the call, we immediately erase the following.
    • Any first name and last search we stored on our servers, linked to your browser's random identifier, during earlier visits.
    • The records of your visits from a link from our outreach.
    • The search, page and timing records of this conversation and of your earlier conversations from this browser.
  • Once each conversation has closed, we automatically erase the following. We verify each erasure.
    • Your conversations from this browser that our conversation platform holds.
    • The enquiry you submitted through the form, including any appointment, and our records of it.
  • We also request the deletion of any notes that our conversation platform's long-term memory stored for your browser before it was switched off. If the request does not identify your browser, or the platform does not list your browser's identifier, our staff complete this deletion manually.
  • Certain records, including call recordings, call records and copies of enquiry emails held in our mailbox, are deleted manually by our staff. Any part of an erasure request that is not completed automatically within 7 days is escalated to our staff for manual completion.
  • If your enquiry gave us your email address, we email you when we receive your request, and again when it is complete, to tell you what we deleted, what we retain and why. If the request is not complete after 30 days, we close it and email you to say what was done, what was not, and how you can ask us to finish it.

Some personal data may remain after we complete an erasure request, as follows.

  • Copies held in our backups remain until they are removed (see section 6).
  • The record that a link from our outreach was opened remains.
  • The temporary notes of the conversation remain until our system clears them, at least 24 hours after the last message.
  • An erased enquiry remains in the deleted items of our records database for 7 days.
  • Emails in the deleted items of our mailbox remain until they are permanently removed after 30 days.
  • Our conversation platform's technical records remain for 30 days, and its logs for up to 60 days.
  • Our email service retains a copy of each email it sends for 30 days.
  • Our AI and hosting providers retain personal data under their own retention rules.

Your rights

The rights in section 7 apply. They are the rights of access, rectification, erasure, restriction, objection and data portability, and the right to lodge a complaint with a supervisory authority.

10. Privacy notice for our business outreach

We contact real-estate agencies and developers to offer our products. This section is the privacy notice for the business contact details we use for that, and for the people who receive our emails or our LinkedIn connection requests. It supplements sections 1 to 8.

Personal data we use, and its sources

  • About the company, we use its name, its website and the general email address it publishes, such as info@ or sales@. We obtain these from public lists of real-estate companies and from the company's own website. Hunter, a business contact-finding service, verifies for us that the address can receive email.
  • About people in senior roles at the company, such as the owner, the managing director or the head of sales, we use their name, job title and LinkedIn profile address. We obtain these from Hunter, which finds them by role. We keep only these three items of personal data about a person. We do not keep a person's own email address or phone number.

How we contact you

  • We write to the company's general email address from our founder's lygge.com mailbox, sent through Hunter. Hunter receives that address, the company's name and website, and the text of our emails, including the link to our demo. Each email explains how to opt out. You can reply "no", or use the unsubscribe link that Hunter adds.
  • Our founder may send a connection request on LinkedIn, manually, from his own account, to a person in one of those roles. We send nothing on LinkedIn automatically.

The links in our emails

  • Each email links to our demo. The link carries a code for the company we wrote to. The code contains no name and no email address.
  • When the link is opened, we record that it was opened, whether it was opened by a web browser or by an automatic program, such as a link preview, and a hashed form of the IP address, which changes every day. If a chat or a call starts from the link, we record that too (section 9). We record an email security scanner that opens the link in the same way.
  • We do not track whether you open our emails. The link to our demo goes straight to lygge.com, and Hunter does not track it. Only the unsubscribe link goes through Hunter. The images in our emails are the same for everyone and carry no code.
  • We never run site analytics on a page opened from these links. Our records show that a link was used, not what was said in the demo. We do not share what you say to the demo with your company.

Replies and opting out

  • We read every reply. Our system sorts replies using fixed word rules, not an AI model, to identify a "no", an opt-out or a complaint.
  • When you reply, we pause all our outreach to your company, by email and on LinkedIn, and cancel the emails scheduled to it, until we have read your reply.
  • When you reply "no", unsubscribe or complain, we add your company to our suppression list, and we stop all our outreach to that company, by email and on LinkedIn. If you ask us only to stop emailing, or if our email cannot be delivered, we stop our emails to that company.
  • Our suppression list holds the company's web address (or the address or profile that asked), the company's name, the reason and the date. We retain these entries with no end date, so that we do not contact the company again.
  • Replies remain in our mailbox and in Hunter. Our records database keeps a copy of each reply, how our system sorted it, and a draft answer for our founder. Our system never sends a reply.

How long we retain it

  • We apply no fixed retention period to business contact details. We retain them while we may contact the company, and until you ask us to erase them.
  • We retain the suppression list with no end date, so that a "no" is always respected.

Opting out and erasure

  • To opt out, reply "no", use the unsubscribe link, or write to hello@lygge.com.
  • To have your personal data erased, write to hello@lygge.com. We delete your name, job title and profile address from our records database and our working files, and cancel any email still scheduled to your company. We keep your company's web address on our suppression list, so that we do not contact it again.
  • Certain records, including your emails in our mailbox and, if you ask, your company's entry in our email sequences in Hunter, are deleted manually by our staff.
  • Some personal data may remain after we complete an erasure request. The deleted items of our records database remain for 7 days. The daily work lists that our system sends to our founder, the copies held by the services that deliver them, and the run records of our automation server also remain for a time.

Your rights

The rights in section 7 apply.

11. Changes to this policy

When we change this policy materially, we will update the date at the top and notify customers of record. Minor edits for clarity will not trigger a notification.

12. Contact and privacy requests

For privacy questions or requests, contact hello@lygge.com. You can request access to or erasure of your personal data by contacting hello@lygge.com. You can also use the formon our demo page and select "DPO / legal / compliance" as the subject.