Privacy Policy

This policy covers LearnefAI's public website and its account-based learning features. LearnefAI is an independent, AI-assisted study tool, not a school or a school-district service. External websites and providers can have their own privacy terms.

For privacy questions, use Contact. For removal of account or learning information, choose Request data deletion.

• Account information: Clerk manages sign-in and account authentication. The application uses a Clerk user identifier and may store your email and account or subscription status to connect your learning activity to your account.
• Profile and learning preferences: optional education level, preferred practice format, prior knowledge, available study time, and requested learning depth. Older accounts may have a previously supplied age; the current profile form does not request an exact age or date of birth.
• Learning inputs and records: prompts, uploaded material during processing, chat requests, generated course content, learning preferences, course progress, assignment submissions and feedback, XP, achievements, and streak activity, depending on the features you use. Not every input is necessarily saved as a separate database record; input information can also appear in generated content.
• Optional private learning groups: a chosen first name, group membership, hashed invitations, and weekly verified XP visible only to members who joined the same private group. Groups are opt-in; there is no public directory or member chat.
• Subscription and referral information: plan status, identifiers associated with payment processing, referral codes, and referral activity where those features apply.
• Support messages: the address, request category, and message you submit when asking for help, reporting content, requesting deletion, or sharing a learning experience. Parent-submitted feedback stays in the private support queue and is not automatically published as a review. Publishing a learner's words or attribution requires separate permission.
• Optional parent summaries, if enabled after review: a recipient email address, invitation and confirmation records, and subscription and delivery records linked to the learner. Summaries use limited learning-activity totals rather than course content or prompts; these counts are not grades or measures of mastery.
• Technical information: request and error logs, security and rate-limit signals, and hosting, page-usage, and performance information. Providers may receive IP addresses, browser or device information, requested URLs, and other request metadata.

Do not submit passwords, sign-in codes, payment-card details, medical information, private school records, or personal information about someone else. Remove identifying details from study material before submitting it.

Information is used to authenticate users, generate and deliver learning content, save course and progress records, personalize available learning features, maintain account limits, administer subscriptions or referrals, and respond to requests. Technical information also supports service operation, troubleshooting, performance measurement, and abuse prevention.

LearnefAI does not sell personal information or use advertising networks. Data is shared with service providers to operate the features described below, subject to their separate terms and the operator's account configuration. We do not treat the public community snapshot as a live analytics feed or evidence of learning outcomes.

Course-generation prompts, relevant course context, chat messages, and text extracted from uploaded study material may be sent to Groq to produce AI responses. Generating a response requires processing the submitted content outside your browser. Responses can contain errors and can repeat details from the input; do not include information you would not want processed by that provider.

The current PDF-processing route reads an uploaded PDF to extract text without saving the original file to Vercel Blob. Extracted text is still processed for AI generation, and generated course content can be saved. This is not a promise that information in a PDF cannot appear in a response, provider record, or operational log.

Earlier versions used public Vercel Blob URLs for uploaded files. A previously stored file may remain accessible to someone with its URL until it is removed. If you previously uploaded sensitive material, identify that upload in a deletion request without re-uploading the sensitive document.

Provider retention, logging, and permitted uses depend on the provider's terms and the account configuration in effect. We do not promise zero-retention AI processing or that all provider-held copies can be removed immediately.

• Clerk: authentication, account sessions, and identity-related account information.
• Groq: processing inputs and producing AI-generated learning responses.
• OpenAI: screening prompts, extracted PDF text, relevant course context, and generated responses for inappropriate content before generation or publication. Screening is not a guarantee of accuracy or safety.
• Resend, when configured: delivering support notifications, parent invitation/confirmation messages, and separately opted-in weekly parent summaries. Delivery requires processing recipient addresses and message content.
• Hosted PostgreSQL through the Vercel Postgres / Neon integration: application records such as accounts, courses, learning preferences, progress, and related activity.
• Vercel: application hosting, request handling, operational infrastructure, and optional public-page Analytics. Vercel Blob may also hold uploads created by earlier versions.
• Stripe: payment and subscription processing for paid accounts. The app uses subscription state and associated identifiers; card entry is handled through payment-provider flows, not the public contact form.

