Level Up legal center

Privacy policies and platform terms built for secure learning.

We protect user data, reports, course content, MCQs, notes, videos, access controls, and imports with clear responsibilities for every role.

Read policiesLast reviewed for Level Up workflows.

Protected learning records

Reports, attempts, enrollments, and content permissions stay role-aware.

Best features of Level Up policies

Protect learners and operations

Role-based dashboards, protected routes, and private report views help keep student, creator, and admin data separated.

Reduce avoidable legal risk

Clear policies reduce avoidable disputes around notes, MCQs, live tests, enrollments, imports, and account access.

Coverage across platform roles

The policy covers students, creators, course managers, token managers, administrators, and public visitors.

No vague templates

Security expectations are written plainly so users know what is allowed, restricted, logged, and reviewed.

Policy updates

Terms can be updated when product workflows, privacy requirements, or abuse patterns change.

Accessible documents

Users can review their responsibilities and understand how to request profile updates or account deletion.

Privacy policies with responsible coverage

Level Up operates around private learning data. These terms explain what we collect, how access is controlled, what users may not do, and how security concerns should be handled.

1. Data We Collect

Name, email, phone number, role, account status, authentication identifiers, and profile details.
Course and plan enrollments, requests, approvals, removals, and access history.
MCQ attempts, responses, scores, duration, reports, live-test participation, and analysis records.
Device and session metadata such as browser, operating system, device type, login time, and security signals.
Uploaded or imported content such as notes, videos, question banks, explanations, images, tags, and admin files.

2. How We Use Data

To provide course access, notes, videos, MCQs, live tests, attempts, reports, and dashboard features.
To verify user roles and prevent unauthorized access to private content or administrative tools.
To maintain platform security, investigate abuse, audit sensitive actions, and prevent account sharing.
To support users, resolve operational issues, process deletion requests, and improve platform stability.

3. Role-Based Access

Students can access only their approved learning content and their own reports.
Creators and course managers can access only content and subjects allowed by administrators or token managers.
Administrators manage users, courses, plans, limits, activity, imports, reports, and access permissions.
Token managers can manage allowed access areas but cannot view activity logs unless explicitly authorized by role rules.

4. Data Protection

We do not sell student, creator, manager, or administrator data.
We use secure sessions and server-side authorization checks before showing private dashboard data.
Administrative and sensitive actions may be logged for accountability, security, and dispute review.
Internal access is limited to legitimate platform operation, support, security, or legal needs.

5. User Responsibilities

Users must keep credentials private and must not share accounts, sessions, reports, notes, videos, or MCQ content.
Users must not bypass permissions, scrape content, probe APIs, exploit bugs, upload malicious files, or overload the service.
Creators and managers must upload only content they are authorized to use and manage.
Students must use purchased or approved content for personal learning unless written permission says otherwise.

6. Content Terms

MCQs, notes, videos, course structures, explanations, imports, reports, and dashboard data are protected platform content.
Copying, reselling, leaking, republishing, exporting, or distributing protected content without permission is prohibited.
Uploaded content may be reviewed, restricted, removed, or corrected if it violates platform rules or law.

7. Prohibited Activity

Attempts to access another user's account, reports, files, MCQs, admin pages, APIs, or database records are forbidden.
Suspicious behavior may lead to session revocation, account suspension, permission removal, audit review, or permanent restriction.
Serious leaks, theft, malicious access, or service attacks may be reported to institutions, providers, or lawful authorities.

8. Breach Response

If a breach is suspected, Level Up may lock sessions, revoke access, preserve evidence, investigate scope, and correct affected systems.
Users should report suspicious access, exposed data, malicious files, copied content, or credential sharing immediately.
Users must not forward leaked data or publish screenshots that expose private records.

9. Retention And Deletion

We retain records needed for learning history, reports, security, audits, support, legal compliance, and operational continuity.
Students may request account data deletion from the profile page. Verified requests are reviewed before completion.
Some records may be retained where needed for security evidence, financial records, dispute handling, or legal obligations.

10. Cookies And Sessions

The platform uses secure cookies and session checks to keep users signed in and to protect dashboard access.
Session metadata can help detect unusual device changes, unauthorized access, or account sharing.
Disabling required cookies may prevent sign-in or dashboard functionality from working correctly.

11. Updates And Contact

Level Up may update these terms when features, laws, operations, or security practices change.
Continued use of the platform after updates means the user accepts the updated terms.
Questions or concerns should be raised through official platform support channels.

Security concerns need immediate attention.

If you notice unauthorized access, exposed data, copied course material, suspicious imports, credential sharing, malicious files, or anything that could harm users or Level Up, contact platform support immediately and do not forward private data to anyone else.