Policies, privacy and platform safety

1. 01
   Accounts
2. 02
   Ownership
3. 03
   Your Twin and your customers
4. 04
   Voice and likeness
5. 05
   Acceptable use
6. 06
   Adult content
7. 07
   Payments and subscriptions
8. 08
   Providers
9. 09
   Availability
10. 10
    Termination
11. 11
    Liability
12. 12
    Changes
13. 13
    Governing law

These Terms of Service ("Terms") govern your access to and use of lilidi.ai ("lilidi", "we", "us"), operated by LiliDi. By creating an account or using the service you agree to these Terms.

1. Accounts

You must be at least 18 years old and able to enter into a binding contract. If you use Lilidi for a company, you confirm that you may accept these Terms on its behalf. You're responsible for everything that happens under your account, including keeping your password safe. You can't resell or sublicense access.

2. Your content & ownership

You own the material you give your Twin - website pages, documents, FAQs, voice samples and images - and the records of its conversations. You give us a limited right to host and process this material only to run your Twin and the features you enable.

We don't train AI models shared across customers on your knowledge, conversations or voice. You are responsible for having the rights to everything you upload and for the accuracy of the knowledge you approve.

3. Your Twin and your customers

• Your Twin answers from the knowledge you approve. You set its boundaries and handoff rules, and you remain responsible for what your business offers and promises to customers.
• Your Twin introduces itself as an AI. Don't configure it to claim to be a person.
• AI answers can be wrong. Check important answers, and don't rely on a Twin for medical, legal, financial or emergency decisions without a qualified person.
• When your Twin joins a meeting or records a conversation, you are responsible for informing participants and obtaining any consent the law requires.
• For personal data your customers share with your Twin, you act as the controller and Lilidi as your processor, under the Data Processing Addendum.

4. Voice and likeness

You may clone only your own voice, or a voice you have written permission to use. The same applies to faces and avatars. We may ask for proof of consent, and we may remove a voice or avatar if consent is missing.

5. Acceptable use

You agree not to use Lilidi to:

• impersonate a real person or organization without permission, or mislead people about who or what they are talking to;
• collect payment card numbers, passwords or government ID numbers through a Twin;
• send spam or unsolicited bulk messages, including through WhatsApp or email;
• harass, threaten or discriminate against anyone, or incite violence, terrorism or self-harm;
• present regulated advice (medical, legal, financial) as if it came from a licensed professional;
• scrape, reverse engineer, or bypass rate limits or safety controls;
• break any law, including consumer protection, privacy and marketing rules.

Violations may result in content removal and account suspension or termination.

Platform rulePornographic and sexually explicit content is not allowed on Lilidi.

Adult and sexually explicit content

Lilidi does not permit users to upload, publish, distribute or intentionally request pornographic, sexually explicit or fetish content through the platform, or to configure a Twin to produce it.

This prohibition includes, without limitation:

• explicit nudity or visible sexual acts;
• pornographic or fetish-oriented imagery;
• sexually explicit depictions of real or fictional people;
• sexualised deepfakes or non-consensual intimate imagery;
• content intended primarily for sexual arousal;
• attempts to bypass safety filters, moderation systems or model-provider restrictions.

Any sexual content involving minors, or any content that sexualises a person who may be under 18, is strictly prohibited and may be reported to the appropriate authorities.

Lilidi may block a response, remove content, restrict features, suspend or terminate an account, and preserve relevant records where required for safety, fraud prevention, legal compliance or investigation.

Because Lilidi runs on third-party AI services, their usage restrictions also apply. A request permitted by one provider may still be blocked by Lilidi's platform-level safety rules.

6. Payments & subscriptions

Lilidi Twin Lite is free with 60 video minutes or 120 audio-only minutes each month, without a payment card. Paid Twin plans are monthly or annual subscriptions. Current prices and minutes are on the pricing page.

• Lite minutes reset each month from activation. Paid plans follow their billing period. Unused minutes don't roll over.
• Free Lite pauses live calls when its allowance runs out; it does not charge for extra minutes.
• Annual plans are billed in advance for the whole year.
• Prices may include or exclude taxes depending on your country; your invoice shows the tax applied.

