Privacy Policy

Account details. If you create an account: your email address and a password (stored only as a hash by our authentication provider). If you sign in with Google: the email address, name and profile picture Google shares with us.

Learning data. When you are signed in, your device syncs to your account: saved vocabulary and review schedules, reading history and favourites, grammar and learning-path progress, placement-test results, word-list plans, and preferences such as your level, target language and translation language.

Texts you import. Text you paste into the importer is processed and saved to your account so you can read it again. It is not offered to other learners.

Usage counts. For signed-in users we count, per day, how many times each part of the app (reader, flashcards, dictation…) was opened. We use this to run plan limits and to see which features are used.

Payments. If you subscribe, our payment processor Stripe collects your card details. We never see or store your full card number; we keep your Stripe customer ID, subscription status and renewal dates.

Messages to us. If you use the contact form, we receive the name, email address and message you enter.

Technical data. Like most websites, our servers receive your IP address, browser type and the pages you request. When the app crashes, it sends an error report (the error message, page and browser) so we can fix it. Our logs strip anything that looks like a password or key.

Signed out, everything you do stays in your browser's or app's local storage and never reaches us. Some data stays local even when signed in: the AI provider keys you enter in Settings, your word-lookup history, your "too hard / too easy" feedback on readings, and your answers on the writing drill. Signing out uploads your synced data and then clears this device.

• To provide Lirami: generate readings at your level, schedule reviews, sync across your devices.
• To run your account and subscription, including plan limits and billing.
• To answer your messages and send essential service emails (sign-in links, password resets, receipts). We do not send marketing email.
• To keep Lirami secure and working: rate limits, abuse prevention, debugging.
• To improve Lirami using aggregated usage statistics.

We do not sell your personal information, share it for cross-context advertising, or use it to train AI models. If you are in the EEA or UK, we rely on contract (to provide the service you asked for), legitimate interests (security, improvement) and legal obligation (tax and accounting records).

Readings, grammar drills, explanations and translations are produced by third-party AI services. To do that we send them the request itself — for example your level, a topic, words you are learning, or the text you imported — but not your email address or name.

• On the shared free tier, requests may go to Anthropic (Claude), Zhipu AI (GLM, servers in China), or OpenRouter and the model providers it routes to.
• Translations may be sent to DeepL.
• If you add your own API key, your requests go to the provider you chose, under your own agreement with them. Your key passes through our server only to make that request and is never stored there.

Read-aloud audio is generated either by our own server or by your browser's built-in speech engine, which may use your operating system vendor's service.

We use these companies to run Lirami. Each processes data only on our behalf and under its own security and privacy commitments:

• Vercel — hosting, and privacy-friendly page analytics that use no cookies and no cross-site identifiers.
• Supabase — database and sign-in.
• Stripe — payments and subscription management.
• Google — "Sign in with Google", only if you choose it.
• Resend — delivery of contact-form messages.
• The AI and translation providers listed above.

We may also disclose information if the law requires it, to protect the rights and safety of our users or others, or as part of a sale or reorganisation of the business, in which case this policy continues to apply.

Readings generated by the AI are kept in a shared library so another learner who asks for a similar topic and level can get one instantly. These readings contain no information about you. If you delete your account, readings you generated stay in the library with no link to you.

We keep your account and learning data until you delete your account. Deleting it (Account → Delete account) cancels any subscription and permanently removes your profile, vocabulary, progress and imported texts from our database. Stripe keeps payment records as tax law requires. Server logs and error reports are kept for a short period by our hosting provider and then deleted. Contact-form emails are kept as long as needed to deal with your message.

You can see and edit most of your data in the app, and delete your account at any time from the Account page. Depending on where you live (for example under the GDPR, UK GDPR, California law or China's PIPL) you may also have the right to access, correct, export, restrict or object to the processing of your data, and to withdraw consent. To make a request, contact us; we will answer within 30 days. You may also complain to your local data-protection authority.

Our providers operate servers in the United States and other countries, and some AI requests are processed in China. Where the law requires it, transfers rely on safeguards such as the European Commission's Standard Contractual Clauses.

Data is encrypted in transit, access to your account data is restricted to you by row-level security in our database, and secrets are never logged. No system is perfectly secure; if we learn of a breach affecting you, we will tell you as the law requires.

Lirami is not directed at children under 13, and we do not knowingly collect their personal information. In the EEA, users under 16 need a parent's consent to create an account. If you believe a child has given us data, contact us and we will delete it.

We will post changes to this policy here and update the date above; for material changes we will also tell signed-in users in the app. Questions? Reach us through the contact form. See also our Terms of Service and Cookie Policy.