Legal

Privacy Policy

Effective March 10, 2026Last updated March 10, 2026

Lernex (“we,” “our,” or “us”) provides study planning, learning, and academic productivity tools. This Privacy Policy explains what information we collect, how we use it, how we protect it, and what choices you have.

This policy applies to our website, mobile app, and related services, including optional Google Classroom and Google Calendar integrations.

2Information We Collect

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

Account & Profile

Email, sign-in method, name, username, avatar, bio, interests, profile visibility settings, onboarding responses, and account preferences.

Learning & Progress

Lesson history, quiz attempts, saved lessons, flashcards, terms, playlists, streaks, points, placement progress, and mastery-related data.

Content & Uploads

Prompts, uploaded documents and images, OCR text, generated lesson content, audio uploads for transcription, and TTS-related settings or assets.

Social & Community

Friend relationships, study sessions, challenges, tutoring threads, feed activity, comments, reactions, and notifications.

Usage & Technical

IP address, request metadata, authentication cookies, local storage preferences, timezone context, and abuse-prevention or rate-limiting identifiers.

Payments & Rewards

Subscription status, billing identifiers, purchase history, points, sparks, boosts, and reward inventory.

3How We Use Your Information

  • 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.
  • Send transactional emails, support replies, and service notices.
  • Import Google Classroom assignments or sync Google Calendar events when you explicitly connect those integrations.

4AI Processing & Personalization

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.

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.

5Google API Data & Integrations

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:

  • https://www.googleapis.com/auth/classroom.courses.readonly
  • https://www.googleapis.com/auth/classroom.coursework.me
  • https://www.googleapis.com/auth/classroom.student-submissions.me.readonly
  • https://www.googleapis.com/auth/calendar.events

For these integrations, Lernex does not request:

  • https://www.googleapis.com/auth/calendar.calendarlist.readonly
  • https://www.googleapis.com/auth/userinfo.email
  • https://www.googleapis.com/auth/userinfo.profile

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

  • Course names and course IDs.
  • Coursework titles, descriptions, due dates, states, max points, and alternate links.
  • 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.

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

  • Google Classroom data is used to import coursework into your assignment planner.
  • Google Calendar data is used to create or update events for due dates and study blocks.
  • Google API data is not sold and is not used for advertising.

6Sharing of Information

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.
  • 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.

7Public & Social Features

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.

8Security & Data Protection

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.
  • 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.

9Data Retention

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.
  • Placement progress may expire after about 30 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.

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.

10Cookies & Tracking Technologies

  • 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.

11Your Rights & Choices

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.
  • Request account or data deletion by contacting support.
  • 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.

12Children’s Privacy

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.

13Contact Us

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

support@lernex.net
This policy was last updated on March 10, 2026. We may update it from time to time, and continued use of Lernex after changes means you accept the revised policy.