Paid subscriptions renew automatically until cancelled. You can cancel at any time in one click from your billing page; your plan stays active until the end of the current period. Credits bought for the retired Lilidi Creative Studio remain subject to the terms in force when you bought them.

7. Third-party services

Lilidi uses third-party services to run your Twin: language models, voice, live video avatars, meeting attendance, messaging, email, calendar and payments. Content is sent to them only to deliver the feature you use. The current list is in the Data Processing Addendum. Channels such as WhatsApp, Zoom, Google Meet and Microsoft Teams have their own terms, and they can change or limit access independently of us.

8. Service availability

We aim for high uptime but don't guarantee uninterrupted service on self-serve plans. Enterprise customers can request SLA terms. Scheduled maintenance may interrupt service briefly.

9. Termination

You can delete your account at any time by emailing [email protected] from the email address you sign in with. We delete your Twin's knowledge, conversations and voice data within 30 days, except records we must keep by law, such as invoices. We can suspend or terminate accounts that violate these Terms or applicable law.

10. Disclaimers & liability

The service is provided "as is". To the maximum extent permitted by law, our total liability for any claim arising from these Terms is limited to the amount you paid us in the 12 months preceding the claim. We're not liable for indirect, consequential or punitive damages.

11. Changes to these Terms

We may update these Terms when we add features, adjust pricing mechanics, or comply with new laws. We'll notify active users by email at least 14 days before material changes take effect.

12. Governing law

These Terms are governed by the laws of the jurisdiction in which LiliDi is registered. Disputes will be resolved in the competent courts of that jurisdiction, unless mandatory consumer protection law in your country requires otherwise.

This Privacy Policy explains how Lilidi (lilidi.ai) accesses, uses, stores and shares personal data when you use our platform, including optional Gmail and Google Calendar integrations. Last updated: October 6, 2026.

What we collect

• Account data: email, display name, password hash, OAuth identifiers (Google/Apple/Microsoft).
• Profile data you provide: avatar, bio, social links, username.
• Twin data: the knowledge you import (website pages, documents, FAQs), Twin settings, voice samples and avatar choices.
• Conversation data: messages, transcripts and, where enabled, audio and video of your Twin's conversations, plus the leads, bookings and follow-ups they produce. What your customers share with your Twin is processed on your behalf under the DPA.
• Connected-service data: Google account identity, connection credentials and metadata, calendar information, and messages and meeting records used by the features you enable, as explained below.
• Billing data: handled by Stripe - we store your customer ID, subscription state, and invoice references. We never see or store full card numbers.
• Usage data: IP, device type, browser, page views, performance and error logs.
• Cookies: auth session, theme preference, referral attribution.

Why we collect it

• To run and secure your account (legal basis: contract).
• To run your Twin: answer your customers, book meetings, write follow-ups and keep your workspace history (contract).
• To provide the email, scheduling and Twin workflows you request or enable, using connected services only after you authorize access (contract; authorization for Google access).
• To process payments and prevent fraud (contract & legitimate interest).
• To send service emails - receipts, security alerts, plan changes (contract).
• To debug, monitor performance and fight abuse (legitimate interest).
• To send product news only if you opt in (consent).

Gmail and Google Calendar

Connecting a Google service is optional. You choose the Google account and approve the permissions on Google's consent screen. We do not receive your Google password. Gmail and Google Calendar can be connected and disconnected separately.

Google data we access and why

• Account identity: your Google account identifier, email address and basic profile information identify the account you connect and show its connection status.
• Gmail: we request permission to send email from your connected account. This integration does not read, search or scan your inbox or existing emails. We process the recipients, subject, message body and delivery information for messages you ask Lilidi to send, including follow-ups, materials and reminders in workflows you enable.
• Google Calendar: we access your calendar list, event details and availability to display upcoming meetings, find available times and manage requested bookings. Event details can include identifiers, titles, descriptions, start and end times, attendee names and email addresses, invitation responses, organizers, locations and meeting links. When you create a booking, we send meeting and attendee details to Google, which can issue invitations and create a Google Meet link. Requested cancellation can delete the corresponding Google event.

What we store

Our backend stores OAuth access and refresh tokens so the connection can continue to work without repeated sign-in, together with granted permissions, expiry and connection status. OAuth credential payloads are encrypted at rest, and communication with Google uses HTTPS. We also store the connected account's identifier and email address. Access to connection credentials is restricted to backend services.

Calendar lists and upcoming events are retrieved when needed. Bookings created in Lilidi and meetings assigned to your Twin can leave stored records containing event identifiers, titles, times, attendee details, meeting links and status. For email workflows, we store drafts and sent-message records, including recipients, subject, body, timestamps and delivery status. These records support your workspace history and the workflows you enable.

Processing, sharing and AI features

Google processes email and calendar actions through its APIs. Messages and meeting invitations are shared with the recipients and attendees you select or configure. Our hosting and database services process the information needed to operate these connections. Some enabled email workflows use Resend for delivery when they are sent through Lilidi's email service instead of your Gmail account, including meeting-summary emails you choose to send to yourself or to people you name.

If you assign your Twin to attend a meeting, we send the meeting link to Recall.ai to provide the meeting attendance service. That service can process meeting audio, transcripts and participant information. Requested AI summaries and follow-up drafts can use meeting transcripts or summaries, sender details and the instructions you provide; this content is processed by Google's Gemini API to generate those outputs. Connecting Gmail alone does not give these AI features access to your mailbox.

Limited Use of Google user data

Lilidi's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including their Limited Use requirements.

We use Google user data only to provide or improve the user-facing features you request or enable. We do not sell it, use it for advertising or credit decisions, or use it to create, train or improve AI or machine-learning models shared across users. Transfers are limited to delivering those features with your consent, security, legal obligations, or a business transfer with your prior explicit consent. These restrictions also apply to data derived from Google user data.

Human access to Google user data is limited to your explicit consent to access specific data, security purposes, legal requirements, or internal operations using aggregated and anonymized data. These limits apply to our personnel and service providers handling that data.

Retention, disconnecting and deleting Google data

We retain connection credentials to maintain the integration until you disconnect it in Lilidi or we process a request to delete them. Using Disconnect for Gmail or Google Calendar in Lilidi removes that connection's stored OAuth credentials and pending authorization records, preventing further Google API access through that connection. To revoke Lilidi's authorization at Google, you can also remove its access in your Google Account's third-party connections. Google may revoke access to both integrations when they share the same authorization.

Disconnecting does not automatically erase stored drafts, sent-message history, booking records or meeting outputs, delete emails or events already in Google, or cancel Twin attendance already scheduled using a saved meeting link. Cancel those assignments and enabled workflows separately if you no longer want them to run.

Workspace records are retained to provide your history and enabled features until you delete them where a deletion control is available, or request their removal or account deletion. To request a copy or deletion of stored Google-related data, email [email protected] from the email address you use for Lilidi and identify the connected account and records concerned. Do not send passwords or tokens. We respond within 30 days and explain any records that must be retained for legal obligations or security. Data already delivered to recipients or held in your Google account must be managed with the relevant recipient or Google.

Who we share it with

We don't sell your data. We share the minimum necessary with:

• AI and media providers - Google (Gemini language models), ElevenLabs (voice and voice cloning) and HeyGen LiveAvatar (live video avatar) - to run the conversations and features you use. Only the content needed for that request is sent.
• Messaging - WhatsApp (Meta), when you connect the WhatsApp channel.
• Infrastructure - Supabase (database, auth, storage), Cloudflare (CDN), Resend (transactional email), Stripe (billing).
• Connected-service and meeting providers - Google, Recall.ai and our backend hosting services, for the email, calendar and meeting workflows described above. The Google Limited Use restrictions apply to Google user data shared with providers.
• Authorities - only when legally compelled or to report illegal content (e.g. CSAM to NCMEC).

How long we keep it

• Account data: until you delete your account.
• Twin knowledge, conversations and voice samples: until you delete them, or 30 days after account deletion.
• Meeting transcripts and summaries: until you delete them or until the auto-delete period you choose in Twin settings. Deleting also requests deletion of the recording and transcript at Recall.ai. Leads, follow-ups and emails already sent are kept; backups are cleared within 90 days.
• Billing records: 7 years (legal accounting requirement).
• Logs: 30 days for debugging, 90 days for security.
• Google connection credentials and related workspace records: as described in Retention, disconnecting and deleting Google data above.

Your rights

