How PrymeStudy handles personal, academic, device, payment, community and product-usage data across the public website, student experiences, Lerion, Daily Mission and institution workflows.
Last updated August 29, 2026
1. Scope and who operates PrymeStudy
This policy applies to PrymeStudy public pages, accounts, student experiences, tutor and lecturer workflows, institution tools, PrymeStudy Social, Lerion and other automated study features, Daily Mission, materials, live classes, attendance, billing, support and related services.
PrymeStudy is an education technology product operated by Lerion Jake Nwauda Digital Innovations Ltd. Different features may process different categories of data depending on how you use the service.
2. Accounts, identity and profile information
We may process information such as name, email address, authentication provider, account status, role, institution, college, department, academic level, matric number where supplied, profile photo, biography, preferences, verification state and onboarding information.
Authentication and account-security data may include session identifiers, login events, device information, password-security metadata and security signals.
3. Courses, enrolment and academic context
PrymeStudy may process course enrolments, course codes and titles, curriculum information, learning outcomes, topic coverage, prerequisites, schedules, academic calendars, assessment timing, study progress, weak areas and other academic-context signals so features can remain scoped to the correct student and academic environment.
4. Materials and uploaded files
When you upload or use PDFs, documents, slides, images, notes, question sheets or other materials, we may process the file, file metadata, ownership and visibility settings, extracted text, indexing status, previews and generated retrieval information.
Material processing may be used to support search, reading, course-aware assistance, moderation and other features that you request or that are enabled for your account.
5. Lerion and automated study features
Lerion and related automated study features may process prompts, messages, selected courses, learning objectives, course materials, session history, study preferences, generated outputs, tool events, progress signals and relevant academic context.
Depending on the feature, PrymeStudy may retain session summaries, mistakes, mastery signals, learning preferences or other memory used to improve continuity between study sessions. Public preview experiences use more limited context than signed-in student experiences.
6. Images, equations, camera, voice and live interactions
Image or equation analysis may process photographs, screenshots, handwritten work, diagrams, answer sheets, equations and related metadata. Camera-based features process the images you submit or capture for the requested task.
Voice and Live Mode may process microphone audio, generated audio, transcripts, timing and session events where required to provide the realtime experience. The exact data processed depends on the mode and permissions you choose.
7. Academic Research and browser activity
When Lerion or a student uses Academic Research, PrymeStudy may process research questions, search terms, pages visited by the research worker, citations, extracted summaries, source metadata, screenshots or progress events needed to display and audit the research session.
Research activity is intended for academic context and may use external websites or search services. Those external services can have their own privacy practices.
8. Daily Mission, quizzes, games and exam simulation
Study and assessment features may process answers, attempts, scores, question history, completion state, readiness, weak areas, difficulty, timing, streaks, mistakes and other performance signals. These signals may be used to choose practice, adapt difficulty or recommend what to study next.
9. Notes, flashcards, study packs, CodeLab and artifacts
Notes, flashcards, study packs and related tools may store generated or student-created study content and references to the courses or materials from which they were produced.
CodeLab may process code, selected programming language, editor state, execution input, sandbox output and error information. Artifact or project tools may process documents, structured work and project-related content needed for the task.
10. PrymeStudy Social and community data
Social features may process posts, comments, reactions, stories, attachments, mentions, visibility settings, community or course scope, moderation decisions, abuse reports and related activity.
Public content is intended to be visible more broadly. Content shared into course, level, department, institution or other restricted spaces remains subject to the permissions and visibility rules for that space.
11. Tutors, tutorials, live classes and attendance
Tutor and live-class features may process listings, booking or participation information, class schedules, session records, messages, host information and attendance data.
Attendance may include class identifiers, join or check-in events, timestamps, QR or manual attendance actions and reports available to authorized teaching or institution users.
12. Timetables, calendars and notifications
PrymeStudy may process timetable, calendar, reminder and notification data to surface academic events and product updates. Push notification features may store device or push tokens and delivery metadata.
13. Billing, credits, subscriptions and payments
We may process plan, entitlement, Full Access Pass, Starter Month, subscription, usage allowance, credit balance, wallet activity, transaction reference, currency, payment status, provider response metadata and audit records.
Sensitive payment credentials such as full card details are handled by payment providers where applicable rather than stored directly by PrymeStudy.
14. Referrals, support and deletion requests
Referral features may record referral codes and attribution needed to operate the programme. Support workflows may process support messages, attachments, contact information and case history.
Account-deletion requests may include the account email, optional note, IP address, user agent, request status and audit timestamps so requests can be verified and processed safely.
15. Device, browser, cookies, sessions and diagnostics
We use cookies, local storage, sessions, CSRF tokens and similar technologies for authentication, security, preferences, rate limiting, continuity and feature state.
We may collect IP address, browser or device information, application version, request logs, crash or diagnostic information, latency, security events and abuse-prevention signals needed to operate and protect the service.
16. How we use information
We use information to provide and personalize requested features, maintain academic context, enforce permissions, process payments, operate support, prevent abuse, secure accounts, troubleshoot failures, improve reliability and understand product usage.
Where automated features rely on external infrastructure, only the context needed for that task should be sent subject to the feature configuration and provider integration.
17. Authorized institution and teaching visibility
Depending on the feature and your institution relationship, authorized institution staff, lecturers, tutors, moderators or administrators may be able to access relevant course, attendance, material, class, moderation or academic records within their permitted scope.
PrymeStudy does not treat an institution-wide role as permission to access unrelated private student information outside the configured product scope.
18. Service providers and external infrastructure
PrymeStudy may use service providers for cloud hosting, storage, email, authentication, payments, analytics, security, push notifications, AI or model infrastructure, realtime communications, browser research and support operations.
Providers receive information needed for the service they perform and are subject to their own terms, contracts or privacy practices where applicable. Processing can occur in countries different from your own depending on the provider and infrastructure used.
19. Retention, deletion and anonymisation
Retention periods vary by data type, product feature, security needs, institution requirements and legal or accounting obligations. We aim to keep personal information only for as long as it is reasonably needed for those purposes.
When an account is deleted, eligible personal information may be deleted or anonymised. Certain payment, fraud-prevention, security, audit or legal records may need to be retained for a longer period.
20. Your choices and data rights
Depending on applicable law and your relationship with an institution, you may be able to request access, correction, export, restriction or deletion of personal information. Some requests can be completed inside PrymeStudy; others can be submitted through Support or the Account Deletion page.
We may need to verify identity before completing sensitive requests.
21. Younger users
PrymeStudy is designed primarily for tertiary and higher-education contexts. Where a feature is used by a person under the age at which they can independently consent to data processing in their jurisdiction, appropriate authorization may be required.
22. Security
PrymeStudy uses measures such as authentication, role and scope controls, guarded routes, secret validation, password hashing, CSRF protection, logging and operational safeguards. No online system can guarantee absolute security, so users should also protect their credentials and devices.
23. Legal requests and policy changes
We may preserve, disclose or process information when reasonably required to comply with applicable law, valid legal process, protect users, investigate fraud or security incidents, or enforce product rules.
We may update this policy as PrymeStudy changes. Material updates should be published with a new effective date or version.
24. Contact
Privacy questions and data requests can be sent through PrymeStudy Support or to the support contact published on the website.
