Lilu.

Legal

Privacy Policy

Last updated: October 13, 2026 — operated by Ilya Litau, contact [email protected]

This page explains what the Lilu app for iPhone and Android (“Lilu”, “the app”) and this website (lilu.litau.app) collect, why, and how you can control it. Lilu is operated by Ilya Litau, an individual developer (“I”, “me”). If anything here is unclear, write to [email protected] — a person reads that inbox.

1. Account and sign-in (optional)

Signing in is optional. If you want your access, saved words and progress to follow you to another phone, you can sign in with Google or Apple. When you do, my backend (Supabase) stores your email address, your name if Google or Apple provides it, and a random user ID. Your email and name are used only to sign you in and manage your account; I do not send them to analytics or crash reports.

2. What I collect

CategoryWhat it isLinked to youPurpose
Account
(Supabase)		 Email address, name (if Google or Apple provides it) and a random user ID — only if you sign in Yes — it is your account Signing you in, managing your account, linking your access to it
Cloud copy of your learning data
(Supabase)		 If you are signed in: a copy of your saved words, learning progress, streaks and achievements, so they can be restored on a new phone Yes — tied to your account Syncing and restoring your data. Deleted together with the account
Clip history
(Supabase)		 The IDs of the clips the app has shown you, the time each one was first shown, and whether it came from the main feed or the free trial feed. Nothing else is stored in it Yes — to an anonymous ID: a scrambled (hashed) form of the app user ID that RevenueCat assigns to your install and purchase. Not to your name or email Not showing you the same clips again after you reinstall the app or use a second phone. Kept while you use the app; deleted together with your account or when you ask me to. “Reset local learning data” does not delete it
Purchases
(App Store / Google Play / RevenueCat)		 Your purchase and subscription status and the app user ID RevenueCat assigns. Payment details stay with Apple or Google — I never see your card. If you enter an access code, it is recorded as redeemed and linked to your account (if you are signed in) Tied to your Apple ID or Google account by the store; an access code is linked to your Lilu account Unlocking paid content, restoring purchases
Early-access payment on the website
(Paddle)		 Your payment details, handled entirely by Paddle on its own checkout, plus the email address Paddle passes to me with the payment so I can send you your access code Held by Paddle and tied to your order — never joined to your analytics or crash-report identity Processing the one-time early-access purchase sold on this website and delivering what you paid for
Product usage
(PostHog)		 Which screens you open, video plays, word taps, subscription-screen views and similar in-app actions, plus coarse device and app info (OS and version, device model, app version, language) No — not joined to your name, email or account Understanding which parts of the app work, and improving them
Session recordings
(PostHog)		 A recording of what happens on screen during a session in the app. Text fields, images, the embedded YouTube player and the screens with personal content (profile and settings, saved words and review, subscription and access code, sign-in, the feedback form, reward pop-ups) are blacked out before saving. The interface text of the other screens, such as the feed and onboarding, is recorded as it is. PostHog keeps a recording for up to 30 days and then deletes it automatically No — not joined to your name, email or account Seeing where people get stuck — onboarding, the paywall screen, the feed — without waiting for a written complaint
Crash reports
(Sentry)		 Automatic diagnostic information if the app crashes or logs an error No — not joined to your name, email or account Finding and fixing bugs
Device identifiers A random install ID created on first launch (it resets when you reinstall the app or reset local data). On Android, the device’s ANDROID_ID is also used to count how many devices use one access code. I do not use your advertising ID Not tied to your name or email. The code-limit identifier is kept with the access code it counts Analytics, limiting one access code to a few devices, preventing abuse
AI word explanations
(Anthropic)		 When you ask for an AI explanation of a word, my server sends Anthropic the word, the Chinese sentence it appears in and your interface language. No name, email or account details are sent. Finished explanations are cached on my server so the same question is not asked twice No — Anthropic receives no account details Explaining a word in context
Feedback and problem reports
(PostHog)		 What you type into the optional “Leave feedback” form or a problem report, with the platform and app version. The text goes to PostHog and is forwarded by a Telegram bot to a private Telegram chat that only I read — Telegram acts as the delivery service. It is not linked to your name, email or account; to get a reply, write to me by email No Making the app better
Launch email
(waitlist)		 The email address you type into the “notify me” form on this website, plus the country Cloudflare reports for your connection and the page you arrived from Yes — it is your email address, and it is never joined to your analytics or crash-report identity Emailing you when the app is out. Kept until I send that email or you ask me to delete it, whichever comes first
Video catalog
(Supabase)		 Requests for the current clip catalog and its transcripts No — not joined to your name, email or account Delivering the clips and transcripts you scroll through

I do not collect your location. Every analytics event tells PostHog to discard your IP address and not to look up a location. Every property I send is also screened for anything shaped like an email address, name, phone number or full web address before it leaves your device, as a second layer of protection behind simply not collecting that information in the first place.

3. What I deliberately do not do

4. How long I keep it, and how to delete it

Your learning data on the phone (saved words, progress, settings) stays there as long as Lilu is installed; deleting the app removes it. In the app, Profile → Settings → “Reset local learning data” clears it immediately and starts a new, unlinked install ID. The one exception is the list of clips you have been shown (see “Clip history” in section 2): I keep a copy of it on my server so that clips do not repeat after a reinstall or on a second phone, and resetting local data does not erase that copy.

I delete the clip history on my server together with your account (see below), and on request. If you never signed in, or the history was not removed when you deleted your account, email [email protected] and attach the Order ID from your Apple receipt for Lilu (on Android, the Google Play order number). I use it to find and delete your clip history.

If you signed in, your account and its cloud copy are kept until you delete the account. To delete it: in the app go to Profile → Settings → Account → Delete Account, or follow the steps on lilu.litau.app/delete-account (it also explains how to ask by email). The account, the cloud copy, the clip history and the link to your access code are deleted as soon as you confirm; anything I have to remove by hand after an email request, I remove within 30 days.

Anonymous analytics and crash records held by my providers are kept for those tools’ own retention periods (session recordings: up to 30 days) and are not matched to a named person, because I do not send them a name or email. If you want a specific record looked into or removed, write to [email protected] with the approximate date and device.

5. YouTube and Google

Every clip in Lilu plays through YouTube’s official embedded video player. That player belongs to Google, and it can set its own cookies and collect its own data under Google’s Privacy Policy and the YouTube Terms of Service — this is true of any app or website that embeds a YouTube video, and it sits outside my control. I do not download, store or re-host any YouTube video or audio.

6. Children

Lilu is not directed at children under 13, and I do not knowingly collect personal information from them. If you believe a child has given me personal information, write to [email protected] and I will remove it.

7. Where your data is processed

My service providers run infrastructure in the United States and other countries. Using Lilu means the data described above may be processed outside the country you are in.

8. Service providers I use

These providers process data on my behalf to run the app; I do not sell data to them or to anyone else.

9. Changes to this policy

I update the date at the top of this page whenever this policy changes and post the new version at this same address.

10. Contact

Email [email protected] for privacy questions, data requests, or anything else about how Lilu handles data. Operator: Ilya Litau.