Privacy Policy

We collect information you provide directly, information created by your use of the Service, and technical data required to operate and secure Lernex.

• —Provide, maintain, and secure accounts, sessions, and core product functionality.
• —Generate lessons, quizzes, flashcards, explanations, and study recommendations.
• —Track progress, streaks, goals, analytics, and assignment planning.
• —Operate social, collaboration, leaderboard, and community features.
• —Enforce usage limits, detect abuse, debug failures, and improve reliability.
• —Find and fix crashes, hangs, and slow launches, and check whether a new app version is stable.
• —Learn when you usually study, so reminders and nudges arrive at useful times.
• —Send transactional emails, support replies, and service notices.
• —Import Google Classroom assignments, personalize study actions from connected classwork, or sync Google Calendar events when you explicitly connect those integrations.

Lernex uses AI models to generate study content, analyze responses, process uploads, and support personalization. Depending on the feature, text, documents, or audio you submit may be sent to AI providers for processing.

• —Lesson, quiz, flashcard, and explanation generation.
• —OCR for uploaded documents and images.
• —Speech transcription and text-to-speech features.
• —Mistake analysis, learning signals, and personalization logic.
• —Support and product-quality tooling.

Your learner profile. Lernex keeps a profile of what it has learned about how you study, such as your goals, the style of explanation you prefer, your pace, the subjects you are active in, and mistakes you keep repeating. You can read it on your Memory page, where each item can be confirmed, corrected, or forgotten.

Estimating how a study session is going. From the timing of your answers, your pauses, hints, skipped questions, and changed answers, Lernex estimates whether you seem confident, engaged, struggling, frustrated, confused, overwhelmed, bored, or neutral. It uses that estimate to adjust a lesson or offer help, such as a hint, a simpler explanation, a worked example, or a break. These estimates are saved with your account.

Reading how you write. When you explain an idea or ask a question, Lernex reads the wording with pattern rules and with an AI model run by a third-party provider. That reading looks for misconceptions, how you reason about a topic, and the tone of what you wrote. It feeds your learner profile and the lessons built for you.

You can turn off behavioral personalization in Settings. Lernex then stops reading your pace, timing, and interaction patterns. Turning it off does not stop the device, crash, and sign-in records described in this policy.

Automated personalization in Lernex is used to tailor educational content and study guidance. It is not used to make decisions with legal or similarly significant effects.

Google integrations are optional. We request Google scopes only when you choose to connect the related feature.

The Google scopes currently requested by Lernex are:

• —openid
• —https://www.googleapis.com/auth/userinfo.email
• —https://www.googleapis.com/auth/userinfo.profile
• —https://www.googleapis.com/auth/classroom.courses.readonly
• —https://www.googleapis.com/auth/classroom.coursework.me
• —https://www.googleapis.com/auth/classroom.topics.readonly
• —https://www.googleapis.com/auth/classroom.courseworkmaterials.readonly
• —https://www.googleapis.com/auth/classroom.announcements.readonly
• —https://www.googleapis.com/auth/drive.file
• —https://www.googleapis.com/auth/calendar.events
• —https://www.googleapis.com/auth/calendar.events.freebusy

Lernex does not request these broader Google Calendar or Drive permissions:

• —https://www.googleapis.com/auth/calendar.calendarlist.readonly
• —https://www.googleapis.com/auth/drive
• —https://www.googleapis.com/auth/drive.readonly

When you use Google sign-in, we may collect and store:

• —Your primary Google Account email address and whether Google reports it as verified.
• —Your basic Google profile information, such as your name and profile picture, to authenticate you and initialize your Lernex account and profile.

When you connect Google Classroom, we may collect and store:

• —Course names and course IDs.
• —Coursework titles, descriptions, due dates, states, max points, work type, Classroom topics, and alternate links.
• —Visible coursework, announcement, and class-material metadata such as titles, links, file type labels, descriptions, and related Google Classroom assignment metadata.
• —For supported Google Drive files attached to Classroom items that you explicitly choose through Google Picker, file metadata and downloaded or exported file contents. Lernex may extract or OCR text and store derived text chunks and embeddings so connected learning features can retrieve relevant material.
• —Your own Classroom submission status, lateness, and available grade fields for imported coursework.
• —Integration status, sync timestamps, and error information needed to keep the connection working.

When you connect Google Calendar, we may collect and store:

• —OAuth access tokens, refresh tokens, expiry timestamps, and granted scope metadata.
• —Calendar sync state such as Google event IDs, ETags, sync timestamps, error states, and the target calendar ID.
• —The assignment due dates and study blocks generated inside Lernex that you choose to sync to Google Calendar.
• —Busy-only time windows from the selected calendar so Lernex can avoid scheduling study blocks during conflicts; this does not include event titles, descriptions, attendees, locations, or full event contents.

We use Google API data only to provide the user-facing integration features you request.

