Privacy Policy

Guest questions are processed to generate learning guidance. The preview does not create a saved Learning Session, long-term learner state, Teacher context, or uploaded-file record. Short-term preview context is encrypted, bound to the guest cookie, and expires after 45 minutes. The visible board lives in memory and clears on refresh. Abuse protection keeps hashed guest/network counters rather than question content.

Choosing to continue stores a short task summary in this browser tab for up to 45 minutes. After subscribing, you explicitly choose whether to turn it into your first saved learning task; we do not silently import a demo transcript. Closing the tab or declining removes this handoff. An expired handoff cannot be used and is removed when Scholar next checks it. Conversion events contain event names only, never question content.

• Account basics: your email and, if you choose to add them later, a display name, grade level, courses, and study or accessibility preferences used to make the learning experience more relevant and usable. A display name and grade are not required to start learning.
• Saved Learning Sessions: signed-in learning messages, related work, supported Learning Objects, and session history can be stored so students can return to the same learning goal instead of starting over.
• AI requests: the current message and authorized learning context used for an AI turn are processed by the configured AI service to generate a response. The learning system also maintains bounded derived session state, such as the current goal, recent attempts, approaches tried, and an outstanding understanding check. This derived state is separate from the student-visible Learning Session history.
• Teacher support: submitted Teacher requests, follow-up messages, attached work, student-reviewed handoff context, educator drafts, and published Teacher feedback are stored so authorized participants can work on the request.
• Library: private student responses, goals, saved items, read state, and related continuity data can be stored for the individual student's experience. Students do not see other students' responses.
• Usage and security counters: limited counters and hashed identifiers are used to enforce plan limits, rate limits, and abuse protections.
• Guest preview: people trying Scholar without an account receive a pseudonymous guest identifier, and Scholar+ may use a salted one-way network fingerprint for limits and security rather than advertising profiles.

Scholar+ does not ask for a home address, phone number, school ID number, government ID, or a face photo to create a standard account. The self-service age-range eligibility check does not ask for or persist a full date of birth; the resulting admission result is used to determine whether the account can enter the current self-service learning experience. Please do not type sensitive personal information into AI learning messages, Teacher requests, Library responses, or uploads.

• Saved Learning Sessions: signed-in conversations, Learning Objects, submitted work, and published Teacher feedback can be stored to support continuity. AI providers also process the content sent to them.
• Derived learning state: temporary working observations and bounded session context have shorter retention rules than visible Learning Session history. The system also stores bounded, replaceable cross-session projections of subject, skill, learning-agency, and support signals derived from learning evidence. These projections can inform later support, have expiration dates, and are separate from visible history; source evidence has its own retention rules.
• Teacher support records: stored so the student and authorized educator workflow can revisit the support case. Final retention periods for visible learning history, uploads, Teacher feedback, and staff audit records remain under review; no fixed deletion schedule is promised here.
• Uploads: saved-session and Teacher-request uploads are private under the application's access rules. Their retention/deletion rules are separate from temporary derived learning state.
• Account deletion: the account-deletion workflow removes account data and private uploads, subject to records that must be retained for legitimate payment or legal obligations.

Saved Learning Sessions, Teacher-request records, Library data, and uploads are private application data under the app's access rules. They are not public or search-indexed. Staff/educator access depends on the authorized role and relationship required by the current product rules.

AI learning messages and the bounded authorized context needed for a response are processed by the configured AI service. Teacher-request uploads and published human feedback follow a separate support workflow. An AI suggestion to involve Teacher does not itself submit a Teacher request; the student reviews and submits that handoff.

Scholar+ uses service providers for hosting/database functions, payments, authentication, and AI responses. Stripe processes payment details; Scholar+ does not store your full card number. AI requests are processed by the configured AI service. Provider handling is governed by the applicable service configuration, terms, and agreements; this policy does not make an unverified promise about a provider's model-training practices. Scholar+ does not sell personal information or use third-party advertising trackers.

Self-service Scholar+ accounts are currently available only to people age 13 or older. Younger-student accounts and parent-managed under-13 accounts are not currently enabled. New self-service signup uses an age-range check before collecting account information. Scholar+ does not ask for or persist a full date of birth for this standard flow. After sign-in, the account keeps an admission result, method/policy version, and timestamp so the learning boundary can be enforced without turning profile completion into an age or safety gate.

Questions about your data, access, correction, or deletion? Email studio404media@gmail.com.