Privacy & Security

Who controls a family workspace

A family administrator creates and manages the family workspace, invites other administrators and students, and controls the school records stored for that family. Students receive access only through an invitation from a family administrator.

Information we collect

Depending on the features a family uses, Student to Scholar may process:

• Account information, including name, email address, phone number, authentication identifiers, and account role.
• Student information, including name, grade level, avatar choice, color, enrolled courses, assignments, schedules, progress, submissions, feedback, and grades.
• Family planning information, including courses, subjects, calendars, no-school dates, family events, books, curriculum details, and uploaded curriculum or book images.
• Learning evidence intentionally saved by the family, including photographs, PDFs, links, reflections, administrator notes, portfolio selections, and Unit Study outcomes.
• Billing-account information, including the selected plan, subscription status, renewal or cancellation timing, Stripe customer and subscription identifiers, and invoice status. Payment-card and bank-account details are entered directly on Stripe’s secure website and are not stored by Student to Scholar.
• Device and service information, including push-notification tokens, device platform, session information, security logs, diagnostics, and IP address information processed by our infrastructure providers.
• Messages and instructions intentionally entered into curriculum-planning or support features.

How we use information

We use this information to authenticate accounts, display the correct family workspace, schedule schoolwork, record progress, deliver requested reminders and review notifications, identify books and curriculum, provide customer support, prevent abuse, maintain service reliability, and comply with legal obligations.

We do not sell personal information. We do not use family or student information for third-party advertising or cross-app tracking.

Service providers

We use service providers only where needed to operate a requested feature. These currently include Supabase for authentication, database, file storage, and server functions; Stripe for website checkout, subscription management, invoices, and payment processing; Expo and Firebase for mobile delivery and notifications; Sentry for privacy-filtered mobile crash diagnostics when enabled; OpenAI for user-requested curriculum and book-image analysis; and Google Books and Open Library for ISBN and book metadata lookup. An ISBN lookup sends the ISBN, not the student’s school record, to the metadata provider.

Provider availability and subprocessors may change as the service evolves. We require providers to protect information consistently with their agreements and applicable law.

Mobile crash diagnostics

Release builds may send a technical crash report to Sentry so we can identify device-specific failures. Reports retain the error type, code location, app version, operating-system version, and device model needed for diagnosis. Student to Scholar disables interaction breadcrumbs, screenshots, view hierarchy, session replay, performance tracing, and default personally identifying fields. Error messages, account details, URLs, student information, assignment information, and custom application context are removed before a JavaScript crash report is sent. We do not use crash diagnostics for advertising or cross-app tracking.

Artificial intelligence

AI processing occurs only when an eligible administrator requests an AI-assisted feature, such as identifying curriculum, generating a proposed plan, extracting book details from an uploaded image, or asking Scholar Guide a how-to question. The relevant prompt, curriculum evidence, or book image may be sent to the AI provider to answer that request. AI output is a proposal and should be reviewed by a family administrator before it becomes part of a school plan.

Scholar Guide is restricted to family administrators. Before a question leaves Student to Scholar, detected student names, family names, email addresses, phone numbers, street addresses, account identifiers, and similar personal details are replaced with neutral labels. The privacy-filtered question and answer are retained in a super-admin-only audit so documentation gaps can be identified. The original personal values and the unsanitized conversation are not stored in that audit, and the AI provider is asked not to retain the request. A user may separately choose to report a help problem; that report includes the selected help context, category, and description the user deliberately enters, but does not attach the Scholar Guide conversation.

Children and students

Student to Scholar is designed to be administered by a parent, guardian, or other authorized family administrator. A family administrator is responsible for deciding whether to create and invite a student account, uploading only learning records they are authorized to keep, and obtaining any consent required by applicable law. Students may review evidence connected to their records but cannot upload or delete photographic evidence. We do not knowingly invite children independently, serve behavioral advertising, or allow unrelated users to discover student profiles.

If you believe a student account was created or an image was uploaded without appropriate authorization, contact us through the Support page.

Photographs and learning evidence

Learning evidence is private to authorized members of the applicable family account and is not publicly displayed. We do not sell it, use it for advertising, perform facial recognition on it, or use it to train artificial-intelligence models. Evidence is sent to an AI provider only if an eligible administrator deliberately invokes a separate AI-assisted feature that clearly identifies the material being processed.

Before an uploaded learning-evidence image is persisted, Student to Scholar removes embedded GPS location information and EXIF, XMP, and similar descriptive metadata supported by the uploaded image format. EXIF metadata is information a camera or editing application may place inside an image, such as the capture location, device details, date, author, or editing history. Removing this hidden information reduces unintended disclosure; administrators should still avoid photographing addresses, identification documents, medical information, or children outside their family without permission.

Permissions and notifications

Camera access is requested only when an administrator chooses to scan an ISBN or photograph learning evidence. Push notifications are optional and may be disabled in the app or the device settings. The core service remains usable when notifications are disabled.

Retention and deletion

Family information is retained while the applicable account or family workspace remains active. Learning-evidence files are stored privately, count toward the family’s storage allowance, and remain until an authorized user removes them or the workspace is deleted. Temporary uploads may be removed after their intake or planning session ends. Deliberately submitted help reports are retained only while useful for support and product improvement and may be deleted after resolution. Privacy-filtered Scholar Guide questions and answers may be retained for product quality and support; unsanitized Scholar Guide transcripts are not retained. Security logs and encrypted backups may remain for a limited operational or legal retention period before they are overwritten or deleted.

Users can initiate permanent account deletion from Configure → Account & access in the mobile app. Deleting a student account removes its student profile and connected schoolwork. Deleting an additional administrator removes that administrator’s access and personal contact profile. If the only family administrator deletes the account and no successor exists, the family workspace and its records are also deleted. Shared curriculum-library records may be retained without the deleted user’s identity so other families do not lose reusable curriculum information.

Security

Data stored in our Supabase-hosted project is encrypted at rest, including regular database backups. We also use encrypted network connections, access controls, database row-level security, and restricted server credentials to protect family information. No internet service can guarantee absolute security, so please use a unique password and promptly report suspected unauthorized access.

Your choices

Users may update profile information, disable notifications, request correction, export relevant information through support, or delete their account. A family administrator may also archive or remove student access in accordance with the family’s responsibilities.

Contact

Questions and privacy requests can be sent to admin@studenttoscholar.com. Please do not email passwords or sensitive student records.