• —Google Classroom data and relevant text extracted from Classroom-linked Drive attachments that you select are used to import coursework into your assignment planner and to ground learner-facing lessons, explanations, quizzes, flashcards, reviews, recommendations, and Today/Generate prompts in connected schoolwork.
• —Lernex uses the per-file https://www.googleapis.com/auth/drive.file permission. It does not list files across your Google Drive or create, edit, or delete Drive files. Classroom may show the titles of linked attachments, but Lernex can retrieve a file only after you choose that file in Google Picker.
• —Google Calendar data is used to create or update events for due dates and study blocks, and to avoid calendar conflicts in auto-generated study plans.
• —Google API data is not sold, is not used for advertising, and is not used to train generalized AI models.

We do not sell your personal information.

We may share information only in limited circumstances necessary to operate the Service, comply with law, or complete a business transaction.

• —Service providers for hosting, storage, email delivery, analytics, payments, and AI processing.
• —Apple and Google, whose push notification services deliver notifications to your devices: Apple for iPhone, iPad, and Mac, and Google for Android.
• —An error-monitoring endpoint that we configure to receive a copy of crash reports, if we configure one. It receives the report described in section 13 and nothing else.
• —Other users when you use public or shared features such as public profiles, leaderboards, playlists, tutoring threads, or social feed activity.
• —Legal, regulatory, security, or fraud-prevention disclosures when required or reasonably necessary.
• —Business transfers such as a merger, financing, acquisition, or asset sale.

If we produce aggregated or de-identified product insights, we do so to avoid identifying individual users. Google API data and data derived from Google API scopes are not sold and are not shared except as needed to provide, secure, or legally support the integration you requested.

Lernex includes social and community features. Your username, avatar, bio, selected stats, public playlists, feed activity, and tutoring-thread content may be visible to other users depending on your privacy settings.

Your real name is hidden by default unless you choose to show it on your public profile.

We use administrative, technical, and organizational measures designed to protect personal information and sensitive integration data.

• —Data is transmitted over encrypted network connections in production.
• —Google and Canvas OAuth tokens are stored encrypted at rest on our servers.
• —OAuth state parameters are signed to help prevent tampering.
• —Sensitive integration actions run server-side; tokens are not exposed to other users.
• —On a Mac, your sign-in session is kept in the macOS Keychain. On a Windows PC, it is kept in a file in your user profile, encrypted with Windows' own per-user protection.
• —Database access is restricted with user-scoped access controls and row-level security where implemented.
• —We retain sync metadata, error logs, and audit-style operational records only as needed to operate, secure, and troubleshoot the Service.

No system is perfectly secure, but we work to reduce risk through encryption, access controls, environment-based secrets, and least-privilege design.

We retain data for as long as reasonably necessary to provide the Service, comply with legal obligations, resolve disputes, and enforce agreements.

• —Quiz progress is generally short-lived and may expire after about 7 days of inactivity.
• —Pending lesson queues are typically cleaned after about 7 days.
• —Non-saved lesson history entries may be cleaned after about 30 days.
• —Upload-history, cache, and signal-related records may be removed on shorter rolling schedules depending on feature type.
• —Billing, abuse-prevention, and security-related records may be retained longer when needed for accounting, legal, or security reasons.
• —Crash and hang reports are kept without your user ID, for as long as they are needed to track stability.
• —Each account keeps up to 40 device records, each updated at its next check-in.
• —Signing out removes that device's push registration, so the device stops receiving notifications for the account.

OAuth tokens and integration metadata are retained while an integration remains active and may be replaced when reauthorized. You may also revoke Google access directly from your Google Account permissions page.

• —Authentication cookies to keep you signed in.
• —Local or session storage for preferences, onboarding flags, and interface state.
• —Performance and analytics tooling used to monitor reliability and usability.

Depending on your location, you may have rights to access, correct, export, or delete personal information.

• —Update your profile, visibility settings, and preferences in the product.
• —Turn off behavioral personalization in Settings. Choose which notifications the iPhone, iPad, Android, and Mac apps send you in those apps' own Settings.
• —Disconnect Google Classroom to revoke its integration token and remove imported Classroom assignments, course records, attached-material records, and stored extracted material chunks from Lernex.
• —Disconnect Google Calendar to revoke its integration token and remove cached busy-only windows and local event-sync records from Lernex. Events already added to Google Calendar remain in your calendar.
• —Delete your account yourself from Settings → Delete account on the web, or from Account → Delete account in the iPhone and Android apps, or from Settings → Delete account in the Mac and Windows apps. Full deletion instructions.
• —Request account or data deletion by contacting support if you cannot sign in.
• —Revoke Google integration access from your Google Account permissions page.

If you use the in-app account deletion flow, some related operational or legal records may still be retained where required.

Lernex is not intended for children under 13, or under a higher age threshold where required by local law. We do not knowingly collect personal information from children without appropriate consent.