Requests and relevant data are shared with these services as needed for the features they support. Support messages and any enabled, separately opted-in parent-summary emails may also pass through the configured email delivery provider. Provider policies and configurations affect processing, retention, and access. Information may also need to be preserved or disclosed to meet a legal obligation, address abuse, or protect the service and its users.

Authentication uses session-related browser storage through Clerk. The app can also use local storage or cookies for preferences and referral attribution. For example, a referral link can store a referral code for the sign-up flow. Removing or blocking necessary browser storage can prevent sign-in or disrupt account features.

Optional Vercel Web Analytics is disabled by default. If the operator enables it, it records public-page visits and aggregate Start free clicks, without account identifiers, submitted form contents, URL query strings, or fragments. It is not mounted on course, profile, authentication, or parent-token pages. Provider-level technical signals can still include device/browser characteristics. Do not put sensitive information in URLs. Browser privacy settings can limit some collection, but disabling a browser feature is not the same as deleting information already held by the app or its providers.

Public subject samples do not submit quiz answers or create course-progress records. Standard hosting requests and any site-wide analytics still apply when you visit them.

Account, course, and activity records may remain while they are needed to operate your account and the service. Some information may also be retained for security, troubleshooting, billing, resolving disputes, or legal obligations. There is no single automatic expiry period that applies to every record and provider.

Archiving is not deletion. Archiving changes a course's status or visibility in account views; it does not remove its stored content. Deleting or closing an authentication account also should not be assumed to remove every linked learning record, historical upload, or billing record without checking the scope of the deletion.

To request removal, use Contact with the deletion category. The public form is for adults: if you are under 18, ask a parent or guardian to submit the request on your behalf and explain their relationship to you. Adults can submit their own request. Include the learner's account email and the scope of the request, such as a specific course, an earlier upload, or the account and its learning records. Never send a password or verification code. Verification of authorization or a clarification of scope may be necessary before a request can be acted on.

Submitting a request does not mean deletion is complete. Removing active records does not instantly remove backups, cached copies, security logs, legally required billing records, or copies held under a provider's own retention rules. These can expire on separate schedules or require separate provider actions. We do not promise instant deletion or a fixed turnaround time through this page.

If you have a paid subscription, explicitly address cancellation as well as data deletion. A deletion request should not be treated as confirmation that a recurring subscription has been canceled.

You can avoid submitting optional information, review the profile controls available in your account, and stop using the service. Depending on where you live, you may have rights to request access to, correction of, or deletion of information, or to raise concerns about its processing. Use Contact to describe what you need.

Requests are subject to verification, applicable law, and the limitations of records and provider systems involved. This policy does not guarantee that every requested action is available through an automated dashboard control.

LearnefAI is intended for ages 13 and up. Children under 13 should not create an account or submit personal information. Learners under 18 should use the service with a parent or guardian's permission. This age guidance is not a representation that every user's age has been verified.

If you believe a child under 13 has provided information, use the deletion-request option and explain your relationship to the child. Do not attach identity documents or additional sensitive child information in the initial message. A guardian's authority may need to be verified.

Review progress together in the learner's dashboard. Weekly parent summaries, when available in Profile, require the learner to opt in and a parent or guardian to confirm the invitation. If the option is unavailable, no summaries will be sent. Creating an account never enrolls anyone in parent emails.

The service does not promise school-specific privacy compliance or a school data agreement. Families and schools should assess whether the tool fits their own requirements.

Authentication, access controls, input checks, and operational safeguards are intended to reduce risks, but no internet service can guarantee absolute security. Keep account access private, use the available sign-in protections, and report suspected unauthorized access through Contact.

Hosting and AI providers may process information in locations other than where you live. We do not promise that information stays in Palm Beach, Florida, or any single country. This policy is not a certification or a guarantee of legal compliance.

This policy may change as the product, providers, or requirements change. The version and effective date at the top identify this notice. Review the current notice before submitting new information, and contact us if a change raises a question about your existing data.

Also read the Terms of Use for eligibility, acceptable use, and service limitations.