Wherever you are, you can request a copy of your data, correct it, or delete it. EU/UK users have full GDPR rights (access, rectification, erasure, portability, restriction, objection). California residents have CCPA rights. Email [email protected] and we'll respond within 30 days.

International transfers

Some processors operate outside your country (typically the US). For EU/UK transfers we rely on Standard Contractual Clauses with our sub-processors.

Children

Lilidi accounts are for adults (18+). If you believe a child has registered, email us and we'll delete the account.

Security

We use TLS in transit and access controls to protect personal data. Google OAuth credential payloads are encrypted at rest and restricted to backend services, as described above. No system is invincible. If a personal data breach occurs, we notify affected users and the relevant authorities as required by applicable law.

Our refund rules are short and on your side.

Subscriptions

Cancel anytime in one click from your billing page. Your plan stays active until the end of the current billing period, and you keep the minutes already included. We don't offer pro-rated refunds for partial periods, except where required by law.

Minutes

Included minutes don't roll over and are not refunded at the end of a period. If a conversation fails because of an error on our side, such as a dropped session, write to [email protected] and we will review it and credit the minutes back where the failure was ours.

EU/UK 14-day right of withdrawal

If you're a consumer in the EU/UK, you have a statutory 14-day right of withdrawal after purchase. If you ask us to start the service within that period, you pay only for the minutes you have used; the rest is refunded on request - email [email protected].

Creative Studio credits

Credits bought for the retired Lilidi Creative Studio follow the refund terms in force when you bought them. Email [email protected] with any question.

Disputes & chargebacks

Please contact us before filing a chargeback - we resolve almost all billing issues within 24 hours. Chargebacks filed without prior contact may result in account suspension.

How to request a refund

Email [email protected] with your account email and the invoice number (visible on your billing page). Approved refunds are returned to your original payment method within 5-10 business days.

This Data Processing Addendum ("DPA") forms part of the agreement between LiliDi ("Processor") and the customer ("Controller") for business use of lilidi. It is designed to satisfy Article 28 GDPR.

1. Roles

For personal data submitted by Controller's end-users to lilidi (the "Customer Data"), Controller acts as data controller and LiliDi acts as processor. Each party complies with applicable data protection laws.

2. Subject matter & duration

Processing covers running the Controller's Twins - hosting approved knowledge, holding conversations with the Controller's customers, booking meetings, sending follow-ups and storing workspace records - for the duration of the subscription, plus a 30-day deletion window thereafter.

3. Categories of data & data subjects

• Data subjects: Controller's authorized users, and the customers and meeting participants who talk to the Controller's Twins.
• Categories: account identifiers, approved knowledge content, conversation messages, transcripts and recordings, contact and lead details shared in conversations, voice samples, usage logs, and email, calendar and meeting information processed for enabled connected-service features.

4. Sub-processors

Controller authorizes the use of the following sub-processors:

• Supabase (database, auth, storage)
• Cloudflare (CDN, edge security)
• Stripe (payments)
• Resend (transactional email)
• Google (connected Gmail and Calendar services)
• Recall.ai (meeting attendance and transcription for enabled meeting features)
• Google Gemini (language models for conversations, meeting summaries and follow-up drafts)
• ElevenLabs (voice, speech recognition and voice cloning)
• HeyGen LiveAvatar (live video avatar streaming)
• Meta (WhatsApp channel, when connected)

We notify Controller at least 30 days before adding or replacing a sub-processor. Controller may object on reasonable data-protection grounds.

5. Security measures

• TLS 1.2+ in transit, AES-256 at rest.
• Row-level security on every database table.
• Least-privilege IAM, audit logging on production access.
• SSO + MFA for staff, hardware-key MFA for production.
• Continuous dependency scanning.

6. International transfers

Where Customer Data is transferred outside the EEA/UK, transfers rely on the EU Standard Contractual Clauses (Module Two) and the UK International Data Transfer Addendum, executed with each sub-processor.

7. Data subject requests

We assist Controller in responding to data subject access, rectification and erasure requests within 5 business days of receipt.

8. Breach notification

We notify Controller without undue delay and in any event within 48 hours of becoming aware of a personal data breach affecting Customer Data.

9. Deletion or return

On termination, Customer Data is deleted from production systems within 30 days and from backups within 90 days, unless retention is required by law.