What stays on your computer
Your subjects, study maps, progress notes, lesson notes, speech settings and downloaded speech models are stored locally. These files are local study aids. Relevant lesson text and context can be included in AI requests described below. Sessions save in a local database and readable Markdown files. You can export or back them up.
Cloud accounts and credits
If you create a cloud account, Lumora’s backend stores your email, password hash, whether your email is confirmed, your plan, account status and credit records. Usage records track token counts, cost and credit changes for each request. Account administration is used to manage access and credits and to investigate problems. Passwords are hashed; the service does not store them in plain text. To limit abuse of free credits, the server keeps short-lived counters keyed to a one-way hash of your IP address.
Account emails
We email you to confirm your address, when you ask to reset your password, and when your account is deleted. These emails are sent from hello@lumoratutor.app through our email provider, Resend. We do not send marketing emails.
AI lesson requests
Lesson text, relevant conversation context and any study images or document excerpts you attach are sent to an AI provider so it can answer. Educational diagrams are generated as SVG code by a text model and rendered in the app. With cloud access, requests pass through Lumora’s backend to the configured provider, currently through OpenRouter. The backend does not store chat prompts or completions as lesson history; your local app keeps that history. Providers handle requests under their own policies. If you use your own provider key, requests use that provider account.
Speech and optional web checks
Speech recognition and synthesis run locally after the required models download. Speech audio is not uploaded for these local features. Before online plan research, Lumora asks permission and shows editable search terms. Approved terms go to Wikipedia and DuckDuckGo, which also see your IP address. You may continue without research. This permission is separate from AI lesson requests.
Google sign-in
Where available, Google sign-in supplies your verified email, name and profile photo. The app uses these to establish a local profile and cache the photo. It does not request access to your contacts or Drive. Google processes the sign-in under its own privacy policy. On the website, Google sign-in confirms your email address and connects your Google account to your Lumora account.
Payments
Paid plans have not opened yet. When they do, payments will be handled by our payment provider, acting as reseller and Merchant of Record; we will name it and link its privacy policy here first. It collects your payment details, billing country and tax information under its own privacy policy. We receive your email address, your plan, the subscription status and the provider’s customer and subscription references, and use them to give you the right plan and credits. We never see or store your card number.
Website and updates
The website is hosted on Vercel, and the cloud API runs on a hosted server. Hosting providers process connection information such as IP addresses and request logs. The Account page loads Google’s sign-in script from accounts.google.com. App update checks contact the release feed.
Feedback and crash reports
When you send feedback from the app, we store your answers, your account email if you are signed in, the app version, your operating system and, if you leave that box ticked, a short summary of settings such as theme and accessibility options. Crash reports are optional: Lumora asks before sending one unless you chose Always or Never in Settings. A crash report contains the error message, a stack trace with personal file paths removed, the app version and your operating system. Feedback, credit requests and crash reports are kept on our server and forwarded to the team’s inbox. Do not send passwords or API keys in feedback.
Cookies
The website sets one essential cookie when you sign in: __Host-lumora, a Secure, HttpOnly session cookie that keeps you signed in for up to 30 days. It is not used for advertising or analytics. Signing out clears it. Google sign-in and the payment provider’s checkout may set their own cookies while you use those services; their policies apply.
Control and deletion
You can remove local learning files using the app’s data controls or by deleting the app’s data folder. This does not remove your cloud account. You can delete your cloud account yourself on the Account page or in the app’s profile panel. Deletion removes your account, sign-ins, sessions, credit balance and usage history; feedback and crash reports you sent stay, without your email address. For access or correction requests, contact us from the account’s email. We may need information to confirm that the account belongs to you.
Children
Lumora is not directed at children under 13, and we do not knowingly collect their personal information. Contact us if you believe a child under 13 has used the service.
Contact and updates
Lumora is operated by Nikola Babic under the name Apodeixis. Privacy questions: support@lumoratutor.app. We will update this page as the service changes, including before optional sync is introduced.