The Lernex extension for Chrome is optional, and it is off on every website until you turn it on for that website. Installing it grants access to lernex.com only, which is where it collects your sign-in. Access to any other site is requested separately, one site at a time, and Chrome’s own settings can withdraw it at any point.

On a site you have turned it on for, the extension reads:

• —The text of the writing field you are actually writing in, once it is long enough to review. This is stored in your Lernex account as a document, in the same place and under the same controls as anything written on the Lernex Write page.
• —The address of the page, without its query string, so that a draft in your Lernex library can link back to where you were writing it.
• —The page's own title or heading, to give that draft a name you will recognise.

The extension does not read:

• —Anything on a site you have not turned it on for.
• —Your browsing history, your bookmarks, your open tabs, or any page you are not writing on.
• —Any page on a sign-in, authentication or payment provider. The extension refuses to run on those regardless of what you have allowed it, and that refusal is in the extension itself rather than being a setting.
• —Any field it identifies as a password, email, telephone, search or similar input.

Which field a draft came from is stored as a one-way hash rather than as a description of the page, so the record we hold cannot be read back as an account of the sites you visit.

Google Docs.When you use the extension in Google Docs, the document is read by your own browser asking Google for it, using the Google session you are already signed into. Lernex servers do not read your Google Docs unless you explicitly hand over a single document through Google’s own file picker, which is how the https://www.googleapis.com/auth/drive.file scope works: it grants access to the individual files you choose and to nothing else in your Drive. That access is only ever used to write a change you asked for into that document.

Text collected by the extension is used to review your writing and, where you have left that setting on, to shape how Lernex teaches you. It is never sold, never used for advertising, never used to train a model for anyone else, and never shared with a third party beyond the processors named in this policy. Removing the extension stops all of it; deleting a draft in Lernex deletes the text.

The Mac and Windows apps send the same requests to the same servers as the website. This section covers what is specific to them: what they keep on your computer, what they send beyond the website’s requests, and how they update.

• —Kept on your computer.On a Mac, copies of your lessons, library, and analytics, and read-aloud audio, are kept in the app’s folders in your user account, and preferences are kept in the app’s defaults. On Windows, copies of your lessons, library, and drafts are kept in a Lernex folder in your local app data, read-aloud audio is kept there too, and preferences are kept in your user registry. Read-aloud audio on a PC is capped at 400 MB, and the least recently played is removed first. Today also keeps a short record on the PC of the late nights you study, so the page can change its background; it is not sent to Lernex and is removed when you sign out.
• —Signing out. Signing out removes the copies of your lessons, library, analytics, and drafts from that computer, and on Windows the read-aloud audio you heard. Work that has not reached Lernex yet stays on the computer for the same account until it is sent. Deleting your account removes it.
• —Device check-ins. When an app opens, or comes back to the foreground, at most every six hours, it tells Lernex the kind of device it runs on: phone, tablet, or computer, its operating system and version, the app version, the screen size, and the language setting. On a Mac it also sends the hardware model. A check-in carries no identifier that follows the computer.
• —App open and close. The apps report when a session starts and ends, how long it was in front, and which area you were in when you left, so Lernex can learn your usual study times.
• —Crash and hang reports. A Mac reports the crash and hang diagnostics that macOS collects for Lernex: the exception type and code, the app and macOS versions, and the names and offsets of the code that was running. A Windows PC reports the name and offset of the module that faulted, the Windows and app versions, and the processor type. Where the app knows it, a report also names a broad area of the app, such as lessons or sign-in, from a fixed list. Neither sends your name, your email address, or what you wrote, and Lernex stores each report without your user ID. A Windows crash dump is read on the PC and never uploaded; only its summary is sent, once you are signed in, and until then the report waits on the computer.
• —Notifications.On a Mac or a PC, Lernex can schedule one local reminder a day, at an hour you choose, naming what is still waiting, such as reviews or coursework due. It is worked out and kept on that computer, not sent to us, and it is removed as soon as nothing is waiting. You can switch it off with “One reminder in the evening” in the apps’ notification settings. Your Mac also registers a push token with Lernex, so that notifications from our servers can reach it. You can turn notifications off in System Settings on a Mac, or in Windows Settings on a PC, at any time.
• —Updates.The Mac app checks for new versions with Sparkle, an open-source updater, which reads an update feed on lernex.com. Sparkle’s system profiling is off, so the check does not send a profile of your Mac. The Windows app checks for updates through Windows App Installer, which reads an .appinstaller file on lernex.com. Both checks are ordinary web requests, so lernex.com sees your IP address and the version of the app that is asking.
• —Studio on the Mac. The Mac app includes Studio, a code workspace. Studio works with the folders you open on your Mac and keeps recent workspaces, task drafts, and code-index snapshots there. It does not send your files or their contents to Lernex. Its preview window loads only the pages you type into it, and it keeps no web storage between sessions.

If you have questions about this Privacy Policy or want to make a privacy-related request, contact us at: