Privacy Policy

Last updated: 4 May 2026 Effective date: [DATE OF PUBLICATION]

This Privacy Policy describes how Importify Limited ("Lilie", "we", "us", or "our") collects, uses, stores, and shares information when you use Lilie ("the Service") at lilie.app, the Lilie Chrome extension, or any related software or website.

Importify Limited is a Hong Kong company with registered office at: Unit 1603, 16th Floor, The L. Plaza, 367–375 Queen's Road Central, Sheung Wan, Hong Kong.

If you have any questions about this Policy or your data, contact us at support@lilie.app.

1. Summary (the short version)

Lilie helps you draft customer support replies. To do that, you choose to share email content with Lilie — via an Apps Script export you run yourself, a Google Takeout export, or by pasting or uploading content directly. Lilie uses what you share to learn how you write and what your product does. We never send email on your behalf without your explicit action, and we never sell your data.

The most important things to know:

• You stay the editor. Lilie drafts replies. You review and send them.
• You initiate every transfer. Lilie does not have direct API access to your Gmail. Email content reaches Lilie only when you upload it, paste it, or run an export script in your own Google account.
• We don't keep raw email content. We extract structured signals (writing style, knowledge base entries) and discard the original message bodies.
• You control your data. You can delete any data you've shared, or close your account, at any time.

The full Policy below explains everything in detail.

2. Who we are and what Lilie does

Lilie is an AI-assisted email drafting tool for customer support. Solo founders and small teams use Lilie to generate draft replies that match their product's facts and their writing style. Drafts are always human-reviewed before being sent.

This Policy applies to:

• The Lilie web application at lilie.app
• The Lilie Chrome extension for Gmail
• Any related Lilie software, website, or service

3. Data we collect

We collect the following categories of data:

3.1 Account data

When you create a Lilie account, we collect:

• Email address
• Name (from your Google account, if you sign in with Google Sign-In)
• A Sign-In session token (issued by our authentication provider, used to keep you signed in)

We use Google Sign-In with basic profile scopes only (openid, userinfo.email, userinfo.profile). Lilie does not request or store any Gmail-access scopes for your account.

3.2 Gmail content (when you choose to upload it)

Lilie does not have direct API access to your Gmail. Instead, you can choose to share Gmail content with Lilie by:

• Apps Script export. Run a Google Apps Script in your own Google account that exports filtered emails to a JSON file in your Drive, then upload that file to Lilie.
• Google Takeout. Use Google's official Takeout tool to export your Gmail to an .mbox file, then upload that file to Lilie.
• Manual paste or upload. Copy and paste email content directly into Lilie, or upload exported .mbox or .json files.

In every case, the data transfer is initiated by you. Lilie does not poll your Gmail and does not fetch new messages on its own.

3.3 Optional: client-side label lookup

When configuring an Apps Script import, users can optionally click "Pick from your labels" to autocomplete from their Gmail labels. This uses Google's client-side OAuth and the gmail.labels scope, which provides only the names of labels — not message content, metadata, or any other email data. The browser communicates directly with Google's servers; Lilie's backend never sees the access token or label data. The token is cached in the browser's local storage and expires after about an hour. This feature is optional — users can type label names manually instead.

3.4 Knowledge base content

You may upload, paste, or import content into Lilie's knowledge base — including help center articles, product documentation, past Gmail support threads, or other writing samples. We process this content to enable Lilie to ground draft replies in your product's facts.

3.5 Usage data

When you use Lilie, we automatically collect:

• Pages or features you access within Lilie
• Actions you take (e.g. drafts generated, agents created)
• Device and browser information (IP address, user agent, screen size)
• Error logs and crash reports

3.6 Cookies, local storage, and similar technologies

Cookies set by Lilie: None. Lilie does not set any cookies on lilie.app. Authentication uses bearer tokens (not cookie-based sessions), and our application servers do not issue Set-Cookie headers.

Third-party cookies: When you sign in with Google, Google sets cookies on accounts.google.com as part of its sign-in flow. Those cookies are set on Google's domain and are governed by Google's Privacy Policy, not ours.

Local storage: Lilie uses your browser's local storage (localStorage on the website, chrome.storage.local in the Chrome extension) to store the following on your device. None of this is transmitted to third parties:

• Your authentication session (Supabase access token and refresh token)
• Onboarding progress
• Cached copies of your voice profiles, agents, and knowledge bases (for faster page loads)
• Theme preference (light/dark)
• Dismissal flags for in-app nudges and the setup checklist

You can clear this data at any time from your browser settings, and it is automatically cleared when you sign out or uninstall the extension.

Analytics: Lilie includes the PostHog analytics SDK in our application bundle. As of the date this Policy was last updated, PostHog is disabled in production — no analytics events are sent and no analytics-related cookies or storage entries are created. If we enable PostHog in the future, this Policy will be updated and the configuration will use explicit-event capture only (no automatic page views, no session recording, no behavioral autocapture).

Error tracking and other telemetry: None. Lilie does not currently use Sentry, Datadog, Bugsnag, Rollbar, Mixpanel, Amplitude, Segment, Hotjar, FullStory, LogRocket, Heap, Matomo, Google Analytics, Google Tag Manager, or any similar third-party SDK.

4. How we use your data

We use the data we collect for the following purposes:

We do not use your data to train any machine learning model that is shared between Lilie users. Your voice profile and knowledge base are scoped to your account only.

5. How we handle email content (important)

Lilie's design is built around minimizing the amount of email content we retain. This section explains exactly what we keep, where we keep it, and when it's deleted.

5.1 Voice cloning

When you clone your voice, you provide your most recent sent emails to Lilie via an Apps Script export, Google Takeout, or manual upload. Lilie extracts a structured profile (sentence length, openers, sign-offs, characteristic phrases), and discards the raw email bodies after extraction. We retain only the extracted profile, which is stored against your user account in our Supabase database (US region).

The extracted voice profile contains derived patterns — not your original email content. You can delete the voice profile at any time from Lilie's Voice settings, which removes it from our systems immediately (subject to backup retention, see Section 9).

5.2 Knowledge base import

You can export up to 5,000 historical emails per import via the Apps Script tool, or upload an .mbox from Google Takeout, and then upload the result to Lilie. You can also import non-email content via paste, file upload (.txt, .md, .pdf, .docx), or a help-center sitemap. Once uploaded, content is processed as follows:

• The text is split into smaller chunks (typically a paragraph or two each)
• Each chunk is embedded as a vector representation for semantic search
• The chunks and their embeddings are stored in our database (documents and chunks tables in Supabase US), tied to your user account and the specific knowledge base they belong to

The original message bodies are not retained. Only the chunked, processed text required for retrieval is stored.

You can delete this content at any time:

• Delete a single knowledge base — removes all chunks and documents associated with it
• Delete a single import — removes all chunks added by that specific import job
• Delete all data — Settings → Privacy → Delete all data removes every chunk, document, voice profile, and account-related record we hold

When you delete content, it is removed from our production database immediately. Backup copies are retained for up to 30 days before being permanently deleted (see Section 9).

5.3 Response feature

When you use Response mode to view your Gmail inbox inside Lilie, message bodies are loaded into your session in real time and not persisted in our database. They exist only in your browser session for as long as you have the Response view open.

Drafts you generate are stored against your account until you send the draft (which moves it to your Gmail Drafts folder) or delete it from Lilie.

5.4 Sending email

Lilie does not send email and does not write to your Gmail account. Lilie writes the draft text into your Gmail compose window via the Chrome extension (the extension fills the compose editor inside the Gmail page you have open); you review and send it from Gmail yourself. Nothing is created in your Gmail Drafts folder by Lilie's servers.

5.5 No logging of email bodies

We do not log or persist raw email bodies in our application logs, error logs, or any other infrastructure system. If a request fails, the error log captures metadata (timestamp, user ID, error type, stack trace) but not the underlying email content.

5.6 Summary of what's retained from Gmail data

6. Third parties we share data with (subprocessors)

We work with a small number of third-party service providers to operate Lilie. Each provider has access only to the data necessary for their function and is contractually obligated to protect your data.

We do not currently use any third-party analytics, error tracking, or behavioral telemetry providers in production. The PostHog SDK is bundled in our application but is disabled. If we enable analytics in the future, this list and the relevant sections of this Policy will be updated, and we will notify users of the change.

A current list of subprocessors is maintained at lilie.app/subprocessors.

OpenAI data handling

We use the OpenAI API for AI-powered features. Data sent to OpenAI is governed by OpenAI's API data usage policy. Specifically:

• OpenAI does not use API inputs or outputs to train their models
• OpenAI retains API request data for up to 30 days for abuse monitoring, then deletes it
• We do not enable any optional data-sharing features

We do not sell your data, and we do not share it with advertising networks, data brokers, or any third party not listed above.

7. International data transfers

Importify Limited is incorporated in Hong Kong. Lilie's servers and primary data storage are located in the United States. If you access Lilie from the European Economic Area, the United Kingdom, or other regions with data protection laws, your data will be transferred to and processed in the United States and Hong Kong.

For transfers from the EEA/UK, we rely on:

• Standard Contractual Clauses (SCCs) approved by the European Commission, where applicable
• Adequacy decisions between jurisdictions, where applicable
• Your explicit consent for the specific transfer when you connect Gmail or import data

You can request a copy of our SCCs by contacting support@lilie.app.

8. Your rights

Depending on your location, you have rights under applicable data protection laws including the General Data Protection Regulation (GDPR) for users in the EEA/UK, the California Consumer Privacy Act (CCPA) for California residents, and the Personal Data (Privacy) Ordinance (PDPO) for Hong Kong residents.

Your rights include:

• Access — request a copy of the personal data we hold about you
• Correction — ask us to correct inaccurate data
• Deletion — ask us to delete your data ("right to be forgotten")
• Portability — receive your data in a machine-readable format
• Restriction — limit how we use your data
• Objection — object to certain types of processing
• Withdraw consent — for processing based on consent (e.g. voice cloning), at any time
• Opt out of sale — we do not sell personal data, but California residents have an explicit right to opt out
• Lodge a complaint — with your local data protection authority

To exercise any of these rights, contact support@lilie.app. We will respond within 30 days.

You can also:

• Delete your voice profile from Lilie's Voice settings
• Delete imported knowledge base entries or entire knowledge bases from Lilie's KB settings
• Delete a specific import — every KB import is tagged with a job_id, so you can revert any single import in one click
• Delete all data from Settings (gear icon) → Privacy → Delete all my data, which removes every chunk, document, voice profile, draft, and account-related record from our systems. The page also displays live statistics (documents, chunks, contacts, storage bytes) so you can see exactly what is held about you before deletion.
• Delete your account entirely from account settings — this removes all associated data within 30 days

9. Data retention

We retain your data only as long as necessary:

When you delete your account, we delete all associated data within 30 days, except where we are required to retain it for legal or regulatory reasons.

10. Security

We take reasonable technical and organizational measures to protect your data, including:

• Encryption in transit — all data is transmitted over HTTPS/TLS
• Encryption at rest — databases and backups are encrypted at rest
• Access controls — only authorized personnel have access to production systems, and access is logged
• Regular updates — we keep dependencies and infrastructure patched
• Incident response — we have a process for detecting and responding to security incidents

If we discover a data breach that affects your personal data, we will notify you and the relevant authorities as required by applicable law, generally within 72 hours of becoming aware of the breach.

No system is 100% secure. If you discover a security vulnerability, please report it to support@lilie.app.

11. Children's privacy

Lilie is not intended for users under the age of 16. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, contact support@lilie.app and we will delete it.

12. Changes to this Policy

We may update this Privacy Policy from time to time. When we make material changes, we will:

• Update the "Last updated" date at the top of this Policy
• Notify you by email if you have an active Lilie account
• Post a notice in the Lilie web application

Your continued use of Lilie after changes are posted constitutes acceptance of the updated Policy.

13. Contact us

For any questions, requests, or concerns about this Privacy Policy or your data, contact:

Importify Limited Unit 1603, 16th Floor, The L. Plaza 367–375 Queen's Road Central Sheung Wan, Hong Kong

Email: support@lilie.app

For users in the EEA, you may also contact your local data protection authority. A list is available at edpb.europa.eu.